The eight canonical constitutional objects and their authority.
Where you are
About The Engine
This page explains where The Engine comes from and how it is governed: the frozen documents that give it authority and the layered architecture that keeps stored facts separate from derived conclusions. For what The Engine does, see the worked demonstration on the home page.
Active constitutional concepts
- Governing lineage
- Frozen authoritative specification
- Five-layer architecture
Next: Review the governing documents and the five-layer architecture, then open the demonstration to see them in practice.
Return to the ConstitutionAbout The Engine
The Engine treats accountability as something to be reconstructed, not asserted. Rather than explain why an outcome happened, it records what obligations an event created, who accepted them, and whether their execution can be demonstrated from evidence. This page sets out the documents that govern that discipline and the architecture that enforces it.
Constitutional lineage
The system is governed by a frozen, authoritative specification. Implementation is bound by these documents and never modifies them. Stage 1 establishes the constitutional foundation: the eight canonical objects, the five physically separated layers, and the eight-destination information architecture.
Governing documents
Specialties as experimental validation of constitutional properties.
Five-layer architecture; Occupational Medicine first domain; employer-first perspective.
The eight canonical navigation destinations.
The five physical layers.
Time is the eighth canonical object; findings are derived, never stored.
Lifecycle standing is derived; five terminal dispositions; acceptance and deferral are lifecycle events.
Specifies the Stage 1 scope.
Specifies the technology stack and one-way layer architecture.
The five-layer architecture
- Layer 1 — Constitutional Data: immutable constitutional facts (PostgreSQL + Prisma).
- Layer 2 — Constitutional Logic: pure derivation of standing and findings.
- Layer 3 — Constitutional Projection: read-optimized composition of data and logic.
- Layer 4 — Constitutional Presentation: UI components consuming projections.
- Layer 5 — Constitutional Experience: navigation, perspective, and session memory.
Dependency direction is strictly one-way (EB-001 Article IV §3): lower layers never import from higher layers.