Internals
For contributors, implementers, and deep-dive readers.
If you are onboarding to the public product surface, stop here and go to Docs Home, Quick Start, or Tutorial. Internals are intentionally the last stop, not the first one.
This section contains detailed technical documentation for those who want to understand or contribute to Manifesto's implementation.
Maintained Internals
Use these pages when you need the current contributor-facing rules around documentation, testing, and glossary terms.
- Glossary - Term definitions
- Test Conventions - Test naming and discovery
- Documentation Governance - Docs maintenance rules
- Current Contract - Single current-only contract entry for external consumers
- Layer Boundaries - Normative layer spec (in Architecture section)
Historical Collections
These indexes are preserved for architectural history and normative traceability. They are not the fastest way to learn the current public surface.
- Architecture Decision Records - Historical decision record index
- Specifications - Current package specs plus historical references
- Design Rationale (FDR) - Rationale index and archived rationale references
- Retired Runtime Pages - Removed package retirement records
Architecture Decision Records (ADRs)
Records of significant architectural decisions:
| ID | Title | Status |
|---|---|---|
| ADR-001 | Layer Separation after Host v2.0.1 | Accepted |
| ADR-002 | DX improvement — automatic $mel injection + onceIntent | Implemented |
| ADR-003 | Historical persistence draft | Superseded by ADR-014 |
| ADR-004 | App Package Internal Decomposition | Proposed |
| ADR-005 | DX improvement — Snapshot Path DSL (${...}) introduction | Withdrawn |
| ADR-006 | Publish Boundary, Canonicalization, and Channel Separation Rules | Proposed |
| ADR-007 | SDK/Runtime Split Kickoff Gate and Staged Locking | Superseded |
| ADR-008 | SDK-First Public Entry and App Package Retirement | Deprecated |
| ADR-009 | Structured PatchPath (Segments) | Implemented |
| ADR-010 | Protocol-First SDK Reconstruction | Implemented |
| ADR-011 | Host Boundary Reset Completeness Policy | Implemented |
| ADR-012 | Remove computed. Prefix from Computed Snapshot Keys | Implemented |
| ADR-013a | MEL Statement Composition — flow and include | Implemented |
| ADR-013b | Entity Collection Primitives — findById, existsById, updateById, removeById | Implemented |
| ADR-014 | Split Former Facade Protocol into Governance and Lineage Packages | Implemented |
| ADR-015 | Snapshot Ontological Purification — Remove Accumulated History from Point-in-Time State | Implemented |
| ADR-016 | Merkle Tree Lineage — Positional Lineage Record Identity via Parent-Linked Hashing | Implemented |
| ADR-017 | Capability Decorator Pattern — Semantic Transformation of SDK Surface | Implemented |
| ADR-018 | Public Snapshot Boundary — User-Facing Snapshot Projection and CanonicalSnapshot Separation | Implemented |
| ADR-019 | Post-Activation Extension Kernel — Safe Public Seam for Arbitrary-Snapshot Operations | Implemented |
| ADR-020 | Intent-Level Dispatchability — dispatchable when Clause | Implemented |
| ADR-021 | MEL Structural Annotation System — @meta Sidecar | Accepted |
| ADR-022 | Compiler-Owned Source Location Sidecar (SourceMapIndex) | Accepted |
| ADR-023 | Object Spread Sugar in MEL | Accepted |
| ADR-024 | Compiler-Owned MEL Source Fragment Editing Primitive | Accepted |
| ADR-025 | Snapshot Ontology Hard Cut — data Retirement and Namespace Separation | Accepted |
| ADR-026 | SDK v5 Action Candidate Surface and Law-Aware submit() Ingress | Accepted |
| ADR-027 | Context and Runtime Namespace Semantics | Accepted |
| ADR-028 | Core-Owned Dynamic Patch Target Semantics | Accepted |
Status meanings (Proposed, Accepted, Implemented, Withdrawn, etc.) are defined in ADR Status Definitions.
There is no standalone ADR-013 page. The mixed proposal was split into ADR-013a and ADR-013b.
Documentation Governance
- Documentation Governance — Core documentation operating rules for ADR/SPEC/FDR, link consistency, archival policy, and PR documentation gates
Specifications
Formal specifications for each package. See the Specifications Hub for links to all package specifications with current versions, plus draft package specs that have not yet landed in the active workspace.
Design Rationale (FDRs)
Foundational Design Records explaining the "why" behind decisions. See the FDR Hub for links to all package FDRs.
Contributing
See the Contributing Guide for how to contribute to Manifesto.