Architecture

ADRs and the meta-project design — how the layers fit together.

• ADR-0001: Adopt Python src-layout
• ADR-0002: Retire the Kuzu graph backend; SQLite is the only store
• ADR-0003: Intent-enforcement layer for exhaustive vocabulary
• ADR-0004: Web Hub is a singleton FastAPI serving every registered project
• ADR-0005: boardos — file-first Scrumban with DB sync, not DB-first
• ADR-0006: External task-tracker seam — the interface an outside tracker must satisfy
• ADR-0007: GUI-first install path — boot the Hub before any CLI setup
• ADR-0008: Design module — reserve a future visual design surface before it ships
• ADR-0009: New-project flow is a single-screen Composer, not a step wizard
• ADR-0010: Consumer distribution needs a version gate before the first real consumer
• ADR-0011: Cross-adapter orchestration lives in core; P8 is not the blocker
• ADR-0012: A lighthouse consumer (streamos) breaks the dogfood monoculture
• ADR-0013: PR-mode multi-agent git workflow is consumer-only; coding-os stays trunk
• ADR-0014: Unified graph-gate — a verifiable, consumer-facing dependency check before edits
• ADR-0015: Kernel scope boundaries — capabilities we deliberately will not buildRecord the platform-grade capabilities the kernel will NOT grow — each with the value it would violate — so a future agent does not reintroduce them as an "obvious" addition.
• ADR-0016: Gated skill-evolution — extend the existing learning loop, do not build a training stackRecord how coding-os should (and should not) adopt the "skill-document-as-trainable-weights" idea from an external, published skill-optimization method — so a future agent extends the existing subsystems instead of standing up a parallel training stack.
• coding-os — Meta-Project Architecture
• Raptor Consolidation Lens — Architecture Review Standard