@event4u/agent-config 14.10.0 → 14.12.0

package/src/config/assurance-capability-registry.json

@@ -0,0 +1,223 @@
+{
+  "_comment": "Assurance capability registry — the ONE canonical answer to 'which assurance capability does which surface own, and what is its state'. Phase 0.1 / 0.2 / 0.3 of road-to-agentic-engineering-assurance, and the artefact its blocker `sibling-roadmap-dispositions` resolves against. THIS IS NOT A SECOND GRADER. Exactly one grader exists in this tree — src/scripts/grade_target_readiness.ts — and every capability whose state can be read off a target repository declares the dimension id of that grader which produces it, in `projection`. A capability with `projection: null` is one no shipped probe reads; its state is `unknown` or it is a process obligation owned by a skill, and either way nothing here grades it. TWO AXES, DECLARED PER ENTRY, because conflating them was a real defect in the umbrella roadmap's own premise: `axis: target` is a property of the user's repository that AC is installed into, which is what grade_target_readiness measures; `axis: self` is a property of THIS package's own tests and reviews, which is what the three sibling roadmaps measured. The umbrella's Phase 4 asked to 'consume the sibling dispositions' for capabilities it had also listed as target-repository capabilities — those are different questions with different answers, so the axis is a required field rather than a note. STATE VOCABULARY is exactly four values and is closed: available | missing | degraded | unknown. `unknown` means nobody measured; `missing` means measured absent; `degraded` means present with a named limitation that is recorded in `limitations`. There is no fifth state and adding one is a contract change, not an entry edit.",
+  "schema_version": 1,
+  "owner": "maintainer",
+  "review_by": "2027-08-23",
+  "registered_at": "2026-08-23",
+  "grader": {
+    "path": "src/scripts/grade_target_readiness.ts",
+    "dimensions": 10,
+    "knockouts": ["test-presence", "static-analysis", "security-supply-chain", "ci-enforcement"],
+    "note": "Grades 0 Absent / 1 Present / 2 Enforced-in-CI / 3 Independent-and-diff-scoped, verdict `min` over the four knockouts, printed as `L<n> — bound by <dimension>`. Emits no aggregate figure — a test greps its own output for `%` and `/100`. `null` is 'this tool cannot tell' and is NOT a zero; on a knockout it binds at L0 with its reason printed."
+  },
+  "state_vocabulary": ["available", "missing", "degraded", "unknown"],
+  "capabilities": {
+    "unit-test": {
+      "axis": "target",
+      "owner_surface": "src/scripts/grade_target_readiness.ts",
+      "projection": "test-presence",
+      "state": "available",
+      "rationale": "A test-runner config (vitest/jest/phpunit/pest/pytest) is probed and the 1 → 2 distinction is whether CI blocks on it.",
+      "evidence": "tests/scripts/grade_target_readiness.test.ts — presence asserted in tests/fixtures/target-repos/full, absence in ci-absent",
+      "revisit_if": "the probe stops distinguishing a present runner from an absent one on the committed fixtures"
+    },
+    "integration-test": {
+      "axis": "target",
+      "owner_surface": "src/scripts/grade_target_readiness.ts",
+      "projection": "test-presence",
+      "state": "unknown",
+      "rationale": "No shipped probe separates integration tests from unit tests; both collapse into the test-presence dimension. Recorded as unknown rather than folded into unit-test, because 'we cannot tell them apart' is not 'they are both present'.",
+      "evidence": "src/scripts/grade_target_readiness.ts — the test-presence probe reads runner configs only; no directory or marker convention distinguishes the two",
+      "revisit_if": "a probe lands that reads a test-suite split (a runner project/suite config, or a conventional directory) on the committed fixtures"
+    },
+    "e2e-test": {
+      "axis": "target",
+      "owner_surface": "none",
+      "projection": null,
+      "state": "unknown",
+      "rationale": "No probe exists. `playwright` and `cypress` return zero occurrences in the grader.",
+      "evidence": "grep -oiE 'playwright|cypress' src/scripts/grade_target_readiness.ts → no match, 2026-08-23",
+      "revisit_if": "an e2e probe ships with fixture coverage for presence AND absence"
+    },
+    "behavior-spec": {
+      "axis": "target",
+      "owner_surface": "src/scripts/grade_target_readiness.ts",
+      "projection": "behaviour-contract",
+      "state": "available",
+      "rationale": "AGENTS.md / openapi.yaml / CONTRACT.md presence is probed as the repository's declared behavioural contract.",
+      "evidence": "tests/scripts/grade_target_readiness.test.ts — graded > 0 in the full fixture, 0 in the python fixture",
+      "revisit_if": "the contract probe is widened to a form whose absence the fixtures no longer distinguish"
+    },
+    "test-red-evidence": {
+      "axis": "self",
+      "owner_surface": "src/skills/test-driven-development/SKILL.md",
+      "projection": null,
+      "state": "available",
+      "rationale": "A process obligation, not a repository artefact: an observed failing test is a fact about a run, and no repository scan can recover it. Owned by the TDD skill's RED → GREEN → REFACTOR cycle, which this roadmap explicitly does not duplicate.",
+      "evidence": "src/skills/test-driven-development/SKILL.md:140 — 'Each case from the list then gets its own RED → GREEN cycle'",
+      "revisit_if": "a durable RED-run identifier is emitted somewhere a later reader can check, at which point this becomes projectable"
+    },
+    "mutation-sensitivity": {
+      "axis": "target",
+      "owner_surface": "src/scripts/grade_target_readiness.ts",
+      "projection": "test-strength",
+      "state": "degraded",
+      "limitations": [
+        "detection only — the grader reads stryker/infection/mutmut config presence and never runs a mutation pass",
+        "no universal min-MSI constant exists here and none may be added (AC-8)",
+        "a tool-assisted rig for THIS package was refused on measured grounds by the sibling roadmap"
+      ],
+      "rationale": "Config presence is detected; sensitivity is never measured by this tree. For AC's own suite the manual control-inversion probe in testing-anti-patterns is the substitute, and it is a named substitute rather than a silent one.",
+      "evidence": "src/skills/testing-anti-patterns/SKILL.md:185 — 'No mutation-testing rig required: comment the control out, run that one spec, put it back.' · agents/roadmaps/archive/road-to-test-independence-and-mutation-evidence.md — rig REFUSED (measured), 10 hand probes in minutes",
+      "revisit_if": "a mutation adapter ships that runs a changed-surface pass and reports survivors and timeouts separately"
+    },
+    "property-test": {
+      "axis": "target",
+      "owner_surface": "src/scripts/grade_target_readiness.ts",
+      "projection": "test-strength",
+      "state": "available",
+      "rationale": "fast-check and Hypothesis are probed as property-based libraries.",
+      "evidence": "src/scripts/grade_target_readiness.ts — 'fast-check' and 'hypothesis' tokens present; asserted > 0 in the full fixture",
+      "revisit_if": "the probe stops distinguishing a present property library from an absent one"
+    },
+    "static-analysis": {
+      "axis": "target",
+      "owner_surface": "src/scripts/grade_target_readiness.ts",
+      "projection": "static-analysis",
+      "state": "degraded",
+      "limitations": [
+        "PHP and JS/TS only — on a Python-primary target the dimension is `not detectable`, never 0, and binds at L0 because it is a knockout",
+        "quality-tools ships no Python mode body"
+      ],
+      "rationale": "The limitation is recorded rather than rounded up: a 0 would claim the target lacks static analysis, and a Python target may well run mypy while the tool cannot tell.",
+      "evidence": "src/skills/quality-tools/SKILL.md:33-36 — PHP and JS/TS mode rows only; grep -ci python → 0 · tests/scripts/grade_target_readiness.test.ts:118-119 — toBeNull() with a paired not.toBe(0)",
+      "revisit_if": "a Python mode body lands in quality-tools/references/ and the grader probes it"
+    },
+    "type-check": {
+      "axis": "target",
+      "owner_surface": "src/scripts/grade_target_readiness.ts",
+      "projection": "static-analysis",
+      "state": "degraded",
+      "limitations": [
+        "not separable from static-analysis — tsconfig.json, phpstan.neon and psalm.xml all feed one dimension",
+        "inherits the Python not-detectable limitation"
+      ],
+      "rationale": "Folded into static-analysis by the shipped grader. Recorded as its own capability with a shared projection rather than deleted, because the policy vocabulary distinguishes them even though the probe does not.",
+      "evidence": "src/scripts/grade_target_readiness.ts — tsconfig / phpstan / psalm tokens all under the static-analysis dimension",
+      "revisit_if": "a probe separates type checking from lint/static analysis on the committed fixtures"
+    },
+    "architecture-constraint": {
+      "axis": "target",
+      "owner_surface": "src/scripts/grade_target_readiness.ts",
+      "projection": "architecture-gates",
+      "state": "available",
+      "rationale": ".dependency-cruiser.* and deptrac.yaml are probed; non-knockout.",
+      "evidence": "src/scripts/grade_target_readiness.ts — 'dependency-cruiser' and 'deptrac' tokens; asserted > 0 in the full fixture and 0 in python",
+      "revisit_if": "the probe stops distinguishing presence from absence on the fixtures"
+    },
+    "dependency-audit": {
+      "axis": "target",
+      "owner_surface": "src/scripts/grade_target_readiness.ts",
+      "projection": "security-supply-chain",
+      "state": "available",
+      "rationale": "Lockfile presence plus a blocking audit step in CI; the 1 → 2 distinction is whether the audit job can fail the build.",
+      "evidence": "tests/scripts/grade_target_readiness.test.ts — the full fixture reports 'lockfile; SAST config; audit runs in CI' at grade 2, ci-absent reports 'no blocking audit step' at grade 1",
+      "revisit_if": "the CI-blocking heuristic is replaced by per-job YAML attribution and the coarse reading changes a fixture grade"
+    },
+    "secret-scan": {
+      "axis": "target",
+      "owner_surface": "none",
+      "projection": null,
+      "state": "unknown",
+      "rationale": "No probe exists. gitleaks, trufflehog and detect-secrets return zero occurrences in the grader. Distinct from this package's own secret hygiene, which is a different axis and separately owned.",
+      "evidence": "grep -oiE 'gitleaks|trufflehog|detect-secrets' src/scripts/grade_target_readiness.ts → no match, 2026-08-23",
+      "revisit_if": "a secret-scan probe ships with fixture coverage for presence AND absence"
+    },
+    "security-scan": {
+      "axis": "target",
+      "owner_surface": "src/scripts/grade_target_readiness.ts",
+      "projection": "security-supply-chain",
+      "state": "available",
+      "rationale": "Semgrep and bandit configs are probed under the security-supply-chain knockout.",
+      "evidence": "src/scripts/grade_target_readiness.ts — 'semgrep' and 'bandit' tokens; the python fixture reports 'no SAST config'",
+      "revisit_if": "the SAST probe stops distinguishing presence from absence on the fixtures"
+    },
+    "runtime-probe": {
+      "axis": "target",
+      "owner_surface": "agents/roadmaps/stubs/road-to-target-project-bootstrap-enforce.md",
+      "projection": "runtime-verification",
+      "state": "unknown",
+      "rationale": "Out of scope by design, and the grader says so in its own output rather than grading a 0. Cut with a stated reason by the sibling roadmap: runtime verification needs a deploy platform this package does not own.",
+      "evidence": "src/scripts/grade_target_readiness.ts:270 — notDetectable: 'needs a deploy platform this tool does not own' · agents/roadmaps/archive/road-to-target-project-assurance-readiness.md — 'Runtime verification (canary/flags/rollback) | Needs a deploy platform AC does not own; stubbed, not planned.'",
+      "revisit_if": "this package gains a deploy or runtime surface it owns, at which point the dimension stops being not-detectable"
+    },
+    "visual-regression": {
+      "axis": "target",
+      "owner_surface": "none",
+      "projection": null,
+      "state": "unknown",
+      "rationale": "No probe exists. percy and chromatic return zero occurrences in the grader.",
+      "evidence": "grep -oiE 'percy|chromatic' src/scripts/grade_target_readiness.ts → no match, 2026-08-23",
+      "revisit_if": "a visual-regression probe ships with fixture coverage for presence AND absence"
+    },
+    "independent-test-author": {
+      "axis": "self",
+      "owner_surface": "agents/roadmaps/archive/road-to-test-independence-and-mutation-evidence.md",
+      "projection": null,
+      "state": "unknown",
+      "rationale": "AI council 2026-08-23, 2/2 convergent, pick (1a). The sibling's pre-registered outcome is `unmeasurable-here` — the third pre-registered state, explicitly NOT a null and NOT a refutation: the measurement did not run because the run lacked a subagent dispatch primitive. `unknown` is exactly 'nobody measured' in this vocabulary. It must never be read back as evidence against spec-first authorship, and policy may not select it until the measurement runs.",
+      "evidence": "agents/evidence/analysis/test-independence-unmeasurable.md · agents/roadmaps/archive/road-to-test-independence-and-mutation-evidence.md — the 'Sibling disposition' table written for this blocker to consume",
+      "shipped_mechanism": "a `test_authorship` envelope field, default `unknown`",
+      "revisit_if": "a subagent dispatch primitive ships AND the sibling's pre-registered corpus, grader and threshold are re-run — the pre-registration fixed them in advance so a later run re-runs rather than redesigns"
+    },
+    "independent-review": {
+      "axis": "self",
+      "owner_surface": "agents/roadmaps/archive/road-to-review-independence.md",
+      "projection": null,
+      "state": "degraded",
+      "limitations": [
+        "single-member: one reviewer, one model family",
+        "derived independence pair is `provisional` / `single-pass`",
+        "src/scripts/self_review_gate.ts:471 hardcodes independenceFields(['anthropic'])",
+        "check_review_schema reports `scanned: 1` in this repository today — a corpus of one, which cannot be distinguished from a conforming corpus"
+      ],
+      "rationale": "AI council 2026-08-23, 2/2 convergent, pick (2b). The fresh-context dispatcher shipped and routes the default review path, so the capability is real; the family axis one member cannot supply is a named limitation, so it is degraded rather than available. Recording it degraded is what keeps P8's floor checkable: a same-context review is never presentable as an independent one.",
+      "evidence": "src/scripts/dispatch_r2_reviewer.ts — emits independence: single-member / fresh · agents/roadmaps/archive/road-to-review-independence.md — blocker second-ci-provider-key resolved option (b)",
+      "revisit_if": "self_review_gate.ts stops hardcoding a single provider AND either multi-family routing is measured or single-family parity is measured"
+    },
+    "requirement-trace": {
+      "axis": "self",
+      "owner_surface": "src/scripts/check_requirements_trace.ts",
+      "projection": null,
+      "state": "degraded",
+      "limitations": [
+        "adoption is 1 of 25 active roadmaps, and the single declarer is the mechanism's own roadmap",
+        "enforcement is parked under two fired falsifiers",
+        "demonstrated value is not evaluable — no documented sample exists"
+      ],
+      "falsifiers": {
+        "no_opportunity": "fired",
+        "no_adoption": "fired",
+        "poor_resolution": "not_fired",
+        "no_demonstrated_value": "not_evaluable"
+      },
+      "rationale": "AI council 2026-08-23, 2/2 convergent, pick (3b). The schema ships and resolves deterministically, so the mechanism works; but two of four pre-registered falsifiers have FIRED and enforcement is parked under them, so `available` would launder a parked outcome into a positive one — which is precisely the failure the blocker's `If you do nothing` names. A traceability capability that cannot demonstrate value over the corpus it was built to serve is degraded in delivered capability even when its code is defect-free.",
+      "evidence": "agents/roadmaps/archive/road-to-requirements-traceability-minimal.md — Phase 2 disposition, live reading 3 rows / 3 linked / 0 unlinked / 0 unresolved over 25 active roadmaps with 1 declaring · src/config/requirements-trace-budget.json — shrink-only ratchet at all-zero",
+      "revisit_if": "adoption reaches >= 3 eligible active roadmaps, OR >= 1 non-maintainer-prompted roadmap adopts the fields, OR the `no_demonstrated_value` falsifier transitions from not_evaluable to a measured state"
+    },
+    "evidence-binding": {
+      "axis": "both",
+      "owner_surface": "agents/roadmaps/stubs/road-to-target-project-evidence-contract.md",
+      "projection": "evidence-traceability",
+      "state": "degraded",
+      "limitations": [
+        "per-dimension evidence strings exist on the target axis and are now asserted, but there is no aggregate per-change evidence record",
+        "verify-completion-evidence produces prose — json, schema and machine return 0 occurrences in that skill",
+        "the aggregate schema is transferred, not built"
+      ],
+      "rationale": "The target axis binds every graded dimension to an evidence string, and that invariant is now pinned by a spec rather than merely true. The aggregate per-change record the umbrella's Phase 4.5 and Phase 6 describe is a transferred successor, so the capability is partially present and its gap is named.",
+      "evidence": "tests/scripts/grade_target_readiness.test.ts — the '1.3 evidence binding' block; sabotage-probed both ways · src/skills/verify-completion-evidence/SKILL.md — 0 occurrences of json/schema/machine",
+      "revisit_if": "the evidence-contract stub is promoted and an aggregate per-change record ships"
+    }
+  }
+}

package/src/config/assurance-threshold-budget.json

@@ -0,0 +1,65 @@
+{
+  "_comment": "PRE-REGISTRATION (resolution of `blocker: assurance-enforcement-thresholds` on agents/roadmaps/road-to-agentic-engineering-assurance.md). This file commits to a CLOSED four-dimension measurement framework and establishes that no new blocking assurance policy may be adopted while its applicable thresholds are null. The `registered_at` date is the pre-registration CUTOFF: any blocking assurance policy proposed after it is governed by these thresholds even while they remain null, and may not adopt blocking enforcement until the applicable ones are set. Each threshold is explicitly `null` — not absent — with a `set_when` clause naming the specific measurement run that will produce it, so 'committed' means 'present in a falsifiable state' rather than 'populated with a number'. That distinction is what resolves the contradiction in the blocker's own text, which asked in one line for 'a number and the measurement that produced it' and five lines later said 'the numbers stay unset until the corpus exists'. NO NUMBER IN THIS FILE WAS INVENTED. No benchmark corpus exists in this tree, so no measurement could have produced one, and a provisional number in a src/config/ file is read by later readers as derived — which is the failure this repository treats as worse than an honest gap. An enforcement gate is PROMISED, NOT SHIPPED: committing untested CI automation with nothing to test it against is how an argument-parser defect is discovered on the critical path, and there is no proposed blocking assurance policy in the tree today for it to run against. It is implemented when the first policy proposal arrives or Phase 8.5 begins, whichever comes first. The dimension set is closed: a fifth dimension requires schema_version 2 and re-registration. Decided by AI council 2026-08-23, 2/2 quorum (anthropic/claude-sonnet-4-5 + openai/gpt-4o), convergent on option (a). The convergence is summarised here rather than linked: both members picked (a), both rejected provisional numbers as 'dressed as derivation', and the two clauses that make the four nulls safe — dimension_applicability keyed to observable policy characteristics, and the safety-floor exemption — came from the final round rather than from the blocker's own text.",
+  "schema_version": 1,
+  "owner": "maintainer",
+  "review_by": "2027-08-23",
+  "registered_at": "2026-08-23",
+  "review_by_note": "A calendar date, because every other budget config in src/config/ carries one and the gates read that shape. The council's preferred form — '90 days after the frozen benchmark corpus commit, or 2027-12-31, whichever is earlier' — is not a date and would not parse; the corpus-indexed condition it expresses is carried in `revisit_if` instead, which is where the council itself also put it.",
+  "threshold_setting_procedure": "A threshold may be set only after the measurement named in its `set_when` clause completes. If set from empirical data, that dimension's `_comment` must cite the percentile or delta and the run that produced it (e.g. 'P95 from ablation run 2026-04-12'). If set as a safety floor independent of any empirical distribution (e.g. false_verified_rate 0.0 for a zero-tolerance property), the `_comment` must state 'safety floor' and name the invariant (e.g. 'no credential in a commit message may pass verification'). A threshold citing neither an empirical derivation nor a named safety invariant is rejected on review. This specifies what must be true of a number, not who chairs the meeting that sets it: the blocker's `owner: maintainer` field assigns the VALUES to the maintainer, not the governance process.",
+  "dimension_applicability": {
+    "_comment": "Dimensions govern a policy by its OBSERVABLE characteristics, never by what its author claims about it. Without this section the four nulls together would form a universal 'no blocking policy may be adopted' constant — functionally a universal minimum threshold of infinity, which is exactly the vanity constant AC-8 forbids under another name. With it, a policy that asserts no empirical claim and no safety property is ungoverned and may be adopted without waiting for an ablation.",
+    "false_verified_rate": "Governs any policy that gates `done` — a false green would let a defective change through.",
+    "defect_catch_uplift": "Governs any policy whose own documentation uses `catch`, `detect`, `find` or `prevent` in reference to a defect class.",
+    "cost_budget": "Governs any policy that adds a gate step or invokes an external service.",
+    "false_positive_burden": "Governs any policy that can return red on a change.",
+    "safety_floor_exemption": "A policy asserting a hard safety property (e.g. 'no AWS key in any commit') is governed by false_verified_rate but NOT by defect_catch_uplift: it claims a red line, not a higher catch rate. Such a policy's `_comment` must state 'safety floor' and name the invariant. This is the AC-11 escape hatch — a hard safety property may block without an empirical uplift claim."
+  },
+  "dimensions": {
+    "false_verified_rate": {
+      "description": "Proportion of changes the harness reports verified that contain a defect, or violate a safety property the policy is supposed to catch.",
+      "threshold": null,
+      "measurement": null,
+      "set_when": "A frozen benchmark corpus exists (Phase 8.1) AND the false-confidence metric is instrumented (Phase 8.2) AND an ablation comparing assurance-on against assurance-off has completed (Phase 8.4).",
+      "blocks_enforcement": true,
+      "unit": "proportion (0.0-1.0)",
+      "direction": "lower_is_better",
+      "_comment": null
+    },
+    "defect_catch_uplift": {
+      "description": "Incremental defects caught with the assurance mechanism active, minus the baseline without it.",
+      "threshold": null,
+      "measurement": null,
+      "set_when": "A frozen benchmark corpus exists (Phase 8.1) AND an ablation comparing assurance-on against assurance-off has completed (Phase 8.4). The measurement is the delta in defect-catch count between the two arms.",
+      "blocks_enforcement": true,
+      "unit": "count_delta (integer, may be negative)",
+      "direction": "higher_is_better",
+      "_comment": null
+    },
+    "cost_budget": {
+      "description": "Wall-clock time and token cost per gated change.",
+      "threshold": null,
+      "measurement": null,
+      "set_when": "A frozen benchmark corpus exists (Phase 8.1) AND a cost/latency measurement run has completed (Phase 8.3). Note: cost is measurable independently of ablation completion, so this threshold can be set before the other three.",
+      "blocks_enforcement": true,
+      "unit": "composite: {p50_seconds, p50_tokens, p95_seconds, p95_tokens}",
+      "direction": "lower_is_better",
+      "_comment": null
+    },
+    "false_positive_burden": {
+      "description": "Reds raised by the mechanism that a maintainer overrides as not-a-defect.",
+      "threshold": null,
+      "measurement": null,
+      "set_when": "A frozen benchmark corpus exists (Phase 8.1) AND an ablation has completed (Phase 8.4) AND human labelling of flagged changes as true- or false-positive is complete. That last input is NOT a named Phase 8 step and is the same class of unobtainable input as the sibling roadmap's `blocker: b-human-risk-corpus`.",
+      "blocks_enforcement": true,
+      "unit": "count_per_100_changes (float)",
+      "direction": "lower_is_better",
+      "_comment": null
+    }
+  },
+  "revisit_if": [
+    "Any dimension's threshold is still null 90 days after the frozen benchmark corpus is committed.",
+    "A proposed blocking policy's observable characteristics map to no dimension under `dimension_applicability`.",
+    "Empirical data shows the four-dimension set is incomplete — a failure mode orthogonal to all four emerges.",
+    "The promised enforcement gate is removed or bypassed without bumping schema_version and re-registering."
+  ]
+}

package/src/config/budgets.yml

@@ -4,6 +4,25 @@
 # instead of hard-coding them (measure_augment_budget, and any future
 # per-tool budget meter).
 
+# ── Ownership ─────────────────────────────────────────────────────────────────
+# Added 2026-08-24, road-to-standing-payload-truth `b-budgets-yml-outside-ownership`.
+# This file was outside `lint_budget_ownership`'s corpus for its whole life,
+# because that gate filtered on `.json`. A budget without an owner is a budget
+# nobody has to defend, and this is the one that gates `standing_rule_delivery` —
+# the larger of the two red payload numbers. It is now governed by an explicit
+# single-file row in that gate's `GOVERNED_NON_JSON`, not by a widened glob.
+#
+# `review_by` IS DERIVED, AND NO CADENCE RULE IS DOCUMENTED — said plainly rather
+# than presented as policy. `lint_budget_ownership` requires the field and defines
+# no interval for it. Two conventions are observable in the sibling budgets:
+# four files use 2026-11-10 (the preamble milestone) and seven use a ~1-year
+# horizon, including this file's subject-nearest sibling
+# `preamble-payload-budget.json`. Registered 2026-08-24 on that convention →
+# 2027-08-24. If a cadence is ever written down and disagrees, this date is wrong
+# and should move to the rule rather than the rule to the date.
+owner: maintainer
+review_by: '2027-08-24'
+
 augment_workspace_guidelines:
   # Verified platform maximum: 99,024 chars (re-measured 2026-07; the old
   # 49,512 ceiling from the 2026-05-08 baseline is obsolete). We deliberately

package/src/config/ci-local-parity.yml

@@ -101,6 +101,35 @@ pre_push_budget_seconds: 25
 #   resolver       not a gate at all — a helper a workflow step calls to compute
 #                  something (a diff base, a scope); it decides and blocks nothing
 ci_only:
+  # road-to-target-project-assurance-readiness steps 0.3 and 3.1. Both run in the
+  # NIGHTLY risk-class-drift workflow, and neither belongs in a local gate chain:
+  # `measure_risk_class_drift` APPENDS to a ledger, so putting it in `task ci` would
+  # make every local run write a row and the drift series would measure how often
+  # contributors ran the gate rather than what the tree looks like. Its classifier
+  # self-test is the half that IS worth running locally, and it is reachable —
+  # `classify_change_risk --self-test` — but the workflow invokes it as a step of
+  # its own rather than through the aggregate, which is what this checker sees.
+  # road-to-npm-payload-reduction Phase 3.1. `report_pack_delta` measures the
+  # BRANCH-vs-BASE packed payload, which has no meaning without a pull request:
+  # locally `--base origin/main --head HEAD` on main reads +0.0 KB every time, and
+  # the step's own contract is to write nothing when the delta is zero. It also
+  # checks out BOTH refs into throwaway worktrees and packs each (~1 minute), so
+  # putting it in `task ci` would add a minute to every local run for a number
+  # that is structurally absent locally. It is a REPORT and cannot red the build
+  # (`continue-on-error: true`, and the script exits 0 whatever the number), so
+  # there is no failure a contributor could discover only after pushing — which is
+  # the exact harm this checker exists to prevent.
+  #
+  # Reachable on demand: `task report-pack-delta -- --base <ref> --head <ref>`.
+  - id: report_pack_delta
+    class: artifact
+    reason: "a pull-request-only delta report with no local meaning (base==head reads +0.0 KB and the step writes nothing); it packs two refs in throwaway worktrees at ~1 min, cannot red the build, and is reachable on demand via `task report-pack-delta`"
+  - id: classify_change_risk
+    class: benchmark
+    reason: "invoked as the nightly drift workflow's self-test step; the classifier itself gates nothing and its `--self-test` is runnable locally on demand (`./scripts-run src/scripts/classify_change_risk --self-test`)"
+  - id: measure_risk_class_drift
+    class: benchmark
+    reason: "appends one row per run to agents/evidence/risk-classifier-drift.jsonl — in a local chain it would make the drift series a count of local gate runs rather than a measurement of merged changes; the standing metric is nightly by design (step 3.1 forbids a per-change trigger)"
   - id: check_release_surface_equality
     class: release
     reason: "shells out to `gh pr diff <n>` for a live release PR — there is no PR body to compare the CHANGELOG against on a local checkout"

package/src/config/discovery/prompt-patterns.yml

@@ -0,0 +1,56 @@
+# Controlled prompt-pattern vocabulary for command `## Examples` Why lines.
+#
+# Read by `src/scripts/check_command_examples.ts` (sub-check c). A Why line on
+# an example must cite exactly ONE id from `approved_patterns`.
+#
+# WHY A CONTROLLED VOCABULARY AND NOT FREE PROSE. A worked example teaches two
+# things: what to type, and why that phrasing works. The second half is the part
+# that transfers to a command the reader has not seen. Free prose lets every
+# author invent their own account of it, and six accounts of the same pattern
+# teach the pattern less well than one. The ids are deliberately few and
+# deliberately about the SHAPE of the invocation, never about the command.
+#
+# FORWARD-ONLY, on the `command-verbs.yml` precedent (ADR-041): only commands
+# added, or promoted into `visible` / `advanced`, since the frozen grandfather
+# set in `check_command_examples.ts` are required to carry Why lines. The
+# existing surface is grandfathered and melts down voluntarily.
+#
+# Adding an id here is a governance change: land it in its own PR with the
+# reason the six below could not carry the case. Do NOT add an id to make one
+# awkward example pass — rewrite the example to an existing pattern, or leave
+# the Why line off and accept the gate's finding.
+
+approved_patterns:
+  # Name the end state, not the sequence of steps to reach it. The agent picks
+  # the steps; a step list from the operator overconstrains it and goes stale.
+  - outcome-not-steps
+
+  # Build the verification into the ask, so the agent can tell green from done
+  # without a second turn.
+  - self-check-loop
+
+  # Point at a file, a ticket, a URL, a line range — a resolvable location
+  # beats a description of the thing.
+  - measurable-target
+
+  # Hand over the artifact itself rather than describing it: paste the log, the
+  # diff, the failing output.
+  - give-the-artifact
+
+  # Cite an existing convention, doc, or sibling implementation as the standard
+  # to match, instead of restating it inline.
+  - point-at-reference
+
+  # State the shape the answer must arrive in — a table, JSON, one sentence, a
+  # file path — when the shape is what makes it usable.
+  - say-the-format
+
+# The two literals a Why line may use. Adopted verbatim from
+# `lint_examples.ts` (`### Why it works` / `**Why it works:**`), the strings
+# the demo linter already detects for the SAME purpose on a different
+# population. Reusing the strings rather than the code keeps the two
+# conventions textually aligned without coupling the gates — the demo linter's
+# scope and observable behaviour are compatibility-pinned and stay untouched.
+why_line_literals:
+  - '**Why it works:**'
+  - '### Why it works'

package/src/config/discovery/unassigned-artefacts.yml

@@ -28,6 +28,8 @@
   reason: scaffold template for ticket-bundle tickets (ADR-101); carries no runtime frontmatter — emit-tickets fills it in per ticket
 - path: src/agent-src/templates/contexts.md
   reason: scaffold index for project contexts/
+- path: src/agent-src/templates/playbook.md
+  reason: scaffold for a Playbook context (ADR-244); its frontmatter is the PLAYBOOK'''s (task/scope/grade/invokes) and is shown in a fence, so the file itself carries none
 - path: src/agent-src/templates/contexts/auth-model.md
   reason: scaffold for project auth-model context
 - path: src/agent-src/templates/contexts/data-sensitivity.md

package/src/config/dispatch-economy-metrics.json

@@ -40,7 +40,7 @@
             "status": "armed-awaiting-projection: Phase 3.1-3.3 are data-window-gated (>= 2 weeks of rules_used); this criterion binds the moment a projection ships"
         },
         "ask_economy": {
-            "definition": "Rung-0.5 substitution and adoption (roadmap Phase 4.4): substitution = ask-routed lines / (ask-routed + rung-1 spawn lines); adoption = ask lines with dispatch_outcome DONE / all ask lines; escalation = the caller\u0027s follow-up SPAWN lines carrying route_taken=subagent + escalated=true + origin=dispatch-economy-2026 (the ask line itself cannot know it was insufficient).",
+            "definition": "Rung-0.5 substitution and adoption (roadmap Phase 4.4): substitution = ask-routed lines / (ask-routed + rung-1 spawn lines); adoption = ask lines with dispatch_outcome DONE / all ask lines; escalation = the caller's follow-up SPAWN lines carrying route_taken=subagent + escalated=true + origin=dispatch-economy-2026 (the ask line itself cannot know it was insufficient).",
             "source": "Audit-log orchestration lines with route_taken='ask' (written by src/scripts/ask_transport.ts, origin tag dispatch-economy-2026).",
             "thresholds": {
                 "escalation_kill": 0.3,
@@ -53,7 +53,9 @@
             "thresholds": {
                 "low_quota_signal": 0.2,
                 "_low_quota": "a sustained median quota below 0.2 over the review window is the cut-line evidence Phase 3.1 requires (>= 2 weeks of data) and the retriever gate's demand signal"
-            }
+            },
+            "classification": "pre-intervention-impossible",
+            "classification_note": "Classified 2026-08-23 by road-to-trigger-delivered-rule-bodies step 0.8, which requires exactly one of miswired / pre-intervention-impossible / stale before anything is changed. NOT miswired: the report path works and 755 orchestration lines in agents/runtime/state/audit/2026-08.jsonl carry both fields, null on every one, because orchestration_record.ts:146-147 reads them from --rules-carried / --rules-used CLI flags that no caller anywhere passes. NOT stale: the question it asks is exactly the one a delivery mode makes answerable. IMPOSSIBLE: `rules_used` is 'rules the worker actually applied/cited' (contexts/execution/orchestration-telemetry.md:68), a model self-report, and under an eager projection there is no runtime consumer of rule bodies to instrument -- nothing can distinguish a rule that was applied from one that was merely present. The metric is left registered rather than deleted so this reasoning stays attached to it, and it no longer gates anything: later/road-to-deferred-rule-retriever condition (c) now reads the trigger-MATCH rate (rules_matched / rules_carried, produced by src/scripts/model_rule_injection), which is an event the delivery concern performs rather than a claim the model makes. The match rate is explicitly NOT relabelled as usage: matched-and-delivered is not applied-and-followed, and calling it usage would make the retriever's own demand gate self-fulfilling. Evidence: agents/evidence/analysis/trigger-delivery-baseline.md section 7."
         }
     },
     "honest_null_consequence": "If the re-measured floor on the post-9.29 tree is materially smaller than the cache-economy baseline (roadmap step 1.4), phases 3-5 of road-to-token-economy-dispatch downgrade to blockers citing the null, and the null is published in docs/benchmark.md. A metric nobody re-runs by review_by is treated as the latency file's fossilization failure: the report command below is the re-verification procedure.",

package/src/config/estate-count-budget.json

@@ -6,18 +6,23 @@
   "owner": "maintainer",
   "review_by": "2027-08-18",
   "metric": {
-    "basis": "src/scripts/check_estate_count.ts. The live side uses collect() from update_roadmap_progress \u2014 the same parser the dashboard is generated from, imported rather than re-implemented. The floor side runs the SAME functions over a scratch copy of the base ref's agents/roadmaps/, materialised by _lib/base_tree.ts (git ls-tree + git cat-file --batch; `git archive` cannot be used here because .gitattributes carries `/agents export-ignore` and would yield an empty, silently-zero tree).",
+    "basis": "src/scripts/check_estate_count.ts. The live side uses collect() from update_roadmap_progress \u2014 the same parser the dashboard is generated from, imported rather than re-implemented. The floor side runs the SAME functions over a scratch copy of the base ref's agents/roadmaps/, materialised by _lib/base_tree.ts (git ls-tree + git cat-file --batch; `git archive` cannot be used here because .gitattributes carries `/agents export-ignore` and would yield an empty, silently-zero tree). SKILL METRICS (added 2026-08-24): _lib/skill_estate.ts walks src/skills/*/SKILL.md under the SAME root, so the floor side measures the base ref's own skill tree with the same function. That needs a SECOND materialised subtree \u2014 materialiseSubtree takes one prefix \u2014 and the two are independent on purpose: a base ref with no src/skills (an old tag, a shallow clone) drops the skill metrics and leaves the roadmap metrics ratcheting.",
     "active_roadmaps": "non-draft roadmap candidates at the top level of agents/roadmaps/, as collect() counts them. This is exactly the number the dashboard header prints as 'N open roadmaps'.",
     "later_roadmaps": "roadmap-shaped *.md files under agents/roadmaps/later/ \u2014 the same is_roadmap_candidate name filter the active side uses, so later/README.md is not counted. Counted from the filesystem because parked roadmaps sit outside collect()'s corpus by design; they are estate all the same, and a drawdown that moved everything into later/ and called the number down would be the burial T1's quality anchor exists to prevent.",
     "open_blockers": "blockers whose Status does not start with `resolved`, summed over the active and later corpora.",
-    "floor": "the same three metrics measured at the base ref (origin/main, else the merge commit's first parent). No base ref resolves -> no floor -> the gate FAILS rather than skipping: a shrink-only gate with no floor passes every possible tree. `--base <ref>` is the explicit escape."
+    "floor": "the same three metrics measured at the base ref (origin/main, else the merge commit's first parent). No base ref resolves -> no floor -> the gate FAILS rather than skipping: a shrink-only gate with no floor passes every possible tree. `--base <ref>` is the explicit escape.",
+    "skill_count": "Maintained src/skills/*/SKILL.md files; `lifecycle: deprecated` EXCLUDED. The exclusion is load-bearing rather than tidy: with deprecated skills counted, deprecating one would create no headroom and the retirement mechanism would be unusable against its own gate. 0 skills carry it today, so the exclusion is a no-op now and a correctness property once a tranche lands. Measured 2026-08-24: 299. Reproduce with `find src/skills -name SKILL.md | wc -l` (299 including any deprecated) or `npx tsx -e \"import {measureSkillEstate} from './src/scripts/_lib/skill_estate.ts'; console.log(measureSkillEstate(process.cwd()))\"` for the split.",
+    "skill_description_tokens": "Exact-BPE tokens (js-tiktoken, cl100k_base, via _lib/token_count.ts gpt_tokens) across those skills' `description:` frontmatter fields ONLY \u2014 not bodies. Measured 2026-08-24: 11,461 over 299 skills (52,983 chars). A SECOND DIMENSION, not a companion figure: a count ratchet alone is gameable by merging four large skills into one file, which lowers the count while the description payload a host must carry stays put. AI council 2/2 (2026-08-24) asked for both in one gate over the roadmap's own recommendation of count-plus-informational-figure. UNRESOLVED rather than approximated: when the tokeniser does not resolve on either side the metric is dropped from the compare with a printed reason, because an exact reading against a proxy one differs by more than the growth this gate is trying to catch.",
+    "skill_metric_rejected_candidates": "Measured before choosing, not argued. (b) catalogue bytes via _lib/skill_catalogue.ts read 0 on a real checkout: readProjectedCatalogue walks .claude/skills, empty in any tree where `task generate-tools` cannot complete (it fails under projection.mode=scoped without the config package) \u2014 a ratchet whose reading depends on whether a generator ran reds for the environment. (d) host-listing slots are the host's decision, not the repository's: a measured install published its own budget event stating it had stripped every description and dropped 402 entries. Neither is reproducible from the repo, so neither can carry a floor."
   },
   "growth_allowances": {
     "_comment": "An exact floor leaves no incidental headroom, so every legitimate increase needs a named path. Two are automatic because existing policy already sanctions the act; the third is the general authorisation.",
     "active_roadmaps": "+1 per addition carrying `estate_offset_exempt: <reason>` in its own frontmatter (unchanged T3 key). Without this the sanctioned un-offsettable addition would fail the count half with no green path.",
     "later_roadmaps": "+1 per roadmap moved from the active top level into later/ in the same change. Parking relocates estate rather than creating it. It does NOT cover a later/ file that appears from nowhere, and it is keyed on parking rather than on any offset so that an archive move cannot buy a new later/ file.",
     "open_blockers": "none. Nothing in the policy sanctions a new blocker, so it takes the claim path or nothing.",
-    "claim": "`estate_growth_exempt: <reason>` added, in this change, to the frontmatter of any roadmap under agents/roadmaps/. Authorises growth in any metric, with the reason printed. Diff-scoped, so a claim left in a file authorises nothing later \u2014 the banking failure a stored baseline had. Deliberately unbounded, which a stored baseline could not afford: there the surplus of an over-raise was inherited by the next change, where nobody could act on it; here the next change's floor IS this change's measurement, so there is no surplus to inherit."
+    "claim": "`estate_growth_exempt: <reason>` added, in this change, to the frontmatter of any roadmap under agents/roadmaps/. Authorises growth in any metric, with the reason printed. Diff-scoped, so a claim left in a file authorises nothing later \u2014 the banking failure a stored baseline had. Deliberately unbounded, which a stored baseline could not afford: there the surplus of an over-raise was inherited by the next change, where nobody could act on it; here the next change's floor IS this change's measurement, so there is no surplus to inherit.",
+    "skill_count": "0 \u2014 no allowance, deliberately. The defect this metric addresses is a corpus that grew +8 in one release (290 at 14.0.0, 291 at 14.9.0 and 14.10.0, 299 at 14.11.0) with nothing objecting. An addition takes the estate_growth_exempt claim path \u2014 a recorded reason read from the diff \u2014 or it fails.",
+    "skill_description_tokens": "0 \u2014 same reasoning. An addition that grows the description payload without adding a file is the gaming path this dimension exists to close, and an allowance would reopen it."
   },
   "target": {
     "_comment": "T1's proposed ceilings, kept as the destination. PROPOSALS, NOT REGISTERED: the roadmap says in as many words that both numbers and the window belong to the maintainer, and no date is pinned in this file. Nothing reads these values \u2014 `one_in_one_out.applies_above_active` is the only threshold the gate evaluates.",