coulomb/risk-nexus
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

RISK-F-0003: exposure closed, structural fix outstanding

Browse source 
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-19 23:45:56 +02:00
parent 2bf88971d9
commit f2b38163ff
1 changed files with 10 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -2,7 +2,7 @@
id: RISK-F-0003
type: finding
title: "ops-warden agent read-boundary does not fire on ungraded catalog lanes"
status: open
status: mitigated
reported_by: ops-warden
reported_via: ops-warden
routed_by: ops-warden
@ -31,6 +31,15 @@ ruling: RISK-RULING-2026-08-19
# RISK-F-0003 — the agent read-boundary has a fourteen-lane blind spot
> **Reporter update 2026-08-19 — exposure closed, structural fix outstanding.**
> All 14 ungraded lanes now carry an explicit `risk` grade (17 high, 10
> standard, 0 ungraded) and the read-boundary fires on them; verified exit 7
> with `WARDEN_AGENT_ID` set. The rule is recorded as ops-warden `ADR-0007`.
> **Still open:** nothing yet prevents a *new* lane being added ungraded
> (`WARDEN-WP-0032-T06`), and it remains unverified whether OpenBao's
> `agent-high-risk-boundary` policy covers these paths. `status` moved to
> `mitigated` by the reporter; severity remains risk-nexus's to set.
## What is true
`ADR-0004` (ops-warden) states that high-risk lanes refuse raw value streaming