The reference checker is part of loopmath. It checks a document against the JSON Schema of its version and against every numbered rule. A clean result does not prove a document meets every requirement in the field descriptions: see what the checker does not test.

validate

Output
  • Each finding has a level, a rule code, a JSON path and a message. The terminal shows the first eight per file; --json carries all of them.
  • Given several files, it also runs the cross-file part of E194: documents in one slate share a task and a base commit.
  • Warnings never fail a file.

JSON output

migrate

Upgrades 0.1 and 0.2 documents to 0.3. See Versions in practice.
  • With --out DIR, each result is written to DIR as NAME.ocp.json. It refuses to write over an input.
  • Without --out, a single result goes to standard output. Several files need --out, or --json to get every migrated document in one object.
  • A result with a conformance error is reported and never written.

In CI

.github/workflows/ocp.yml

Schema only

The JSON Schemas (draft 2020-12) are in the specification repository, one per version. Any validator can check a document against them:
A schema check alone misses the numbered rules: references between entities, cycles, sums and the configuration id. A document that passes the schema can still fail loopmath ocp validate.

Privacy