An implementation's conformance claim is meaningless without the contract revision it was tested against. The lm15 pin discipline is adopted verbatim:
- CONTRACT_PIN: each implementation repo carries a file named
CONTRACT_PINcontaining exactly one full 40-hex git SHA of this repo's main branch, plus a trailing newline, nothing else. - Atomic bumps: land the contract commit first (with AUTHORITY-grade evidence), then bump the pin in the same implementation commit as the code change, so every pinned pair of revisions is green. Never bump the pin just to make CI green — the diff between old and new pin is part of the review.
- The claim: "conforms" =
harness/check.py --shim <name>exits 0 at the pinned SHA, stated as grade + profile + pin. For a grade-2 engine the profile names how it binds and serves entries (e.g. "grade 2, declared-tier profile, pinabc…"); for a grade-1 library the profile part names the profiles itsprofile_checkop implements — a hold-only library executes nothing, so it claims checkable profiles, not served ones. Reports regenerate; the pin is the durable part of the claim.
| implementation | language | grade | profile | pin | status |
|---|---|---|---|---|---|
| programir-contract reference shim | python | 1 (+node_execute) | checks declared-tier | (in-repo) | green 81/81 incl. exec + record + floor families (v0.5, D-042 point 6) + the contract-sync wave, node_set {0.1,0.2,0.3,0.4,0.5} (2026-08-12) |
| programir-go | go | 1 (+node_execute) | checks declared-tier | ce0d6e87293579537cc2a92ae6f578cd9c53d951 |
green 82/82 incl. the exec + record + floor families and the D-051 field-record amendment; node_set {0.1,0.2,0.3,0.4,0.5}. Provenance note: the v0.4/v0.5 catch-up and the engine consulted the reference implementation (recorded in the repo README) — the clean-room claim now covers only the pre-D-041 hold layer (2026-08-25) |
| programir-ts | typescript | 1 | checks declared-tier | 8a87e4f7dc385f3940fec75ccb2f10a7cb1fbd9c |
lags at node_set {0.1,0.2,0.3} — pinned pre-D-041; the v0.4 record family (cases/node-set/record/) and the v0.5 floor family (cases/node-set/floor/) are unmet; catch-up pending. Last green claim: 43/43 at the pin (2026-08-10) |
| dspy-Python | python | 1 (+node_execute) | checks declared-tier | 4857708ef172ce0714f74c0973da5b0946f972a2 |
green 82/82 incl. the D-051 field-record amendment (ap-17: prefix absent, constraint in shape) atop the v0.5 families; node_set {0.1,0.2,0.3,0.4,0.5}; pin bumped atomically with the dspy D-051 sync commit (2026-08-20) |
Grade-2 claims additionally require passing the adapter-ir contract corpus and the lm15-contract harness — this repo does not re-test the lower layers.