ENGINEERING CASE STUDY
A release should remain checkable after it leaves the runtime.
The detached-release path binds a declared payload universe, manifest state and receipt snapshots so a recipient can detect modification, unexpected entries and signature or chain failures outside the originating runtime.
Engineering problem
Copying a ZIP or export is not enough to preserve the technical meaning of what was actually issued. A verifier needs a declared universe, content commitments, signature state and failure semantics.
Implementation
The current release verifier freezes an explicitly declared ZIP payload universe, binds payload and detached release manifests, supports detached Ed25519 signing and can verify embedded signed or unsigned V2 receipt snapshots.
Adversarial checks
Current tests reject modified exports, rewritten release manifests, duplicate ZIP names and invalid signature binding. An unsigned release is reported as an attention state rather than upgraded to verified.
Boundary
Detached release verification is implemented, but current product authority explicitly states that it is not yet the default output of packet compilation. Complete end-to-end packet/release readiness is therefore not claimed.