Architecture decision records

Each record below captures one architectural decision: the context that forced it, the decision taken, the alternatives weighed, and the consequences accepted. Records are immutable once accepted — a decision that is later reversed gets a new record that supersedes the old one, rather than an edit in place.

The format is a trimmed MADR: Status, Context, Decision, Consequences, Alternatives considered.

ADR	Decision	Status
0001	Repository scope: a pulsed-FRC kinematic and RTL hot-path laboratory, bounded by sibling ownership	Accepted
0002	Multi-language acceleration chain with fastest-measured-first dispatch	Accepted
0003	Local upstream-pending carriers and prescribed sibling inputs	Accepted
0004	Curated public API facade guarded by a drift gate	Accepted
0005	Separate delivered capability from roadmap; gate unimplemented tooling	Accepted
0006	Two-tier formal verification: Lean for software invariants, open-source flow for HDL	Accepted
0007	Validation against cited publications and independent references; no fabricated numbers	Accepted
0008	Two MIF-008 trigger lanes: debounced safety-qualified path and registerless zero-cycle fast-veto lane	Accepted
0009	Standards-interop as contracts and a readiness mapping, not runtimes or compliance	Accepted
0010	Merge-window predictor lock-window feature boundary and veto-dominant double-gate	Accepted