K09 · bounded executable evidence infrastructure
Protocol Conformance Results
Direct answer
All published positive fixtures round-tripped exactly and all six negative fixtures produced their declared errors in the K09 reference implementation.
Authority and disclosure boundary. K09 publishes static tools, synthetic fixtures, source-derived event records, signed offline imports, non-certifying traces, redacted procurement structures, and public/protected partition schemas. It does not perform live monitoring, reveal protected topology or credentials, decide awards, certify facilities, authorize operations, or prove factual truth from a signature.
Defined negative behavior
| Case | Expected | Actual | Status |
|---|---|---|---|
| Undefined token | UNDEFINED_TOKEN | UNDEFINED_TOKEN | PASS |
| Truncated compact payload | TRUNCATED_PAYLOAD | TRUNCATED_PAYLOAD | PASS |
| CRC mismatch | CRC_MISMATCH | CRC_MISMATCH | PASS |
| Unsupported version | UNSUPPORTED_VERSION | UNSUPPORTED_VERSION | PASS |
| Duplicate non-repeatable token | DUPLICATE_TOKEN | DUPLICATE_TOKEN | PASS |
| Trailing binary data | TRAILING_DATA | TRAILING_DATA | PASS |
Raw fixture files
- CASE-K09-001 — ascii-enum (38 bytes)
- CASE-K09-001 — json-int (19 bytes)
- CASE-K09-001 — cbor-int (8 bytes)
- CASE-K09-001 — compact-binary (12 bytes)
- CASE-K09-002 — ascii-enum (27 bytes)
- CASE-K09-002 — json-int (17 bytes)
- CASE-K09-002 — cbor-int (7 bytes)
- CASE-K09-002 — compact-binary (11 bytes)
- CASE-K09-003 — ascii-enum (22 bytes)
- CASE-K09-003 — json-int (17 bytes)
- CASE-K09-003 — cbor-int (7 bytes)
- CASE-K09-003 — compact-binary (11 bytes)
- CASE-K09-004 — ascii-enum (23 bytes)
- CASE-K09-004 — json-int (17 bytes)
- CASE-K09-004 — cbor-int (7 bytes)
- CASE-K09-004 — compact-binary (11 bytes)
- CASE-K09-005 — ascii-enum (26 bytes)
- CASE-K09-005 — json-int (17 bytes)
- CASE-K09-005 — cbor-int (7 bytes)
- CASE-K09-005 — compact-binary (11 bytes)
- CASE-K09-006 — ascii-enum (35 bytes)
- CASE-K09-006 — json-int (18 bytes)
- CASE-K09-006 — cbor-int (7 bytes)
- CASE-K09-006 — compact-binary (11 bytes)
- CASE-K09-007 — ascii-enum (28 bytes)
- CASE-K09-007 — json-int (18 bytes)
- CASE-K09-007 — cbor-int (7 bytes)
- CASE-K09-007 — compact-binary (11 bytes)
- CASE-K09-008 — ascii-enum (23 bytes)
- CASE-K09-008 — json-int (17 bytes)
- CASE-K09-008 — cbor-int (7 bytes)
- CASE-K09-008 — compact-binary (11 bytes)
- CASE-K09-009 — ascii-enum (25 bytes)
- CASE-K09-009 — json-int (17 bytes)
- CASE-K09-009 — cbor-int (7 bytes)
- CASE-K09-009 — compact-binary (11 bytes)
- CASE-K09-010 — ascii-enum (24 bytes)
- CASE-K09-010 — json-int (17 bytes)
- CASE-K09-010 — cbor-int (7 bytes)
- CASE-K09-010 — compact-binary (11 bytes)
- CASE-K09-011 — ascii-enum (17 bytes)
- CASE-K09-011 — json-int (17 bytes)
- CASE-K09-011 — cbor-int (7 bytes)
- CASE-K09-011 — compact-binary (11 bytes)
- CASE-K09-012 — ascii-enum (26 bytes)
- CASE-K09-012 — json-int (19 bytes)
- CASE-K09-012 — cbor-int (7 bytes)
- CASE-K09-012 — compact-binary (11 bytes)
Repeatability evidence
Every fixture was encoded five times. All repeated outputs were byte-identical, decoded to the original ordered token sequence, and received a SHA-256 digest. The digest proves equality to the published fixture, not semantic correctness or authority.