Conformance Matrix
The Operation Contract (OC-1) defines eighteen gates, C1 through C18. Every package that ships an
./ops surface is run against all of them on every change, and the result is the table below.
The gates are run against built artifacts, not source — the same tarball a consumer installs. That distinction is the point: a contract verified against source proves that the code in the repo is correct, and a contract verified against the build proves that the thing you actually download is. Two of them, C15 and C16, exist specifically to catch the ways those diverge.
A warning is not a pass. A gate that would succeed vacuously — no fixtures to check, no exports to compare — is reported as a warning, because a formality that always succeeds is worse than no gate at all: it converts an unknown into a false assurance. Every open warning is named below with its detail, so there is nothing here you have to take on trust.
{/* START GENERATED CONFORMANCE MATRIX */}
Generated from ga/conformance.json by scripts/generate-conformance-page.mts. Contract version 1.0.0.
12 of 12 packages conformant — 216 gates passing, 0 warning, 0 not applicable, 0 failing.
Legend: ✅ pass · ⚠️ warning · – gate does not apply to this package · ❌ fail.
The matrix
| Package | Domain | C1 | C2 | C3 | C4 | C5 | C6 | C7 | C8 | C9 | C10 | C11 | C12 | C13 | C14 | C15 | C16 | C17 | C18 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
@runstamp/pptx | pptx | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
@runstamp/delimited-data | common | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
@runstamp/docx | docx | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
@runstamp/forms | pdf | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
@runstamp/pdf | pdf | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
@runstamp/mail-artifacts | common | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
@runstamp/provenance | common | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
@runstamp/review-operations | common | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
@runstamp/scientific-publishing | common | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
@runstamp/table-extraction | common | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
@runstamp/technical-publishing | common | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
@runstamp/xlsx | xlsx | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
What each gate checks
| Gate | Checks |
|---|---|
| C1 | Signature |
| C2 | Envelope |
| C3 | Serialization |
| C4 | Errors |
| C5 | Code registry |
| C6 | No-throw |
| C7 | Determinism |
| C8 | Receipt honesty |
| C9 | Locator round-trip |
| C10 | Locator stability |
| C11 | No silent loss |
| C12 | Loss ordering |
| C13 | Export hygiene |
| C14 | Verb vocabulary |
| C15 | Cancellation |
| C16 | API report |
| C17 | Operation identity |
| C18 | Operation coverage |
{/* END GENERATED CONFORMANCE MATRIX */}
How to reproduce this
Nothing on this page is hand-maintained. Clone the repository and run:
pnpm contract:verify
The command prints the same matrix and exits non-zero if any gate fails. ga/conformance.json is
its machine-readable output, and this page is generated from that file — so if the two ever
disagree, the page is wrong and the command is right.
Related
- Operations Reference — every operation, its verb and its codes.
- Troubleshooting — what to do when a gate or an operation fails.