Annex D — Deterministic Test Vectors

This annex defines deterministic reference vectors supporting validation of canonical serialization, rule identity derivation, deterministic replay equivalence, and conformity artifact hashing.

1. Hashing Requirements

• All hashing operations SHALL use SHA-256 as defined in FIPS 180-4.
• All canonical forms SHALL be encoded using UTF-8 without BOM.
• No additional whitespace SHALL be introduced beyond canonical form.
• Hash computation SHALL operate exclusively on canonical byte sequences.

2. Canonical Serialization Vector

{"artifact":{"decision":"approve"},"context":{"a":1,"b":2},"expected":{"decision":"approve","state":"valid"},"input":{"x":3,"y":9},"metadata":{"system":"demo","timestamp":"2026-01-01T00:00:00Z","version":"1.0"}}

EVIDENCE_HASH_A1 = SHA256(canonical UTF-8 byte sequence above)

3. Rule Identity Vector

{"decision_logic":{"else":"deny","if":"input.age >= min_age","then":"approve"},"min_age":18,"rule":"min-age-check"}

RULE_HASH_B1 = SHA256(canonical UTF-8 byte sequence above)

4. Replay Equivalence Vector

(recomputed_evidence_hash == EVIDENCE_HASH_A1) AND
(resolved_rule_hash == RULE_HASH_B1) AND
(recomputed_decision == "approve") AND
(recomputed_state == "valid")

Replay SHALL evaluate TRUE only if all conditions are satisfied.

5. Artifact Hash Vector

ARTIFACT_HASH_D1 = SHA256(canonical_conformity_artifact_structure)

6. Conformance Condition

An implementation SHALL be considered Trust-State conformant under this annex only if all canonical forms, hash derivations, and replay evaluations produce byte-identical and deterministic results.