What is not established
- No B3 implementation exists and no repository byte has changed.
- The archive/receipt mechanism is designed but has not executed end to end.
- Local receipts are explicitly unattested operator-supplied observations.
- Hosted origin, descendant custody, continuous filesystem custody, runtime network isolation, and production-time disk quotas remain gated or explicit nonclaims.
- B4 still owns the current law drain after B3 cutover.
Exact artifact
The raw hosted bytes were fetched after publication and matched the digest above exactly.
Supersession
This artifact supersedes v1 by relation. V1 remains immutable at issue #25 and gist https://gist.github.com/heyoub/fab81375193946704d9774b6be80b7a0; it is not an implementation basis.
V2 incorporates the executed semantic and mechanism red-team findings: acyclic exact revisions, historical supersession nodes, derived composite meaning, one physical activation owner, typed shared evidence, exact coverage mapping, one-use requests, request-bound preparation, a sole Git-owned execution subject, explicit local-origin and custody ceilings, and a closed B3/B4 migration seam.
Standing
Two independent exact-byte red teams reviewed the published candidate digest and reported no material publication blocker. Implementation may begin only from these exact bytes. A semantic change requires a successor artifact; this issue and gist are not edited in place.
What is not established
Exact artifact
a65dd136226d79db86fa22911d64117ae2d6ecdfee8fa1046bbce43da835a4e2d9f804b493c30e76B10FDFEECB92048C61610EE5481FB4F119C2603116AB20E4536CAD3C891495011,443The raw hosted bytes were fetched after publication and matched the digest above exactly.
Supersession
This artifact supersedes v1 by relation. V1 remains immutable at issue #25 and gist https://gist.github.com/heyoub/fab81375193946704d9774b6be80b7a0; it is not an implementation basis.
V2 incorporates the executed semantic and mechanism red-team findings: acyclic exact revisions, historical supersession nodes, derived composite meaning, one physical activation owner, typed shared evidence, exact coverage mapping, one-use requests, request-bound preparation, a sole Git-owned execution subject, explicit local-origin and custody ceilings, and a closed B3/B4 migration seam.
Standing
Two independent exact-byte red teams reviewed the published candidate digest and reported no material publication blocker. Implementation may begin only from these exact bytes. A semantic change requires a successor artifact; this issue and gist are not edited in place.