v166.8 — DecoderPromotionReceipt
Overview
v166.8 completes the v166.x QLDPC / Hashing-Bound Code Receipts governance arc by introducing the terminal promotion-governance artifact:
DecoderPromotionReceipt
This release provides a deterministic, hash-bound mechanism for declaring decoder promotion eligibility and receipt-chain promotion decisions while preserving the canonical baseline decoder and enforcing all upstream safety requirements.
Promotion is treated as a governance decision.
Promotion is not treated as source replacement.
Promotion is not treated as runtime activation.
Promotion is not treated as proof of correctness.
Promotion is not treated as authority.
The sacred decoder remains the oracle.
The promoted candidate remains bound by deterministic receipts.
Added
Promotion Governance Artifacts
DecoderPromotionUpstreamBindingDecoderPromotionEligibilityGateDecoderPromotionTargetDecoderPromotionDecisionDecoderPromotionScopeDecoderPromotionRuntimeBoundaryDecoderPromotionRollbackBindingDecoderPromotionAuditBoundaryDecoderPromotionAuthorityBoundaryDecoderPromotionReceipt
Structured Errors
DecoderPromotionErrorCodeDecoderPromotionError
Public Builders
build_decoder_promotion_upstream_bindingbuild_decoder_promotion_eligibility_gatebuild_decoder_promotion_targetbuild_decoder_promotion_decisionbuild_decoder_promotion_scopebuild_decoder_promotion_runtime_boundarybuild_decoder_promotion_rollback_bindingbuild_decoder_promotion_audit_boundarybuild_decoder_promotion_authority_boundarybuild_decoder_promotion_receipt
Public Validators
validate_decoder_promotion_upstream_bindingvalidate_decoder_promotion_eligibility_gatevalidate_decoder_promotion_targetvalidate_decoder_promotion_decisionvalidate_decoder_promotion_scopevalidate_decoder_promotion_runtime_boundaryvalidate_decoder_promotion_rollback_bindingvalidate_decoder_promotion_audit_boundaryvalidate_decoder_promotion_authority_boundaryvalidate_decoder_promotion_receipt
Governance Model
Promotion is now bound to the complete receipt chain:
CanonicalDecoderBaselineReceipt
→ DecoderCandidateManifest
→ DecoderReplayEquivalenceReceipt
→ DecoderOptimizationContract
→ DecoderFastPathEquivalenceReceipt
→ DecoderImplementationBoundaryReceipt
→ DecoderBenchmarkLadderReceipt
→ DecoderRollbackReceipt
→ DecoderPromotionReceipt
A promotion receipt is considered valid only when every required upstream receipt is present, valid, and hash-bound.
Promotion Rules
Promotion now requires:
- Replay equivalence
- Optimization contract validation
- Fast-path equivalence
- Implementation boundary validation
- Benchmark ladder validation
- Rollback readiness
- Promotion eligibility gate satisfaction
Promotion does not require:
- Runtime activation
- Decoder execution
- Source replacement
- Benchmark execution
- Rollback execution
Safety Guarantees
v166.8 explicitly enforces:
source_replacement_allowed = false
baseline_source_mutation_allowed = false
runtime_activation_performed = false
promotion_execution_performed_by_receipt = false
The receipt may declare promotion.
The receipt may not perform promotion.
The receipt may not mutate source code.
The receipt may not activate runtime execution.
Semantic Hardening
Added declaration guards preventing promotion overreach, including:
- silent decoder replacement
- source replacement
- runtime activation
- benchmark marketing
- benchmark-as-proof
- replay-equivalence-as-proof
- rollback bypass
- hardware authority
- ML decoder authority
- probabilistic promotion
- global correctness claims
- QEC advantage claims
- baseline mutation
- undeclared approximation policies
Legitimate receipt-chain promotion phrases remain allow-listed.
Determinism
The promotion receipt uses:
- canonical JSON serialization
- SHA-256 receipt identities
- self-hash exclusion
- exact bool validation
- exact integer validation
- deterministic ordering
- child-before-aggregate validation
- aggregate recomputation rather than trusted fields
All promotion-safe flags are recomputed.
No aggregate state is trusted.
Validation
Promotion Receipt Tests
tests/test_decoder_promotion_receipts.py
220 passed
Upstream Receipt Validation
tests/test_decoder_rollback_receipts.py
140 passed
tests/test_decoder_benchmark_ladder_receipts.py
44 passed
tests/test_decoder_implementation_boundary_receipts.py
121 passed
tests/test_decoder_fast_path_equivalence_receipts.py
12 passed
tests/test_decoder_optimization_contracts.py
10 passed
tests/test_decoder_replay_equivalence_receipts.py
16 passed
tests/test_decoder_candidate_manifests.py
84 passed
tests/test_canonical_decoder_baseline_receipts.py
38 passed
Full Suite
19048 passed
Hash Stability
Validated under:
PYTHONHASHSEED=0
PYTHONHASHSEED=1
with identical receipt identities.
Boundary Verification
Verified:
git diff --name-only -- src/qec/decoder/
Result:
(no modified decoder files)
No files under:
src/qec/decoder/
were modified.
What This Release Does NOT Do
v166.8 does not:
- replace decoder source code
- activate runtime execution
- execute decoder workloads
- execute benchmarks
- execute rollback
- perform git operations
- install dependencies
- mutate repository state
- prove correctness
- prove global correctness
- prove QEC advantage
- grant hardware authority
- grant ML authority
Promotion remains a deterministic governance receipt.
Not an execution surface.
Arc Completion
v166.8 completes the planned v166.x governance chain:
v166.0 → CanonicalDecoderBaselineReceipt
v166.1 → DecoderCandidateManifest
v166.2 → DecoderReplayEquivalenceReceipt
v166.3 → DecoderOptimizationContract
v166.4 → DecoderFastPathEquivalenceReceipt
v166.5 → DecoderImplementationBoundaryReceipt
v166.6 → DecoderBenchmarkLadderReceipt
v166.7 → DecoderRollbackReceipt
v166.8 → DecoderPromotionReceipt
The QLDPC / Hashing-Bound Code Receipts governance arc is now complete.
Gremlin Notes
- Missing targets now raise proper promotion errors instead of vanishing into
KeyError. - Escape-sequence goblins (
\n,\r,\t) can no longer smuggle forbidden declarations past the semantic guards. - Promotion targets must bind to the correct upstream receipts;
"trust me bro"is not a cryptographic proof. - Benchmarks remain evidence, not truth.
- Silent decoder replacement remains forbidden.
- Runtime activation remains forbidden.
- The sacred decoder remains untouched.