EM-XCT-10 · Enterprise profiles · Published 0.1.0

Enterprise Model Release Acceptance

Register immutable model releases, derive context-qualified installability and assurance, gate canonical status with evidence and holds, and withdraw new use without destroying reproducibility.

4 bundles · 8 layers · 16 findings · 32 questions

Required adoption limits

Use as a bounded reference gate with authoritative external registry, resolver and profile inputs. Do not treat fixture defaults, catalogue flags or labels as production proof.

Publication addendum and exact limits

Use in a Company Dimension

Start with a pinned external claim, a file capture, an acquisition activity and an attributed account. Add evidence relationships and purpose-qualified assessments when needed. The package includes three synthetic examples, a closed schema, a reference validator and native installation checks.

Research assurance: reviewable-draft. This is a bounded original companion. Truth, permissions and source independence are never inferred. A trusted host must authenticate actors, hold the latest complete register and invoke the companion validator. Adoption limits.

Bundles → Layers → Findings → Questions

Collect the expected evidence for each question. Unknown context remains explicit. Listed actions confer no operational permission.

MRA-B1Release identity2 layers

Govern release identity for an enterprise model release.

MRA-L1Coordinates and immutability2 findings

Separate and verify coordinates and immutability.

MRA-F1

Release coordinate

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

Questions

MRA-Q1 Which model and semantic version identify this release?evidence
Expected answer
- Release coordinate
MRA-Q2 Can the same coordinate ever point to different bytes?decision
Expected answer
- Release coordinate

Artifacts

Release coordinate recordDigest-addressed record or reference governed by this profile.

Actions and unknown handling

Validate the governed record and retain its evidence without conferring operational permission.

MRA-F2

Registration binding

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

Questions

MRA-Q3 Which WM-XCT-013 entry and act register the release?evidence
Expected answer
- Registration binding
MRA-Q4 Which authority created the immutable coordinate?decision
Expected answer
- Registration binding

Artifacts

Registration binding recordDigest-addressed record or reference governed by this profile.

Actions and unknown handling

Validate the governed record and retain its evidence without conferring operational permission.

MRA-L2Byte and semantic identity2 findings

Separate and verify byte and semantic identity.

MRA-F3

Package digest

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

Questions

MRA-Q5 Which digest verifies the exact released bytes?evidence
Expected answer
- Package digest
MRA-Q6 Does any mutable locator masquerade as the lock?decision
Expected answer
- Package digest

Artifacts

Package digest recordDigest-addressed record or reference governed by this profile.

Actions and unknown handling

Validate the governed record and retain its evidence without conferring operational permission.

MRA-F4

Semantic fingerprint

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

Questions

MRA-Q7 Which pinned canonicalization profile produced the semantic fingerprint?evidence
Expected answer
- Semantic fingerprint
MRA-Q8 Is the fingerprint kept distinct from package-byte identity?decision
Expected answer
- Semantic fingerprint

Artifacts

Semantic fingerprint recordDigest-addressed record or reference governed by this profile.

Actions and unknown handling

Validate the governed record and retain its evidence without conferring operational permission.

MRA-B2Resolution and installability2 layers

Govern resolution and installability for an enterprise model release.

MRA-L3Exact closure2 findings

Separate and verify exact closure.

MRA-F5

Resolution receipt

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

Questions

MRA-Q9 Which WM-XCT-040 receipt proves mandatory closure resolution?evidence
Expected answer
- Resolution receipt
MRA-Q10 Are all closure members digest-addressed?decision
Expected answer
- Resolution receipt

Artifacts

Resolution receipt recordDigest-addressed record or reference governed by this profile.

Actions and unknown handling

Validate the governed record and retain its evidence without conferring operational permission.

MRA-F6

Transitive retention

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

Questions

MRA-Q11 Which closure bytes must remain for historical replay?evidence
Expected answer
- Transitive retention
MRA-Q12 Can dependency withdrawal break a prior exact lock?decision
Expected answer
- Transitive retention

Artifacts

Transitive retention recordDigest-addressed record or reference governed by this profile.

Actions and unknown handling

Validate the governed record and retain its evidence without conferring operational permission.

MRA-L4Target-context staging2 findings

Separate and verify target-context staging.

MRA-F7

Staging context

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

Questions

MRA-Q13 For which target context was the closure staged?evidence
Expected answer
- Staging context
MRA-Q14 Does a receipt from another context count?decision
Expected answer
- Staging context

Artifacts

Staging context recordDigest-addressed record or reference governed by this profile.

Actions and unknown handling

Validate the governed record and retain its evidence without conferring operational permission.

MRA-F8

Installability predicate

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

Questions

MRA-Q15 Which mechanical checks make the release installable here and now?evidence
Expected answer
- Installability predicate
MRA-Q16 Which quality or approval claims are explicitly excluded?decision
Expected answer
- Installability predicate

Artifacts

Installability predicate recordDigest-addressed record or reference governed by this profile.

Actions and unknown handling

Validate the governed record and retain its evidence without conferring operational permission.

MRA-B3Assessment and evidence2 layers

Govern assessment and evidence for an enterprise model release.

MRA-L5Profile and tool pins2 findings

Separate and verify profile and tool pins.

MRA-F9

Assessment profile

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

Questions

MRA-Q17 Which profile version and digest define the criteria?evidence
Expected answer
- Assessment profile
MRA-Q18 Can latest or an unpinned profile support assurance?decision
Expected answer
- Assessment profile

Artifacts

Assessment profile recordDigest-addressed record or reference governed by this profile.

Actions and unknown handling

Validate the governed record and retain its evidence without conferring operational permission.

MRA-F10

Tool identity

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

Questions

MRA-Q19 Which tool versions and artifact digests executed the assessment?evidence
Expected answer
- Tool identity
MRA-Q20 Can a tool name alone reproduce the result?decision
Expected answer
- Tool identity

Artifacts

Tool identity recordDigest-addressed record or reference governed by this profile.

Actions and unknown handling

Validate the governed record and retain its evidence without conferring operational permission.

MRA-L6Fixtures and evidence2 findings

Separate and verify fixtures and evidence.

MRA-F11

Negative fixtures

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

Questions

MRA-Q21 Which frozen fixture set was executed and did every negative fail as expected?evidence
Expected answer
- Negative fixtures
MRA-Q22 Where is the fixture outcome recorded?decision
Expected answer
- Negative fixtures

Artifacts

Negative fixtures recordDigest-addressed record or reference governed by this profile.

Actions and unknown handling

Validate the governed record and retain its evidence without conferring operational permission.

MRA-F12

Evidence sufficiency

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

Questions

MRA-Q23 Which digest-addressed evidence supports every required kind?evidence
Expected answer
- Evidence sufficiency
MRA-Q24 Is the assessment active rather than revoked or superseded?decision
Expected answer
- Evidence sufficiency

Artifacts

Evidence sufficiency recordDigest-addressed record or reference governed by this profile.

Actions and unknown handling

Validate the governed record and retain its evidence without conferring operational permission.

MRA-B4Publication control2 layers

Govern publication control for an enterprise model release.

MRA-L7Holds and projection2 findings

Separate and verify holds and projection.

MRA-F13

Scoped hold

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

Questions

MRA-Q25 Which canonical, new-install or discovery scope does this hold affect?evidence
Expected answer
- Scoped hold
MRA-Q26 Is it blocking or advisory and who may dispose it?decision
Expected answer
- Scoped hold

Artifacts

Scoped hold recordDigest-addressed record or reference governed by this profile.

Actions and unknown handling

Validate the governed record and retain its evidence without conferring operational permission.

MRA-F14

Projection precedence

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

Questions

MRA-Q27 Does the catalogue reflect authoritative current predicates?evidence
Expected answer
- Projection precedence
MRA-Q28 How is a stale projection detected and corrected?decision
Expected answer
- Projection precedence

Artifacts

Projection precedence recordDigest-addressed record or reference governed by this profile.

Actions and unknown handling

Validate the governed record and retain its evidence without conferring operational permission.

MRA-L8Withdrawal and history2 findings

Separate and verify withdrawal and history.

MRA-F15

Withdrawal notice

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

Questions

MRA-Q29 Which WM-XCT-013 act authorizes the notice and when is it effective?evidence
Expected answer
- Withdrawal notice
MRA-Q30 Which current eligibility and discovery scopes stop?decision
Expected answer
- Withdrawal notice

Artifacts

Withdrawal notice recordDigest-addressed record or reference governed by this profile.

Actions and unknown handling

Validate the governed record and retain its evidence without conferring operational permission.

MRA-F16

Non-destructive retention

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

Questions

MRA-Q31 Are release bytes, evidence and the transitive closure retained?evidence
Expected answer
- Non-destructive retention
MRA-Q32 Can exact historical locks still resolve after withdrawal?decision
Expected answer
- Non-destructive retention

Artifacts

Non-destructive retention recordDigest-addressed record or reference governed by this profile.

Actions and unknown handling

Validate the governed record and retain its evidence without conferring operational permission.

Research and validation

Claude's frozen R2 implementation audit accepted with limits after append-only supersession and duplicate-criterion blockers were fixed. Grok independently accepted the five-record design boundary with limits; it did not execute or freeze-audit the final code. Executed tests and native checks are recorded separately. Research dossier · Review and limits · Tests · Native acceptance · Checksums.

Catalogue identity: vr.profile.enterprise-model-release-acceptance. EM-XCT-10 remains a broader, partially covered research contour. Parent models are semantic references; no subtype or whole-parent conformance is asserted.