Docs · Decisions
Decision journal.
Every structural decision is locked in a dated ADR with a re-evaluation trigger. 68 decisions, mirrored exactly from the repository at version 0.38.0.
| ADR | Decision |
|---|---|
| ADR-0068 | ADR-0068-one-maintained-minor-and-a-dated-release-train.md |
| ADR-0067 | ADR-0067-the-workflow-carries-a-contract-the-gate-reads.md |
| ADR-0066 | ADR-0066-a-manifest-row-can-be-proposed-and-a-proposal-never-crosses.md |
| ADR-0065 | ADR-0065-the-gate-can-be-armed-only-by-the-operators-hand.md |
| ADR-0064 | ADR-0064-the-verdict-gets-a-report-an-auditor-reads-alone.md |
| ADR-0063 | ADR-0063-what-a-sarif-finding-about-a-missing-file-anchors-to.md |
| ADR-0062 | the SARIF emission is validated against the official schema, and that is worth one dev dependency |
| ADR-0061 | the spelling brick is specified by a corpus, not by its implementation |
| ADR-0060 | a vacuous green is disclosed, not refused |
| ADR-0059 | the mutation ratchet is enforced as freshness, not as a level |
| ADR-0058 | documentation has genres, and they do not mix |
| ADR-0057 | the shared corpus is pinned without a registry |
| ADR-0056 | the evidence layer widens, and never leaves GATE_NON_SCOPE |
| ADR-0055 | the verdict is a standards-legible in-toto attestation |
| ADR-0054 | the runtime boundary is explicit |
| ADR-0053 | the construction gate certifies a declared horizon, not the whole arc |
| ADR-0052 | the survival thesis and the first third-party mission |
| ADR-0051 | the gate is made as strong as its headline |
| ADR-0050 | the public claim is narrowed to the provable form |
| ADR-0049 | the build is isolated from the publish |
| ADR-0048 | the release carries verifiable proof, and the builder paths we refuse |
| ADR-0047 | the verdict is computed where a test can reach it |
| ADR-0046 | mutation testing is an instrument, not a gate |
| ADR-0045 | the gate cannot be satisfied by paperwork |
| ADR-0044 | generated harness artifacts are refreshed, not owned |
| ADR-0043 | territory is declared in two parts — the rule names the category, the mission names its files |
| ADR-0042 | craft-rule confrontation is continuous, not a gate-crossing ritual |
| ADR-0041 | `runward rules --for <paths>` — declared territory, with a named match reason |
| ADR-0040 | per-rule non-scope declaration — every gate names what it cannot verify |
| ADR-0039 | the operator layer stays outside the CLI — three tiers named, nothing new mechanised |
| ADR-0038 | `--mine` mines across languages, groups by dependency family, and never resurrects a ratified DRAFT |
| ADR-0037 | `runward characterize` detects infrastructure and framework/DB config signals (presence only) |
| ADR-0036 | `runward characterize` reports git churn hotspots and bus-factor — counts, never "seams" |
| ADR-0035 | `runward characterize` extracts pinned versions from the lockfile it already detects |
| ADR-0034 | `runward characterize` sees the whole tree — nested workspaces — and orders every scan deterministically |
| ADR-0033 | `runward status` reports a mission's real lifecycle position — its state and which decisions to reopen |
| ADR-0032 | track the current OSCAL release, and watch dated external facts out-of-band |
| ADR-0031 | sovereign engineering evidence for regulated environments — narrow the wedge, never claim compliance |
| ADR-0030 | the agent operates runward — neutral baseline, best-effort harness detection, machine-readable surface |
| ADR-0029 | MCP is a discovery boundary, never an enforcement path |
| ADR-0028 | Distributable packagings — the gate installable in one gesture, across every channel |
| ADR-0027 | Adapters into competing orchestrators — the gate as a review layer they call |
| ADR-0026 | Hand-over as a gated conformance phase — the succession is proven, not promised |
| ADR-0025 | The OSCAL mapping published as a versioned, citable mini-spec |
| ADR-0024 | A machine surface for the rule set — rules --json, explain |
| ADR-0023 | manifest --sync — runward scaffolds the form, never the content |
| ADR-0022 | Regime mappings as versioned data, selected by --regime-version |
| ADR-0021 | Drift promoted to blocking under --strict; opt-in evidence sealing (--freeze) |
| ADR-0020 | Rule evidence signatures — an opt-in deterministic content predicate |
| ADR-0019 | Typed evidence pointers, verified at the gate |
| ADR-0018 | Native skill packagings as opt-in application adapters over the gated core |
| ADR-0017 | The application↔infrastructure double vision — shared-brick placement as a gated deliverable |
| ADR-0016 | `runward compliance <regime>` — a deterministic evidence-pack assembler, upstream of the auditor |
| ADR-0015 | Regulatory conformance as a regional profile; the OWASP ASI mapping is universal |
| ADR-0014 | The `runward characterize` command contract |
| ADR-0013 | Retro-documentation as the transmission phase pointed backward |
| ADR-0012 | The gate as a port, with harness adapters |
| ADR-0011 | Neutral ecosystem standards as versioned ports in the reference stack |
| ADR-0010 | AGENTS.md as a first-class handover deliverable |
| ADR-0009 | OWASP Top 10 for Agentic Applications (ASI01–10) as the gate's risk grammar |
| ADR-0008 | An opt-in hook seam around check |
| ADR-0007 | Advisory LLM conformance verification, subordinate to the gate |
| ADR-0006 | Rule-set evolution as tracked migrations |
| ADR-0005 | Baseline-worktree test validation is out of scope for the gate |
| ADR-0004 | Advisory drift detection — applied pointers that no longer resolve |
| ADR-0003 | Deterministic form-lint of the conformance manifest before the semantic check |
| ADR-0002 | Harden the --strict gate against vacuous passing |
| ADR-0001 | Enforce declared rule-conformance at the gate |
Generated from the repository ADR journal · runward v0.38.0
← Docs