GROUP N ACCEPTED in full (receipt 061e5c2e, out 20260913T1109444702137Z-N; r5 df6cca2d, launch-v2.ps1 6e2c2eac / .cs c3a905ec, run-daemon helpers pinned). Containment contract implemented as ruled; N-D's actual OS error 5 on the pinned exe's breakaway rung is the measurement I wanted. r5 is the field driver. Termination controls: the owned-job / retained-handle authority as built is AUTHORIZED for the field run; PID-tree kill stays forbidden.

NEXT — one return, then I rule provisioning + signing + apply + GO in ONE pass:
GRANTED NOW (read-only PREP, no mutation): run r5's PREP against the intended RIG_ROOT (exclusive-create precondition checked, not created), pinning: subject exe .worktrees/304-w2-repr/target/release/spt.exe 72d30901… (never rebuilt), the prebuilt XTASK_BIN + its hash (no hidden cargo build), firewall blob 848a23fe, the 4 rule-absence samples for spt-core-bootstrap-inbound-tcp/-lan, port 29470 test / 5470 protected, fleet exclusion C:/Users/decid/AppData/Local/spt-core/bin/spt.exe measured not assumed, resident daemon identity (pid 4732 or whatever is there now, by anchor), free space, and the binder state. PREP writes nothing under RIG_ROOT and touches no fleet home.
RETURN WITH IT, in the same doc: the integrated provisioning plan against r5 — the exact ordered mutating steps with commands and pins: rig-local trust overlay (Ruling B: exact repaired bytes; `xtask debug-pin --home` + `xtask debug-rollout --artifact <triple>=<rigexe> --stage-dir <H>/releases --state RIG_ROOT/rollout-state.json --version <explicit>`; real apply + trial promotion; debug-mark-applied NOT authorized), signing key: generated OUTSIDE repo/transcripts/archives, never in argv, unset after, only the signing process + its bounding timeout inherit it, dummy-sentinel negative control first; RIG_ROOT/bin/spt.exe as the ONLY CLI/supervisor/brain/apply path; prepared-home provenance record + one-attempt consumption; the run-scoped daemon job; F5 budgets (PREP 600 / EXP 300 / REPORT 180, handoff 120, report reserve 30); the D3 removal payload 416280db as the cleanup arm; preservation of every original + partial artifact; and the disposal receipt separate from the run ledger.
STILL HELD until that pass: any write under RIG_ROOT, key generation, trust writes, artifact placement, apply, the field run.