Files
management/docs/adr/template.md
T
Thore CimbalandClaude Fable 5 e36ed337a7 feat: slice 1 - the neckbeard framework chain runs end to end
Tracer bullet of the migration design (Gate 4, slice 1): pinned v0.1.1
baseline under docs/sources/upstream/ with provenance note, the
Karpathy block moved verbatim to docs/sources/regelwerk/ (standing
rule mapped onto the sources read-only mechanism), AGENTS.md assembled
from the byte-true upstream sections plus the project section 6
(group rules condensed from the old CLAUDE.md), CLAUDE.md reduced to
the upstream pointer, WORKFLOW.md and all four templates copied,
schema.yaml extended (issue milestone/priority/status columns,
component type, wiki area vision - all flagged in the header),
validate.py and gen_status.py forked with marked extensions,
pruefe_upstream_drift.py added, STATUS.md generated, CI gains the
offline validate job, README directory link defused.

Verified: validate 0 errors 0 warnings (the three pre-existing
directory-link errors are gone), gen_status --check current,
drift check 0 findings, baseline byte-identical to the reference
checkout (10/10 files), four negative tests fire (WIP limit 3x
in-progress, waiting without wartegrund, component slug mismatch,
single-byte drift in WORKFLOW.md). gen_status needs Python >= 3.10
locally (write_text newline) - noted for the design AAR.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-11 12:00:00 +00:00

38 lines
1.2 KiB
Markdown

---
type: adr
id: "0000"
status: proposed # proposed | accepted | superseded
date: YYYY-MM-DD
supersedes: null # path to older ADR, e.g. docs/adr/0002-old.md
superseded_by: null # filled in on the OLD adr when a new one replaces it
related: [] # optional: paths to design docs / issues
---
<!-- Copy to docs/adr/NNNN-slug.md. Delete all comments when filling in. -->
# ADR-0000: Title
## Context
<!-- The situation and the forces at play. Constraints upfront:
deadlines, scale, team knowledge, existing decisions. -->
## Options Considered
<!-- Name each option, even the one you lean toward. Pros/cons per
option; a small dimension table (complexity, cost, maintenance,
familiarity) where it helps. Keep proportional to the decision. -->
## Decision
<!-- The choice, in one or two sentences. -->
## Consequences
<!-- What becomes easier, what becomes harder, what we will need to
revisit. Honest cons included. -->
<!-- Rules: an accepted ADR is never edited — write a new ADR that
supersedes it and set superseded_by here. Lasting directional
decisions only; feature-local choices belong in the design doc. -->