emergent-security/docs/evidence/2026-10-03-decision-runbook-integration.md

Decision and runbook integration evidence

Release 0.2.0, pilot. Knowledge manifest digest: 33bd6ea3b7bf3ea28144ffb20a62b4fcf4b2b7cb7aeddc1da0585fa6853b6162.

Delivered and checked

• 14 cards, 24 owners, 69 revision-pinned source files; all local reviewed source hashes match. Startup is 4,863 UTF-8 bytes within the 5,500-byte budget.
• decisions and runbooks teach the presentation/approval/PDP/procedure boundaries, current owner capabilities, and escalation routes. Startup discovers both; current pilot pointers load this shared release.
• Native v0.2 orientation pack passes runbook-tutorials' actual schema and semantic validator. The pack contains no shell commands, makes all steps manual-only, and stops at preparation/handoff.
• Concrete unsigned adoption draft passes informed-decision's actual intake validator with a synthetic test grant only. It has no approval binding, prebound human, submission receipt or human answer. serves.resolves=never.
• 336 tests pass in the checkout and built source distribution: 327 portable tests plus nine real owner-contract tests enabled by EMERGENT_OWNER_ROOT. Without that variable the nine integration tests explicitly skip.
• The real intake validator refuses missing admission, forged reviewer, caller-pinned approval, caller-supplied effect actor and altered packet content. The actual runbook engine refuses out-of-order handoff and missing evidence, and stops auto-confirm at the manual-only entry step. Run state lives only in disposable temporary directories; no operational rehearsal is claimed.
• Withdrawing either new owner withholds its journey and startup while unrelated root guidance remains retrievable. Existing reference evaluator tests pass.
• Wheel and source distribution build. The wheel carries all 14 cards and the new card bytes match the reviewed release. The source archive contains the pack, draft and integration tests. Release seal and draft freshness checks pass.

Provider understanding

2026-10-03-claude-decision-runbook-probe.json records a fresh Claude session (claude-opus-5-5, installed default) answering eight integration scenarios. The implementing Codex session reviewed recipient, action, ownership and citations. The corrected run preserves all required boundaries; no unsafe recommendation was observed. pep-owner is equivalent to the effect owner responsible for authorization verification. For an unspecified procedure owner, resolving that owner with the delegator before placing the pack is appropriate.

The first run used an overly broad delegator route in several answers. Cards were made explicit about draft submission, engine questions and effect-owner verification, and the eight cases were rerun. The retained report is the corrected result for the exact release digest above. This is not independent review. No full 28-case or cross-provider certification is claimed for 0.2.0; older provider evidence stays tied to 0.1.1.

Limits and remaining live work

No memo was submitted, approval answered, service deployed, notification sent, external policy changed or infrastructure step executed. A local run seal is not independent custody; a valid draft is not submitter admission. The proposed memo class/group and actual submission path require owner disposition.

EMERGENT-WP-0002 remains active. T11 completes the local knowledge/offline handoff integration; T02/T05/T07/T08/T09/T10 retain adoption, independent review, actual compaction/harness continuity, full Grok validation and wider rollout. Automation is linked to existing INFD-WP-0005 and RBT-WP-0006. The existing adoption decision remains open. See docs/decision-runbook-integration.md for exact record links and the owner review package.