Architecture Decisions

Architecture Decision Records (ADRs) explain choices that affect more than one module and are expected to remain stable over time. Read them when you need to understand why the repository uses a particular runtime, deployment, storage, or frontend approach.

ADRs provide design context. Current interfaces still come from schemas, typed contracts, code, and tests; current delivery status comes from Project Progress.

Accepted Decisions

Decision	Date	What it explains
ADR 0001: Agent-first convergence	2026-07-17	Why RIGOR converged shared Agent runtime mechanics, Web tooling, durable jobs, and four domain deployment units without merging domain authority

New records should be added only for durable cross-module decisions, not routine refactors or temporary implementation notes.