RISK-WP-0001 T01-T06,T08: the four instruments, the index, and the first grading

Severity (impact x likelihood, fidelity modifier for controls that lie,
headline-vs-constraint, build-mode double grade, the floor), disclosure
(publish/embargoed/restricted, and the build-mode deferral re-taken and
narrowed with RISK-F-0001 in hand), escalation (the five INTENT triggers
settled plus an ordering-hazard trigger the RISK-F-0002 case forced;
proposed, awaiting the custodian), review (intervals, what a review is,
what missing one produces, the production re-score).

Then applied: RISK-F-0001 critical/embargoed/escalated, RISK-F-0002
medium with a high constraint on RISK-F-0001's remediation, filed as a
peer and escalated only on the ordering, RISK-F-0003 high/embargoed/no
escalation. No unset field remains.

REGISTER.md is generated; make check reports overdue, stalled, ungraded
and unanswered escalations without changing anything.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

findings/RISK-F-0003-ops-warden-read-boundary-ungraded-lanes.md

@@ -11,10 +11,22 @@ system: ops-warden
 environment: production
 fix_owner: ops-warden
 fix_tracking: WARDEN-WP-0032-T05
-# risk-nexus's fields, deliberately left unset by the reporter.
-severity: unset
-disclosure: unset
-escalation: unset
+# Graded by risk-nexus 2026-08-19 — docs/rulings/2026-08-19-first-grading.md
+severity: high
+severity_at_production: high
+impact: I4
+likelihood: L2
+fidelity_modifier: false
+production_rescore: false
+disclosure: embargoed
+embargo_condition: "the five exec_capable lanes graded under WARDEN-WP-0032-T05"
+embargo_since: "2026-08-19"
+embargo_review: "2026-09-18"
+escalation: none
+last_reviewed: "2026-08-19"
+review_by: "2026-09-18"
+graded_by: risk-nexus
+ruling: RISK-RULING-2026-08-19
 ---
 
 # RISK-F-0003 — the agent read-boundary has a fourteen-lane blind spot
@@ -122,3 +134,50 @@ OpenBao and owns three of the five lanes above, is `category: tooling`.
 - `wiki/playbooks/agent-read-boundary.md`
 - `RISK-F-0002` — ops-warden sign ungated (same system, different control)
 - `zone-engine` `ZONE-WP-0001-T02` — the work that surfaced this
+
+## Register ruling — 2026-08-19
+
+`high` (`I4` × `L2`), embargoed until the five `exec_capable` lanes are graded
+under `WARDEN-WP-0032-T05`, no escalation.
+
+**Graded on its worst lane.** Four of the five are `I3`-shaped — a publish
+token, an OIDC login, an ingestion key, a hub write token, each bad inside its
+own system. `openbao-api-key` is not: it reaches the store the estate's other
+secrets live in, and a disclosure there propagates past every boundary the
+others respect.
+
+**Likelihood `L2`** — an agent session with `WARDEN_AGENT_ID` is a foothold the
+estate does grant. The register holds the line this finding drew: the exposed
+population is not established, so it is neither assumed zero nor assumed large,
+and the unverified OpenBao `agent-high-risk-boundary` coverage is a review
+question rather than an assumption in either direction. Confirming that
+coverage for these five paths would lower the grade.
+
+**No fidelity modifier, and it was close.** `ADR-0004` reads categorical while
+the implementation is opt-in, so the documentation asserts a boundary that does
+not exist for 14 lanes. The modifier is scoped to attestations a system
+produces at runtime, and documentation drift is not that. But if any compliance
+evidence anywhere cites `ADR-0004` as implemented, that *is* a false
+attestation and a separate finding. This register has not looked, and says so
+rather than assuming.
+
+**No escalation.** Known, owned, tracked (`WARDEN-WP-0032-T05` for the five
+lanes, `WARDEN-WP-0032-T06` for the structural fix), and moving. Severity alone
+deliberately does not reach the operator.
+
+**On the maturity-context direction**, which is the operator's and not
+re-decided here: the note that `.repo-classification.yaml` `category` cannot
+carry the signal is confirmed from this repo's own registration work today.
+`railiance-platform` runs production OpenBao and owns three of the five lanes
+while classified `tooling`; `risk-nexus` classified itself with the same
+vocabulary an hour ago. The maturity ladder needs its own field, and that is
+`ZONE-WP-0001-T03`'s to build.
+
+Reasoning: `docs/rulings/2026-08-19-first-grading.md`.
+
+## Reviews
+
+- **2026-08-19** — graded. Next review 2026-09-18 (`high` → 30 days).
+  Open at review: OpenBao policy coverage of the five paths; whether
+  `WARDEN-WP-0032-T05` has landed; whether any compliance evidence cites
+  `ADR-0004` as implemented.