Codex, Claude, and Grok use session-owner and zone-engine on the two cases. The unsigned draft names that rerun and stays unsubmitted. RISK-F-0015 stays open. Assistant: grok Assistant-Session: 01a10286-9185-7bb2-b411-89cf6ab4c0c6
2.3 KiB
Route clarification — knowledge 0.2.6
Live pilot: 0.2.6, manifest digest
8d1d6a9d4d07fec7b619618de7dfe2be2254c1790f85f4198c7fe19db9751c02.
Release 0.2.5, digest
9e186dbd6f2d5eb455bca24db4b03cd866c63c4e94660430dd15f2ca9856215f,
remains the historical seal for the Informed Decision re-pin. This release
does not extend 0.2.4 provider probes, resume reloads, pilots, or Whitehat's
0.2.3 library acceptance.
What changed
The owner pins are unchanged. Informed Decision remains
b4f637326ba3c2526f4648c4c90544948408d53f.
The startup card now says an earlier knowledge receipt does not carry authority into a resumed, compacted, or provider-switched session. The next recipient is the session owner, and glas-harness owns that boundary. A provider change alone is not a question for the delegator. The startup card is 5301 bytes, under the 5500-byte cap.
The zones card now sends a question about a live zone authorization endpoint to zone-engine. That endpoint is absent. Offline conformance is the whole answer. The PEP owner keeps the stance when an actual allow or deny is requested.
Why
On sealed 0.2.4, Codex, Claude, and Grok each named delegator for
model-switch. The fixture route is session-owner and the source is
glas-harness. Grok named pep-owner for zones while denying a live zone
API. The fixture route is zone-engine. Those reports stay historical.
This wording is the package change. It is not a new provider result, and it
does not close RISK-F-0015. T07 has not accepted it.
Checks
Source check: 24 owners verified-files,
ok: true, live_state_verified: false. Startup retrieves as
verified-files. Seal and unsigned-draft checks pass. Portable tests:
332 passed, 9 skipped. With EMERGENT_OWNER_ROOT=/home/worsch, the 9
owner-contract tests passed. The unsigned adoption draft was regenerated
for this digest and was not submitted. Decision
d20a9750-2b29-534e-8227-fb866581a6ca remains open.
Still open
The first two-case rerun is a separate record:
docs/evidence/2026-10-03-026-route-rerun.md. A later rerun, after the probe
prompt named the token session-owner, is
docs/evidence/2026-10-03-026-role-token-rerun.md. Compaction, a governed harness
session, owner feedback, human
adoption, and fleet reach remain open. EMERGENT-WP-0002 stays blocked.
No DoD-Ok is claimed.