Skip to main content

Review a change without making it live

These answers are deterministic read-model proof. They do not create evidence, canonical truth, review approval, a governance decision, promotion, certification, release authority, or backend equivalence.
CasePASS
Questions3/3
Evidence checks9/9
Supportsupported-preview

Separate the currently accepted version from proposals that are ready for review or promotion.

External input files

FilePurposeRoleBytesSHA-256
fixtures/canonical/assertion-evidence-thin-slice.jsonAccepted package, version, assertion, evidence, decision, and promotion baseline.canonical-fixture13,670sha256:ebe489c0b5dbdcc490aca7bf76516d3e988e4eaa49ab172500532f003ef6902d
fixtures/canonical/stage-aware-governance-outcomes-extension.jsonReview-ready, decision-ready, promotion-ready, and blocked proposal states.governed-extension20,372sha256:1b28af7b833a43cfe69d7360d35702b40bcacc9975fddaefbfc5506a06085c62

The case manifest is fixtures/reference-cases/review-change-without-making-it-live.json with digest sha256:b6419a3e523c3a210efc0769b42859154f8d1c7ca4fc702c9e0abc424ed1d696. These identities are taken from the executed suite report, not copied into this page by hand.

1. Which version is currently accepted?

Verified answerVersion 1 remains the accepted state because it is the target of the latest promotion record.

Answer state: answered

Why it matters: A mutable label cannot silently replace the decision and promotion lineage that establishes current state.

Evidence returned by the execution

ProofKindActual runtime valueResult
Current versioncurrent-state"version:compliance-demo-v1"PASS
Current-state derivationboundary"latest-promotion-record"PASS
Promotion establishing current stategovernance"promotion:control-support-001"PASS

The current-promoted-state reference query executed through python-canonical-runtime. Every value above was resolved from the query's actual output and exactly matched the case contract.

Show the complete verified runtime output
{
"packageRef": "package:compliance-demo",
"currentVersionRef": "version:compliance-demo-v1",
"currentVersionState": {
"versionRef": "version:compliance-demo-v1",
"versionLabel": "v1",
"createdAt": "2026-05-02T02:15:00Z",
"includedObjectRefs": [
"assertion:control-support-001",
"evidence:extract-001"
]
},
"previousVersionRef": "version:compliance-demo-v0",
"previousVersionState": {
"versionRef": "version:compliance-demo-v0",
"versionLabel": "v0",
"createdAt": "2026-05-02T02:00:00Z",
"includedObjectRefs": []
},
"promotionRef": "promotion:control-support-001",
"decisionRef": "decision:control-support-001",
"decisionOutcome": "approve",
"sourceProposalRef": "proposal:control-support-001",
"promotedChangeSetRefs": [
"changeset:control-support-001"
],
"promotedAt": "2026-05-02T02:15:00Z",
"promotedBy": "actor:reviewer",
"semanticDiffSummary": {
"created": [
"assertion:control-support-001",
"evidence:extract-001"
],
"changed": [],
"superseded": [],
"conflicts": []
},
"currentStateProof": {
"currentStateDerivation": "latest-promotion-record",
"packageRef": "package:compliance-demo",
"versionRef": "version:compliance-demo-v1",
"decisionRef": "decision:control-support-001",
"promotionRef": "promotion:control-support-001",
"sourceProposalRef": "proposal:control-support-001",
"activeVersionRefs": [
"version:compliance-demo-v1"
],
"activeVersionMatchesLatestPromotion": true,
"preservesPackageVersionDecisionPromotionBoundaries": true
},
"caveats": [
"current state is derived from the latest promotion record, not mutable package truth",
"active package version must match the latest promotion target",
"package, version, decision, and promotion records remain distinct"
]
}

2. What must happen next for Proposal A?

Verified answerProposal A is ready for human review and has no review record yet.

Answer state: answered

Why it matters: The system can identify the next legitimate action without pretending that review already occurred.

Evidence returned by the execution

ProofKindActual runtime valueResult
Proposal identitygovernance"proposal:stage-review-ready-001"PASS
Next governance stagegovernance"review-ready"PASS
No completed reviewgovernance[]PASS

The accepted-vs-proposed-state reference query executed through python-canonical-runtime. Every value above was resolved from the query's actual output and exactly matched the case contract.

Show the complete verified runtime output
{
"packageRef": "package:compliance-demo",
"acceptedState": {
"packageRef": "package:compliance-demo",
"currentVersionRef": "version:compliance-demo-v1",
"currentVersionState": {
"versionRef": "version:compliance-demo-v1",
"versionLabel": "v1",
"createdAt": "2026-05-02T02:15:00Z",
"includedObjectRefs": [
"assertion:control-support-001",
"evidence:extract-001"
]
},
"previousVersionRef": "version:compliance-demo-v0",
"previousVersionState": {
"versionRef": "version:compliance-demo-v0",
"versionLabel": "v0",
"createdAt": "2026-05-02T02:00:00Z",
"includedObjectRefs": []
},
"promotionRef": "promotion:control-support-001",
"decisionRef": "decision:control-support-001",
"decisionOutcome": "approve",
"sourceProposalRef": "proposal:control-support-001",
"promotedChangeSetRefs": [
"changeset:control-support-001"
],
"promotedAt": "2026-05-02T02:15:00Z",
"promotedBy": "actor:reviewer",
"semanticDiffSummary": {
"created": [
"assertion:control-support-001",
"evidence:extract-001"
],
"changed": [],
"superseded": [],
"conflicts": []
},
"currentStateProof": {
"currentStateDerivation": "latest-promotion-record",
"packageRef": "package:compliance-demo",
"versionRef": "version:compliance-demo-v1",
"decisionRef": "decision:control-support-001",
"promotionRef": "promotion:control-support-001",
"sourceProposalRef": "proposal:control-support-001",
"activeVersionRefs": [
"version:compliance-demo-v1"
],
"activeVersionMatchesLatestPromotion": true,
"preservesPackageVersionDecisionPromotionBoundaries": true
},
"caveats": [
"current state is derived from the latest promotion record, not mutable package truth",
"active package version must match the latest promotion target",
"package, version, decision, and promotion records remain distinct"
]
},
"acceptedProposalRef": "proposal:control-support-001",
"proposedStateRefs": [
"proposal:stage-review-ready-001",
"proposal:stage-promotion-ready-001"
],
"proposedStates": [
{
"proposalRef": "proposal:stage-review-ready-001",
"targetPackageRef": "package:compliance-demo",
"baseVersionRef": "version:compliance-demo-v1",
"changeSetRefs": [
"changeset:stage-review-ready-001"
],
"reviewerRefs": [
"actor:reviewer"
],
"validationResultRefs": [
"validation:stage-review-ready-001"
],
"reviewRefs": [],
"decisionRefs": [],
"promotionRefs": [],
"readyStages": [
"review"
],
"blockingOutcomes": [],
"stageOutcome": "review-ready",
"lifecycle": {
"proposal": "open"
},
"semanticDiffSummary": {
"created": [],
"changed": [
"assertion:control-support-001"
],
"superseded": [],
"conflicts": []
}
},
{
"proposalRef": "proposal:stage-promotion-ready-001",
"targetPackageRef": "package:compliance-demo",
"baseVersionRef": "version:compliance-demo-v1",
"changeSetRefs": [
"changeset:stage-promotion-ready-001"
],
"reviewerRefs": [
"actor:reviewer"
],
"validationResultRefs": [
"validation:stage-promotion-ready-001"
],
"reviewRefs": [
"review:stage-promotion-ready-001"
],
"decisionRefs": [
"decision:stage-promotion-ready-001"
],
"promotionRefs": [],
"readyStages": [
"review",
"decision",
"promotion"
],
"blockingOutcomes": [],
"stageOutcome": "promotion-ready",
"lifecycle": {
"proposal": "approved"
},
"semanticDiffSummary": {
"created": [],
"changed": [
"assertion:control-support-001"
],
"superseded": [],
"conflicts": []
}
}
]
}

3. Is Proposal B already current because it was approved?

Verified answerNo. Proposal B is promotion-ready, but it has no promotion record and Version 1 remains current.

Answer state: answered

Why it matters: Approval and promotion remain different events, preventing proposed state from masquerading as accepted reality.

Evidence returned by the execution

ProofKindActual runtime valueResult
Proposal B stagegovernance"promotion-ready"PASS
No promotion recordgovernance[]PASS
Accepted version remains Version 1current-state"version:compliance-demo-v1"PASS

The accepted-vs-proposed-state reference query executed through python-canonical-runtime. Every value above was resolved from the query's actual output and exactly matched the case contract.

Show the complete verified runtime output
{
"packageRef": "package:compliance-demo",
"acceptedState": {
"packageRef": "package:compliance-demo",
"currentVersionRef": "version:compliance-demo-v1",
"currentVersionState": {
"versionRef": "version:compliance-demo-v1",
"versionLabel": "v1",
"createdAt": "2026-05-02T02:15:00Z",
"includedObjectRefs": [
"assertion:control-support-001",
"evidence:extract-001"
]
},
"previousVersionRef": "version:compliance-demo-v0",
"previousVersionState": {
"versionRef": "version:compliance-demo-v0",
"versionLabel": "v0",
"createdAt": "2026-05-02T02:00:00Z",
"includedObjectRefs": []
},
"promotionRef": "promotion:control-support-001",
"decisionRef": "decision:control-support-001",
"decisionOutcome": "approve",
"sourceProposalRef": "proposal:control-support-001",
"promotedChangeSetRefs": [
"changeset:control-support-001"
],
"promotedAt": "2026-05-02T02:15:00Z",
"promotedBy": "actor:reviewer",
"semanticDiffSummary": {
"created": [
"assertion:control-support-001",
"evidence:extract-001"
],
"changed": [],
"superseded": [],
"conflicts": []
},
"currentStateProof": {
"currentStateDerivation": "latest-promotion-record",
"packageRef": "package:compliance-demo",
"versionRef": "version:compliance-demo-v1",
"decisionRef": "decision:control-support-001",
"promotionRef": "promotion:control-support-001",
"sourceProposalRef": "proposal:control-support-001",
"activeVersionRefs": [
"version:compliance-demo-v1"
],
"activeVersionMatchesLatestPromotion": true,
"preservesPackageVersionDecisionPromotionBoundaries": true
},
"caveats": [
"current state is derived from the latest promotion record, not mutable package truth",
"active package version must match the latest promotion target",
"package, version, decision, and promotion records remain distinct"
]
},
"acceptedProposalRef": "proposal:control-support-001",
"proposedStateRefs": [
"proposal:stage-review-ready-001",
"proposal:stage-promotion-ready-001"
],
"proposedStates": [
{
"proposalRef": "proposal:stage-review-ready-001",
"targetPackageRef": "package:compliance-demo",
"baseVersionRef": "version:compliance-demo-v1",
"changeSetRefs": [
"changeset:stage-review-ready-001"
],
"reviewerRefs": [
"actor:reviewer"
],
"validationResultRefs": [
"validation:stage-review-ready-001"
],
"reviewRefs": [],
"decisionRefs": [],
"promotionRefs": [],
"readyStages": [
"review"
],
"blockingOutcomes": [],
"stageOutcome": "review-ready",
"lifecycle": {
"proposal": "open"
},
"semanticDiffSummary": {
"created": [],
"changed": [
"assertion:control-support-001"
],
"superseded": [],
"conflicts": []
}
},
{
"proposalRef": "proposal:stage-promotion-ready-001",
"targetPackageRef": "package:compliance-demo",
"baseVersionRef": "version:compliance-demo-v1",
"changeSetRefs": [
"changeset:stage-promotion-ready-001"
],
"reviewerRefs": [
"actor:reviewer"
],
"validationResultRefs": [
"validation:stage-promotion-ready-001"
],
"reviewRefs": [
"review:stage-promotion-ready-001"
],
"decisionRefs": [
"decision:stage-promotion-ready-001"
],
"promotionRefs": [],
"readyStages": [
"review",
"decision",
"promotion"
],
"blockingOutcomes": [],
"stageOutcome": "promotion-ready",
"lifecycle": {
"proposal": "approved"
},
"semanticDiffSummary": {
"created": [],
"changed": [
"assertion:control-support-001"
],
"superseded": [],
"conflicts": []
}
}
]
}

What this proof means

All 3 questions executed successfully. Their underlying reference queries exactly matched their declared expectations, and all 9 answer/evidence checks resolved against actual runtime output.

What this does not prove

These answers are deterministic read-model proof. They do not create evidence, canonical truth, review approval, a governance decision, promotion, certification, release authority, or backend equivalence.