Enterprise Model Release Acceptance

Release coordinate

Keep release coordinate explicit, immutable where required, and independently verifiable.

1. Which model and semantic version identify this release? evidence
2. Can the same coordinate ever point to different bytes? decision

Registration binding

Keep registration binding explicit, immutable where required, and independently verifiable.

1. Which WM-XCT-013 entry and act register the release? evidence
2. Which authority created the immutable coordinate? decision

Package digest

Keep package digest explicit, immutable where required, and independently verifiable.

1. Which digest verifies the exact released bytes? evidence
2. Does any mutable locator masquerade as the lock? decision

Semantic fingerprint

Keep semantic fingerprint explicit, immutable where required, and independently verifiable.

1. Which pinned canonicalization profile produced the semantic fingerprint? evidence
2. Is the fingerprint kept distinct from package-byte identity? decision

Resolution receipt

Keep resolution receipt explicit, immutable where required, and independently verifiable.

1. Which WM-XCT-040 receipt proves mandatory closure resolution? evidence
2. Are all closure members digest-addressed? decision

Transitive retention

Keep transitive retention explicit, immutable where required, and independently verifiable.

1. Which closure bytes must remain for historical replay? evidence
2. Can dependency withdrawal break a prior exact lock? decision

Staging context

Keep staging context explicit, immutable where required, and independently verifiable.

1. For which target context was the closure staged? evidence
2. Does a receipt from another context count? decision

Installability predicate

Keep installability predicate explicit, immutable where required, and independently verifiable.

1. Which mechanical checks make the release installable here and now? evidence
2. Which quality or approval claims are explicitly excluded? decision

Assessment profile

Keep assessment profile explicit, immutable where required, and independently verifiable.

1. Which profile version and digest define the criteria? evidence
2. Can latest or an unpinned profile support assurance? decision

Tool identity

Keep tool identity explicit, immutable where required, and independently verifiable.

1. Which tool versions and artifact digests executed the assessment? evidence
2. Can a tool name alone reproduce the result? decision

Negative fixtures

Keep negative fixtures explicit, immutable where required, and independently verifiable.

1. Which frozen fixture set was executed and did every negative fail as expected? evidence
2. Where is the fixture outcome recorded? decision

Evidence sufficiency

Keep evidence sufficiency explicit, immutable where required, and independently verifiable.

1. Which digest-addressed evidence supports every required kind? evidence
2. Is the assessment active rather than revoked or superseded? decision

Scoped hold

Keep scoped hold explicit, immutable where required, and independently verifiable.

1. Which canonical, new-install or discovery scope does this hold affect? evidence
2. Is it blocking or advisory and who may dispose it? decision

Projection precedence

Keep projection precedence explicit, immutable where required, and independently verifiable.

1. Does the catalogue reflect authoritative current predicates? evidence
2. How is a stale projection detected and corrected? decision

Withdrawal notice

Keep withdrawal notice explicit, immutable where required, and independently verifiable.

1. Which WM-XCT-013 act authorizes the notice and when is it effective? evidence
2. Which current eligibility and discovery scopes stop? decision

Non-destructive retention

Keep non-destructive retention explicit, immutable where required, and independently verifiable.

1. Are release bytes, evidence and the transitive closure retained? evidence
2. Can exact historical locks still resolve after withdrawal? decision