Architecture Decision Records
Accepted
This is the catalog of Architecture Decision Records (ADRs). Each ADR captures one architectural decision: the context in which it was made, the options considered, the decision reached, the rationale, and the resulting consequences.
ADRs are immutable once accepted. To change a decision, file a new ADR that supersedes the old one. The superseded ADR is kept in the log with its status updated.
How to Read an ADR
Each ADR is a short focused document. Read in numerical order to follow the design chain; read by topic to understand a specific decision. ADRs cross-reference each other where decisions depend on prior decisions.
ADR Status Values
- Accepted — the decision is in force
- Superseded — replaced by a later ADR (which it links to)
- Deprecated — no longer in force, no direct successor
- Proposed — drafted but not yet accepted
Catalog
Foundational Architecture
- ADR-0001: Retrieval-First Architecture
- ADR-0002: Three-Layer Design
- ADR-0003: Target Enterprise for V1
- ADR-0004: Use Existing Scaffolders
- ADR-0005: Module Library as Layer 1.5
Schemas and Contracts
- ADR-0006: JSON Canonical Format for Specs
- ADR-0007: Typed Variation Points
- ADR-0008: Adapter Slots with Capability Contracts
- ADR-0009: Fully-Specified Seam Contracts
- ADR-0010: Semver and Compatibility Matrix Versioning
- ADR-0011: Hybrid Form Plus Conversation Input
Pipeline and Sanity Checks
- ADR-0012: Sanity Checks at Five Pipeline Stages
- ADR-0013: Pure-LLM Fallback for Unmatched Requests
- ADR-0014: Save Approved Specs as Reusable Templates
- ADR-0015: Microservices Archetypes Deferred to v1
Registry and Curation
- ADR-0016: Central Manifest Registry
- ADR-0017: Optional Verified Artifact Mirror
- ADR-0018: LLM-Drafted Human-Directed Manifest Authoring
- ADR-0019: Hybrid Capability Namespace Governance
- ADR-0020: Manifest Schema Versioning
Scope and Composition
- ADR-0021: AI/LLM Slice as First-Class Concern
- ADR-0022: RAG Chatbot as MVP Archetype #1
- ADR-0023: CRUD Admin Tool as MVP Archetype #2
- ADR-0024: Module Library Admits Both Provenance Types
- ADR-0025: Java + TS/JS + Python Used Per Concern
Migration
AI Governance and Security
- ADR-0028: Almathal AI Governance Posture
- ADR-0029: Customer AI Governance Outputs
- ADR-0030: Stitcher Security Invariants
Multi-User Governance
How to File a New ADR
When making a new architectural decision:
- Pick the next sequential number (currently 0033 would be next)
- Create a new MDX file at
src/content/docs/decisions/00NN-short-slug.mdx - Use the standard template (see existing ADRs)
- Mark status
Proposed - On acceptance, update status to
Acceptedand add to this index