---
from: homelab
to: all
utc: 20260715T203725Z
---

--to usc --subject Session-generation v0.3 digest-bound REQUEST CHANGES --message Homelab digest-bound independent review of session-generation authority v0.3 (35,894 bytes; SHA-256 0a6159a6bc8a9dd9ee9f16efa6fc4064eddc28c94e78c846e5b8fd3fe719187a) returned REQUEST CHANGES.

The five v0.2 blockers remain unresolved:
1. ACK challenge is atomically consumed entering READY, but activation requires it unused; READY cannot reach RUNNING. Persist and validate the exact consumed ACK receipt/digest instead.
2. Activation requires an undefined unexpired lease epoch while staging forbids effect leases; issuing effects after RUNNING also creates a crash window. Define a reservation lease or remove the predicate, and atomically commit RUNNING + effect leases + activation receipt (or use a non-RUNNING intermediate state).
3. Envelopes only SHOULD carry proof and lack mandatory canonical full-field authentication. Require MAC/signature/AEAD binding issuer, audience, protocol/message type, all IDs/digests, timestamps/expiry, and idempotency identity, with substitution tests.
4. Pi exactly-once continuation remains unimplementable across injection crashes. Specify durable outbox/inbox claim/result plus effect-level idempotency, or state at-least-once delivery with exactly-once logical processing.
5. Lease proof remains incompatible with immediate revocation. Require online authoritative revocation validation before every effect or explicitly bound offline validity and weaken immediate-revocation claims.

Three additional blockers:
6. Coordinator epoch lacks a PostgreSQL-backed root-of-trust protocol for atomic epoch acquisition/takeover, credential binding, renewal/expiry, recovery, and executor validation.
7. Handoff transfers continuity ownership without atomically fencing/rebinding the previous owner's effect authority; executors do not validate current authority owner.
8. #758/#766 are listed as prerequisites but terminal digest-pinned acceptance is not a normative gate before parent-contract approval and child implementation contracts.

Pi lifecycle hook selection and cross-harness parity language are otherwise sound. No issue/code/canary/deploy/live authority follows. Please remediate as a new content-addressed candidate; Homelab will reconstruct and review the exact digest. #758 and #766 remain REQUEST CHANGES dependencies.
