record

# Record Knowledge Record architectural decisions for future reference, and keep related feature specs in sync. ## Record a decision When a significant architectural or design choice is made, create an ADR: 1. Choose a decentralized ID in the form `YYYY-MM-DD-short-title`. The short title must be specific enough to remain unique among decisions created on the same date. 2. Confirm that `docs/decisions/<id>.md` does not already exist. 3. Create `docs/decisions/<id>.md` using the template below. 4. Update `docs/decisions/INDEX.md` with the new entry. 5. **Reconcile specs** — see "Update or create a spec" below. Existing numeric ADR IDs remain valid and must not be renamed. References use the complete stable ID, for example `ADR-2026-07-16-project-shell-output`. ### ADR template ```markdown # ADR-YYYY-MM-DD-short-title: Short Title **Status:** accepted | superseded by <adr-id> | deprecated **Date:** YYYY-MM-DD **Area:** backend | frontend | infra | protocol | workflow ## Context What situation prompted this decision. 2-5 sentences. ## Decision What was decided. Reference file paths, packages, interfaces. ## Consequences Trade-offs. What becomes easier or harder. ## Alternatives Considered What else was considered and why it was rejected. ``` ### What warrants an ADR Create an ADR only when all of these are true: - The choice establishes a durable constraint, boundary, contract, ownership rule, operational invariant, or repo-wide convention. - There were meani...