INTERPLANE / Developer documentation

Conformance

Trace INTERPLANE conformance, refusals and reported results to source-pinned fixtures and evidence, including failed and planned stages.

Evidence before a support claim

The canonical conformance directory defines its fixtures and runner instructions. The adapter guide explains how the reference is checked. Follow those pinned commands rather than replacing expected verdicts with newly generated success.

The source STATUS snapshot reports 106 / 106 conformance cases. 106/106 (verdicts byte-identical to `conformance/expected/verdicts.json`, which the Python runner also produced; CI requires exactly 106)

These are source-reported results, not a new execution by the website. A failing or blocked Spark run remains failing or blocked in the source record below. Cross-check Versioned Status, STATUS.md and the stage reports before claiming qualification.

The small offline exercise is a useful first observation, not a replacement for adapter conformance, failure controls or a live deployment gate.

Source and verification

Status snapshot: 68c00986b4bbb9e91a0a1efb11973c9253ecb0b6. Generated 2026-10-30T04:07:09Z. Raw facts.

Spark verification: NO VERDICT The Spark has not published a verdict for this commit yet.

A successful reference example is not the Spark verdict. Planned work is not implemented support. Versioned status and canonical STATUS.md retain those distinctions.