Disclosure

Residual coverage the gates do not reach

Each gate names what it does and does not decide. The residuals below are disclosed as part of the standard, not discovered after a gate fails:

• Changelog freeze checks that a published entry's bytes match a recorded digest; it does not judge whether the prose is accurate or complete.
• Range coverage checks that changelog entries tile every released version with no gap or overlap; it does not judge the quality of what they say.
• The unreleased worklog tail is reviewed rather than machine-frozen: before a release cut, entries are correctable in place, so review and version-control history, not a digest, are the control there.
• Store resolution confirms one declared store resolves; it cannot detect a second, unnamed store a project might also keep.
• The tracked-store check confirms the store is a tracked git repository whose pointer, recorded sync target, and actual remote agree; it does not verify that the repository is backed up, accessible, or hosted anywhere in particular.
• The single-writer lease leaves a propagation window between taking the lease and its reaching the sync target; the store-consistency divergence check is the overlapping control that catches a collision in that window, and the two together, not the lease alone, are the guard. In this build the cross-system sync step (opf sync) has not landed, so the lease is enforced single-host single-writer; cross-system enforcement arrives with sync.
• A base tool enforces only the base standard and the profiles it supports; a profile it does not support is recorded as present-but-unevaluated rather than failing base validation.
• The discovery token is a single exact string, stable within a base-schema major line: a mistyped or altered token is a cannot-evaluate that stops the tool, never a silent empty store.
• A host provider's conveniences call the external API of the host the target names. The egress bound is that named host and nothing else; the standard cannot vouch for the host's own behaviour beyond that bound.
• Public deliverables reach the product repository through opf render under that repository's normal review flow; the quality of that review flow is the adopter's own discipline, which the standard requires to exist but does not itself gate.