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

Keep RISK-F-0015 open after the role-token rerun.

Browse source 
The two-case routes match session-owner and zone-engine. T07 has not accepted a complete corpus.

Assistant: grok
Assistant-Session: 01a10286-9185-7bb2-b411-89cf6ab4c0c6
This commit is contained in:
tegwick 2026-10-03 23:14:31 +02:00
parent 0022d10aa7
commit 08e9eec0ed
1 changed files with 30 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

32
findings/RISK-F-0015-emergent-claude-owner-routing.md
View file

@ -23,8 +23,8 @@ fidelity_modifier: false
production_rescore: false
disclosure: public
escalation: none
last_checked: "2026-10-03T20:47:08Z"
next_check: "2026-10-03T20:47:08Z"
last_checked: "2026-10-03T21:13:07Z"
next_check: "2026-10-03T21:13:07Z"
cadence: instant
clean_streak: 0
checked_by: "grok/risk-nexus"
@ -213,6 +213,7 @@ met.
Initial filing/movement; cadence remains instant, with no clean rung earned.
- **2026-10-03** — not clean: 0.2.4 Claude zones route is zone-engine; model-switch is delegator, not fixture session-owner, and omits glas-harness. T07 still wait and has not accepted. Stays open. Cadence instant → instant; checked again immediately.
- **2026-10-03** — not clean: sealed 0.2.6 two-case rerun has Codex, Claude, and Grok name zone-engine for zones and glas-harness for model-switch. The fixture role label session-owner is still unused. The rerun is not a full corpus and T07 has not accepted it. Stays open. Cadence instant → instant.
- **2026-10-03** — not clean: probe prompt cd9602c two-case rerun has Codex, Claude, and Grok record zone-engine and session-owner, with glas-harness in the model-switch sources. Some source lists are wider than the fixture. The corpus is two cases and T07 has not accepted it. Stays open. Cadence instant → instant.
## Review — 2026-10-03: sealed knowledge 0.2.6 two-case rerun
@ -238,3 +239,30 @@ Both closure conjuncts remain unmet. The fixture role label is not the
recorded route, the corpus is two cases, and `EMERGENT-WP-0002-T07` is still
`wait`. Severity stays low `I1` × `L3`. Disclosure stays `public`.
Escalation stays `none`.
## Review — 2026-10-03: role-token rerun on sealed knowledge 0.2.6
Status stays `open`. The closure condition is not met.
Probe prompt `cd9602c9d90b4f6c9d32348b27536d36edaede00` names the fixture
token `session-owner`. The rerun is Codex, Claude, and Grok on `zones` and
`model-switch` only. The package is still 0.2.6 digest
`8d1d6a9d4d07fec7b619618de7dfe2be2254c1790f85f4198c7fe19db9751c02`,
commit `f65d0e64bc710eafb1dac4dd64b05516493d8c31`. The prompt change does not
change that seal. Evidence is
`emergent-security/docs/evidence/2026-10-03-026-role-token-rerun.md`. Each
review is an implementing Grok session, not an independent Whitehat principal.
Zones: all three routes are `zone-engine`. Each denies a live authorization
endpoint and HOT-as-permission. Source lists add `net-kingdom` or
`emergent-security` beside the fixture source `zone-engine`.
Model-switch: all three routes are the fixture token `session-owner`. Each
keeps `glas-harness` in sources, refuses carried authority, and requires a
reload. Codex and Grok also cite `emergent-security`. Claude's sources are
`glas-harness` only.
The route tokens for these two cases match. Closure still needs
`EMERGENT-WP-0002-T07` to accept complete current-release provider evidence.
This corpus is two cases, and T07 is still `wait`. Severity stays low
`I1` × `L3`. Disclosure stays `public`. Escalation stays `none`.