Home Contact
Universal Substratev1.4
/
For agents Markdown
Appendicesnormative v1.4.0bundle v1.4.18 blocks

Appendix Q. Thirty-two corrective runtime and release conformance fixtures

These fixture IDs continue after Appendix M. Exact fixture bundles provide setup records, canonical input bytes, keys where safe, policy/registry locks, expected codes, output bytes/digests, SQL state, event sequence, and projection state.

Concept & directionLNK

These fixture IDs continue after Appendix M. Exact fixture bundles provide setup records, canonical input bytes, keys where safe, policy/registry locks, expected codes, output bytes/digests, SQL state, event sequence, and projection state.

#Q1. Ledger, receipt, event, and idempotency

IDScenarioExpected code or result
T-297Two streams append concurrently to one logical shard.One gap-free commitSequence and one contiguous receipt chain.
T-298Transaction rolls back after provisional commit-sequence computation.ShardHead does not advance; no committed gap.
T-299Lower commit remains open while a higher append races.Higher append waits on ShardHead.
T-300Publisher crashes after broker acknowledgement.Same event ID/bytes redelivered; consumer applies once.
T-301Consumer receives noncontiguous commitSequence.Halt with RTR-EVENT-COMMIT-GAP.
T-302Logical shard handoff lacks signed bridge.Reject with RTR-LEDGER-SHARD-HANDOFF.
T-303Retry changes expected sequence only.Idempotency equivocation.
T-304Retry changes detached proof set only.Idempotency equivocation.
T-305Unknown-result resolution occurs under another principal.Non-leaking denial.
T-306Same record ID/digest is submitted under another key and stream.Placement conflict; no second append.

#Q2. Proof, checkpoint, cursor, and replay

IDScenarioExpected code or result
T-307Proof signer field changes without resigning.RTR-PROOF-TARGET-MISMATCH.
T-308Proof creation time or key epoch changes.Invalid proof.
T-309COSE protected algorithm disagrees with ProofTarget.RTR-PROOF-ALGORITHM-CONFUSION.
T-310Receipt store identity changes after proof.Invalid store proof.
T-311Merkle implementation duplicates odd leaf.Golden-root mismatch.
T-312CloudEvents shard/sequence differs from canonical event.Quarantine envelope.
T-313Cursor plaintext exposes a private sort value.Privacy conformance failure.
T-314Cursor crosses projection code generation.Reject and restart query.
T-315Cross-shard deliveries are permuted.Same declared deterministic reduction digest.
T-316Empty projection starts from restored nonzero checkpoint.Recovery blocked.
T-317Replay encounters lawful erasure tombstone.Qualified NON_REPRODUCIBLE_BY_POLICY result.
T-318Legacy ledger is sealed and bridged.First v1.4 receipt verifies bridge.
T-319Legacy receipt chain fails pre-cutover audit.Migration blocked; incident opened.

#Q3. Control, dispatch, and executable release proof

IDScenarioExpected code or result
T-320Lease clock ID matches but arbiter boot ID differs.Reject before actuator.
T-321Persisted authority epoch rolls backward after reboot.Latch SAFE.
T-322Exact command duplicate arrives twice.One actuator application; original disposition returned.
T-323Same command sequence carries a different setpoint.Equivocation; fence controller.
T-324Command sequence gap occurs under STRICT_CONTIGUOUS policy.Reject and invoke fallback.
T-325Command is admitted but feedback times out.Admission retained; execution UNKNOWN_FEEDBACK.
T-326Two workers consume one dispatch nonce.Exactly one enters DISPATCHING.
T-327Social-agent runtime submits an R5 action.Action type is structurally unavailable.
T-328Fixture manifest omits input or golden artifact.Release gate fails.

Existing fixtures T-010, T-057, T-058, T-234, T-243, and T-253 are interpreted under the v1.4 proof target, commit sequence, shard head, confidential cursor, and replay rules when a v1.4 profile is declared.