cd ../case-studies
~/case-studies/logbook-institution.md
Architectural Deep-Dive

LogBook Institution

A Go and Next.js academic LMS/ERP foundation with JWT-derived tenant context, modular services, and explicit progress limits.

NOTE: The system is in active development and is approximately 9% toward the full parity goal described in its private repository.

tenant-aware LMS backend

system flow

Verified identity establishes organization context before domain handlers run.

JWT
verified identity
→
Context
derive org_id
→
Handlers
Go domain routes
→
PostgreSQL
tenant-scoped state

Snapshot

LogBook Institution is a private Go and Next.js academic LMS/ERP foundation. It explores how a large institutional workflow can be decomposed into a modular backend without losing explicit tenant boundaries, migration discipline, or testable business rules.

The repository describes the project as approximately 9% toward its full Moodle-parity goal. The frontend is currently the binding constraint, so this page presents backend architecture evidence rather than a claim of a finished product.

Backend evidence

  • 35 backend packages organize the domain and supporting services.
  • 168 routes expose the current workflow surface.
  • The Go codebase contains approximately 18.9k lines of code.
  • 46 database migrations record the evolving relational model.
  • The stack includes Go, chi, pgx, Next.js, and PostgreSQL.

Security boundary

The backend derives org_id from a verified JWT claim rather than accepting tenant identity from the request body. Tenant-isolation tests and negative-capability tests exercise the paths that must not cross an organization boundary.

That decision is more important than the route count: authorization context comes from verified identity, and the system tests both what a user can do and what a user must be unable to do.

Current status and trade-offs

This is active architecture work in a private repository. The system has meaningful backend structure, but the full product goal is much larger than the current implementation. The portfolio therefore emphasizes the decisions, boundaries, and measurable repository evidence while keeping the progress claim visible.