| ADR-0102 | ADR-0102-whether-the-seal-hashes-a-junit-report-by-what-the-gate-reads-of-it-rather-than-its-bytes.md | accepted (2026-10-23) — the maintainer chose A now with D and E from the adopter's follow-up: a documented normaliser for drift, `--freeze` refuses to seal a cited JUnit report whose root counts failures or errors, and `check` warns when a cited report carries failures outside the cases it cites. B waits for a second adopter; C is discarded | 2026-10-22 |
| ADR-0101 | ADR-0101-whether-the-eu-ai-act-pack-carries-rows-for-article-50-transparency-and-the-system-qualification.md | accepted (2026-10-23) — the maintainer chose B and C: operator-required rows for the system's qualification and Articles 4, 5, 14 and 50 in a new lens file, and the lens's dated notes printed under the draft's header. A and D are not taken | 2026-10-22 |
| ADR-0100 | ADR-0100-whether-a-mission-can-span-several-repositories-a-system-and-one-aggregated-evidence-file.md | accepted (2026-10-23) — the maintainer kept A (one mission per project) and recorded the convention an operator's system document follows meanwhile: cite each member's emitted artefact by digest, never merge their states. C is the target contract if a second adopter asks; E is measured before any sentence says it works | 2026-10-22 |
| ADR-0099 | ADR-0099-which-regime-lenses-come-after-the-three-ai-ones-cra-nis2-dora-gdpr-and-where-each-belongs.md | accepted (2026-10-23) — the maintainer chose, regime by regime: D for GDPR and NIS2 (a documentation crosswalk, no pack), C for DORA (a lens of the D3 period report, when D3 is built), A for the CRA. B (a pack per regime) is not taken for any of the four | 2026-10-22 |
| ADR-0098 | ADR-0098-whether-the-gate-says-how-old-a-committed-junit-report-is-and-what-it-may-read-to-say-it.md | accepted (2026-10-23) — the maintainer chose B now and G next: the output counts the rows judged on a committed JUnit report and says their freshness is not verified by this command; runward then ships the regenerate-and-compare guard as a recipe adopters run in CI. C, D and E are discarded; F stays written down for a second adopter | 2026-10-22 |
| ADR-0097 | ADR-0097-whether-the-structure-contract-reads-section-headings-written-in-another-language.md | accepted (2026-10-20) — the maintainer chose option A: the structure contract reads the template's English headings only, and names every heading it does not find. Options B to E stay written down with their cost; E (a missing trigger as a strict gap outside the opt-in) is not decided here. An agent wrote this record; the maintainer decided (ADR-0088 decision 4, applied to decisions as to rows) | 2026-10-20 |
| ADR-0096 | Code Quality and JUnit renderings of the verdict, and why runward's gaps are not filed as vulnerabilities | accepted (2026-10-13) — class R under ADR-0088 decision 2; the maintainer accepted the | 2026-10-13 |
| ADR-0095 | `check --json` carries the ratification row by row, the causes by kind, and the assurance mode in force | accepted (2026-10-13) — class R under ADR-0088 decision 2; the maintainer accepted the | 2026-10-13 |
| ADR-0094 | The forge adapter boundary: one port, GitHub and GitLab at parity, the verdict forge-neutral | accepted (2026-10-13) — class R under ADR-0088 decision 2; the maintainer accepted the | 2026-10-13 |
| ADR-0093 | What runward shows is assembled from files the CLI writes and never raises; a customer-run satellite verifies and displays; a hosted product is a separate product | accepted (2026-10-13) — the maintainer accepted the umbrella architecture and its four | 2026-10-13 (revised the same day after two adversarial reviews) |
| ADR-0092 | ADR-0092-a-claims-layer-factual-sentences-are-tagged-typed-and-sealed-the-rest-is-said-unchecked.md | accepted (2026-10-13) — the maintainer accepted the revised record with the three recommended | 2026-10-13 |
| ADR-0091 | ADR-0091-machine-checked-proofs-as-evidence-a-ratified-statement-a-kernel-checked-proof-read-and-never-run.md | accepted (2026-10-12) — class R under ADR-0088 decision 2 (its increment 1 touches the | 2026-10-12 |
| ADR-0090 | ADR-0090-a-mission-chooses-its-assurance-mode-machine-is-a-first-class-choice-honest-only-on-a-named-floor.md | accepted (2026-10-12) — constitutional, class R under ADR-0088 decision 2 (it changes the | 2026-10-12 |
| ADR-0089 | ADR-0089-the-verdict-carries-its-witness-a-small-checker-that-shares-no-code-re-checks-it.md | accepted (2026-10-06) — constitutional, class R under ADR-0088 decision 2 (it touches the | 2026-10-05 |
| ADR-0088 | ADR-0088-runwards-own-delivery-runs-under-a-delegation-charter-the-gate-reads.md | accepted (2026-10-01) — the maintainer accepted this record as written: agents under their own | 2026-10-01 |
| ADR-0087 | ADR-0087-a-qualification-kit-the-user-runs-runward-ships-the-evidence.md | accepted (2026-10-02) — the maintainer accepted the record with every recommended option; | 2026-10-01 |
| ADR-0086 | ADR-0086-security-advisories-and-a-fix-time-target.md | accepted (2026-10-01) — the maintainer accepted the four criteria, the retroactive advisories, eleven after the amendment below (CVE requested for S1 and S2 only), option (b) for the retroactive list and (a) going forward when the fix applies without rework, and the 30-day aim | 2026-10-01 |
| ADR-0085 | ADR-0085-the-release-chain-publishes-a-draft-first-then-makes-it-immutable.md | accepted (2026-10-01) — the maintainer chose the recommended chain, with the prepare phase started by a tag push, and the ratchet summary committed under `docs/compliance/ratchet-summaries/`; the setting is enabled only after one release has run on the new chain | 2026-10-01 |
| ADR-0084 | ADR-0084-security-intake-leaves-one-inbox-the-judgement-stays-human.md | accepted 2026-09-30 — the recommended split, chosen by the maintainer; the two measurements under "What would settle it" remain to be run and can reopen it | 2026-09-30 |
| ADR-0083 | ADR-0083-exit-code-two-carries-several-meanings-say-which-before-splitting-it.md | accepted 2026-09-28 — option A, chosen by the maintainer: keep 2 for every current case, make the class legible; doctor's critical exit stays 2 and is written into the port contract | 2026-09-28 |
| ADR-0082 | ADR-0082-an-agent-may-ratify-under-its-own-name-never-under-a-humans.md | accepted 2026-09-28 — the recommended direction, chosen by the maintainer, who opened the question on 2026-09-27 (« ça peut très bien être un autre agent IA qui va ratifier aussi, pas forcément un humain » [it may very well be another AI agent that ratifies too, not necessarily a human]) | 2026-09-27 |
| ADR-0081 | ADR-0081-the-scale-bench-is-a-local-instrument-not-a-ci-measurement.md | accepted 2026-09-27 — a correction of fact rather than a new direction: it narrows one sentence of ADR-0075 to what the tree does, changes no behaviour and no verdict, and is ratified by the maintainer's merge | 2026-09-27 |
| ADR-0080 | ADR-0080-the-regulated-tier-the-repository-disciplines-the-forge-proves.md | accepted 2026-09-26 — direction chosen by the maintainer after an investigation of what runward already has, what regulated organisations are asked for, and what their forges already enforce; the delivery criteria are below | 2026-09-26 |
| ADR-0079 | ADR-0079-a-release-keeps-a-signed-summary-of-its-mutation-ratchet.md | accepted 2026-09-26 — ratified by the maintainer as a decision, before implementation; the criteria under « What would settle it » are now the delivery criteria, and the 7 run links in ADR-0059 stay until the summary job ships | 2026-09-26 |
| ADR-0078 | The domain core is a category, and one written absence of territory is reopened | accepted 2026-09-24 — the maintainer handed the open question of [ADR-0077](ADR-0077-rules-for-shows-what-the-mission-already-cited-a-reminder-not-a-territory.md) back to be investigated to a conclusion rather than arbitrated; this is that conclusion | 2026-09-24 |
| ADR-0077 | `rules --for` shows what the mission already cited — a reminder, not a territory | accepted 2026-09-24 — the maintainer asked for the defect to be fixed after a three-way investigation (doctrine, code, adversarial field measurement), and approved this shape | 2026-09-24 |
| ADR-0076 | OSCAL 1.2.3, a widening measured rather than announced | accepted 2026-09-24 — the maintainer asked for the watch's findings to be handled; the bump is the policy ADR-0032 already ratified ("track the current OSCAL release"), applied once more with its proof | 2026-09-24 |
| ADR-0075 | ADR-0075-a-required-nature-the-project-cannot-produce.md | accepted 2026-09-12 — all three answers, chosen by the maintainer: install the linter, commit a scan whose subject is the rule, declare the limit a CLI cannot cross | 2026-09-12 |
| ADR-0074 | ADR-0074-a-mission-cites-the-journal-it-declares.md | accepted 2026-09-12 — **option 3**, chosen by the maintainer: `adr:` resolves across the conventional journal locations, and a refusal names every place it looked | 2026-09-12 |
| ADR-0073 | ADR-0073-how-a-report-becomes-citable-evidence.md | accepted 2026-09-12 — **option 1**, chosen by the maintainer: the report is committed, and the product ships the step that makes it committable | 2026-09-11 |
| ADR-0072 | ADR-0072-an-unknown-is-surfaced-never-refused.md | accepted 2026-09-11 (this states a rule the product already follows in three places and | 2026-09-11 |
| ADR-0071 | ADR-0071-what-identifies-the-object-a-report-judges.md | accepted 2026-09-12 — **option 2**, chosen by the maintainer: the digest is printed as of before the write, declared as such | 2026-09-11 |
| ADR-0070 | ADR-0070-the-package-is-the-product.md | accepted 2026-09-11 (decided on a measurement nobody had taken: the tarball opened as a | 2026-09-11 |
| ADR-0069 | ADR-0069-the-structure-contract-is-the-default-for-new-missions.md | accepted 2026-09-09 (the maintainer's explicit call, made on the question the M1 | 2026-09-09 |
| ADR-0068 | ADR-0068-one-maintained-minor-and-a-dated-release-train.md | accepted 2026-09-09 (ratified on the maintainer's order, two days after 0.38.0 shipped — the first supported-lines table below is this policy's first act; the first post-bump security release remains the measurement that settles it) | 2026-09-03 |
| ADR-0067 | ADR-0067-the-workflow-carries-a-contract-the-gate-reads.md | accepted 2026-09-03 (ratified by the maintainer on the 2026-09-02 investigation's measurements, unamended) | 2026-09-02 |
| ADR-0066 | ADR-0066-a-manifest-row-can-be-proposed-and-a-proposal-never-crosses.md | accepted 2026-09-03 (ratified by the maintainer on the 2026-09-02 investigation's measurements, unamended) | 2026-09-02 |
| ADR-0065 | ADR-0065-the-gate-can-be-armed-only-by-the-operators-hand.md | accepted 2026-09-03 (ratified by the maintainer on the 2026-09-02 investigation's measurements, unamended) | 2026-09-02 |
| ADR-0064 | ADR-0064-the-verdict-gets-a-report-an-auditor-reads-alone.md | accepted 2026-09-09 (the maintainer's explicit call — accept and build; the settling measurement, an external reader answering the five questions without the repository, remains ahead of it and is what the pilot runs) | 2026-09-01 |
| ADR-0063 | ADR-0063-what-a-sarif-finding-about-a-missing-file-anchors-to.md | accepted 2026-09-01 (measured against GitHub code scanning; record below) | 2026-08-29 |
| ADR-0062 | the SARIF emission is validated against the official schema, and that is worth one dev dependency | accepted 2026-08-27 | 2026-08-27 |
| ADR-0061 | the spelling brick is specified by a corpus, not by its implementation | accepted 2026-08-27 | 2026-08-27 |
| ADR-0060 | a vacuous green is disclosed, not refused | accepted 2026-08-27 | 2026-08-27 |
| ADR-0059 | the mutation ratchet is enforced as freshness, not as a level | accepted 2026-08-26 (all five criteria demonstrated in CI; the red/green pair for criterion 2 is recorded below with its run ids; this document crosses nothing) | 2026-08-24 |
| ADR-0058 | documentation has genres, and they do not mix | accepted 2026-08-17 (all four criteria met; record below; this document crosses nothing) | 2026-08-17 |
| ADR-0057 | the shared corpus is pinned without a registry | accepted 2026-08-14 (all four ratification criteria met on the built binary; this document crosses nothing) | 2026-08-14 |
| ADR-0056 | the evidence layer widens, and never leaves GATE_NON_SCOPE | accepted 2026-08-14 (the three widenings are delivered with their proofs; record below; this document crosses nothing) | 2026-08-14 |
| ADR-0055 | the verdict is a standards-legible in-toto attestation | accepted (2026-08-14; layers 1 and 2 proven, record below) | 2026-08-14 |
| ADR-0054 | the runtime boundary is explicit | accepted 2026-08-14 (the consolidated boundary test exists and passes on the built binary; record below; this document crosses nothing) | 2026-08-14 |
| ADR-0053 | the construction gate certifies a declared horizon, not the whole arc | accepted (2026-08-13; ratification proofs recorded below) | 2026-08-13 |
| ADR-0052 | the survival thesis and the first third-party mission | accepted 2026-08-18 (the thesis is locked and the pilot is armed — everything that does not depend on the third party; record below) | 2026-08-12 |
| ADR-0051 | the gate is made as strong as its headline | accepted (2026-08-13; ratification record below) | 2026-08-12 |
| ADR-0050 | the public claim is narrowed to the provable form | accepted 2026-08-17 (the five executable proofs were run; record below) | 2026-08-12 |
| ADR-0049 | the build is isolated from the publish | accepted (ratified 2026-08-11 — canary results appended under Ratification) | 2026-08-11 |
| ADR-0048 | the release carries verifiable proof, and the builder paths we refuse | accepted (ratified 2026-08-11 — see Ratification) | 2026-08-11 |
| ADR-0047 | the verdict is computed where a test can reach it | accepted (ratified 2026-08-06 — see Ratification) | 2026-08-06 |
| ADR-0046 | mutation testing is an instrument, not a gate | accepted (ratified 2026-08-05 — see Ratification) | 2026-08-05 |
| ADR-0045 | the gate cannot be satisfied by paperwork | accepted (ratified 2026-08-04 — see Ratification) | 2026-08-04 |
| ADR-0044 | generated harness artifacts are refreshed, not owned | accepted (ratified 2026-08-04 — see Ratification) | 2026-08-04 |
| ADR-0043 | territory is declared in two parts — the rule names the category, the mission names its files | accepted (ratified 2026-07-31 — see Ratification) | 2026-07-31 |
| ADR-0042 | craft-rule confrontation is continuous, not a gate-crossing ritual | accepted (ratified 2026-07-31 — see Ratification) | 2026-07-31 |
| ADR-0041 | `runward rules --for <paths>` — declared territory, with a named match reason | accepted (ratified 2026-07-31 — see Ratification) | 2026-07-31 |
| ADR-0040 | per-rule non-scope declaration — every gate names what it cannot verify | accepted (ratified 2026-07-21 — see Ratification) | 2026-07-21 |
| ADR-0039 | the operator layer stays outside the CLI — three tiers named, nothing new mechanised | accepted | 2026-07-21 |
| ADR-0038 | `--mine` mines across languages, groups by dependency family, and never resurrects a ratified DRAFT | accepted (ratified 2026-07-29 — see Ratification) | 2026-07-20 |
| ADR-0037 | `runward characterize` detects infrastructure and framework/DB config signals (presence only) | accepted (ratified 2026-07-29 — see Ratification) | 2026-07-20 |
| ADR-0036 | `runward characterize` reports git churn hotspots and bus-factor — counts, never "seams" | accepted (ratified 2026-07-29 — see Ratification) | 2026-07-20 |
| ADR-0035 | `runward characterize` extracts pinned versions from the lockfile it already detects | accepted (ratified 2026-07-29 — see Ratification) | 2026-07-20 |
| ADR-0034 | `runward characterize` sees the whole tree — nested workspaces — and orders every scan deterministically | accepted (ratified 2026-07-29 — see Ratification) | 2026-07-20 |
| ADR-0033 | `runward status` reports a mission's real lifecycle position — its state and which decisions to reopen | accepted (ratified 2026-07-29 — see Ratification) | 2026-07-20 |
| ADR-0032 | track the current OSCAL release, and watch dated external facts out-of-band | accepted | 2026-07-17 |
| ADR-0031 | sovereign engineering evidence for regulated environments — narrow the wedge, never claim compliance | accepted | 2026-07-17 |
| ADR-0030 | the agent operates runward — neutral baseline, best-effort harness detection, machine-readable surface | accepted | 2026-07-16 |
| ADR-0029 | MCP is a discovery boundary, never an enforcement path | accepted | 2026-07-16 |
| ADR-0028 | Distributable packagings — the gate installable in one gesture, across every channel | accepted | 2026-07-16 |
| ADR-0027 | Adapters into competing orchestrators — the gate as a review layer they call | accepted | 2026-07-16 |
| ADR-0026 | Hand-over as a gated conformance phase — the succession is proven, not promised | accepted | 2026-07-16 |
| ADR-0025 | The OSCAL mapping published as a versioned, citable mini-spec | accepted | 2026-07-16 |
| ADR-0024 | A machine surface for the rule set — rules --json, explain | accepted | 2026-07-16 |
| ADR-0023 | manifest --sync — runward scaffolds the form, never the content | accepted | 2026-07-16 |
| ADR-0022 | Regime mappings as versioned data, selected by --regime-version | accepted | 2026-07-16 |
| ADR-0021 | Drift promoted to blocking under --strict; opt-in evidence sealing (--freeze) | accepted | 2026-07-16 |
| ADR-0020 | Rule evidence signatures — an opt-in deterministic content predicate | accepted | 2026-07-16 |
| ADR-0019 | Typed evidence pointers, verified at the gate | accepted | 2026-07-16 |
| ADR-0018 | Native skill packagings as opt-in application adapters over the gated core | accepted | 2026-07-12 |
| ADR-0017 | The application↔infrastructure double vision — shared-brick placement as a gated deliverable | accepted | 2026-07-11 |
| ADR-0016 | `runward compliance <regime>` — a deterministic evidence-pack assembler, upstream of the auditor | accepted | 2026-07-10 |
| ADR-0015 | Regulatory conformance as a regional profile; the OWASP ASI mapping is universal | accepted | 2026-07-10 |
| ADR-0014 | The `runward characterize` command contract | accepted | 2026-07-09 |
| ADR-0013 | Retro-documentation as the transmission phase pointed backward | accepted | 2026-07-09 |
| ADR-0012 | The gate as a port, with harness adapters | accepted | 2026-07-09 |
| ADR-0011 | Neutral ecosystem standards as versioned ports in the reference stack | accepted | 2026-07-09 |
| ADR-0010 | AGENTS.md as a first-class handover deliverable | accepted | 2026-07-09 |
| ADR-0009 | OWASP Top 10 for Agentic Applications (ASI01–10) as the gate's risk grammar | accepted | 2026-07-09 |
| ADR-0008 | An opt-in hook seam around check | accepted | 2026-07-07 |
| ADR-0007 | Advisory LLM conformance verification, subordinate to the gate | accepted | 2026-07-07 |
| ADR-0006 | Rule-set evolution as tracked migrations | accepted | 2026-07-07 |
| ADR-0005 | Baseline-worktree test validation is out of scope for the gate | accepted | 2026-07-07 |
| ADR-0004 | Advisory drift detection — applied pointers that no longer resolve | accepted | 2026-07-07 |
| ADR-0003 | Deterministic form-lint of the conformance manifest before the semantic check | accepted | 2026-07-07 |
| ADR-0002 | Harden the --strict gate against vacuous passing | accepted | 2026-07-07 |
| ADR-0001 | Enforce declared rule-conformance at the gate | accepted | 2026-07-07 |