Skip to content

Architectural Decision Records

ADRs codify the scope invariants of nubos-pilot. Each ADR is authoritative for the constraint it documents. Decisions are superseded by new ADRs, never rewritten.

Status lifecycle

  1. Proposed: authored but not yet accepted; subject to revision during review.
  2. Accepted: the decision is binding; downstream work consumes the invariant as-is.
  3. Deprecated: superseded by a later ADR (referenced via Supersedes NNNN); retained for history.

An ADR may enter directly as Accepted when it is ratified at authoring time. ADRs are append-only: a superseded ADR is never rewritten; instead a new ADR with a higher number references it via its Supersedes line.

Numbering

ADRs follow the pattern NNNN-kebab-title.md with a zero-padded four-digit sequence starting at 0001. Numbers are incremented monotonically, with no skips and no re-use, so cross-references (for example ADR-0003) stay stable. The index below is contiguous 0001-0019; every number is in use.

The Plan-side Trust Layer ADR was originally authored as a second 0013-plan-trust-layer.md, colliding with the earlier 0013-learnings-store-schema-evolution.md. The collision was resolved by keeping 0013 for the learnings-store ADR (authored first, 2026-05-03) and renumbering the Plan-side Trust Layer ADR to 0019-plan-trust-layer.md.

Index

ADRTitleStatus
0001No-Daemon InvariantAccepted
0002Zero Runtime DependenciesAccepted (amended by 0006, 0014)
0003Max Six Unit-TypesAccepted
0004Atomic Commit per UnitAccepted
0005Three Orthogonal File-TreesAccepted
0006Accept yaml@^2.8 (Amendment to 0002)Accepted
0007Codebase Documentation Layer as Shared Agent MemoryAccepted
0008Worktree Isolation per Slice (opt-in)Accepted
0009TUI Framework for Interactive Dashboard — Option D (no amendment; no TUI dependency adopted)Accepted
0010Nubosloop (Build / Verify / Critic-Schwarm / Route)Accepted
0011Researcher-Schwarm with Mehrheit / Union / Schnittmenge mergeAccepted
0012Completeness Mandate as Pflicht-BoilerplateAccepted
0013Learnings-Store Schema Evolution PolicyAccepted
0014Vector-Memory Layer (opt-in, local-default)Accepted (amends 0002)
0015Named-Agent-Messaging for in-task agent dialogueAccepted
0016Project-Level Close + Archive LifecycleAccepted
0017Strict Output-Schema Enforcement at Write-TimeAccepted
0018Researcher-Schwarm — Schema + Reconciler + Disagreement-Gate + Reasoning-TraceAccepted (amends 0011)
0019Plan-side Trust Layer — Mechanical PLAN.md ValidationAccepted