The offline trace MUST read only files the harness keeps and the repository's Git: the change requests as a JSON file (--issues, a list of objects with number and, where kept, title and body), the citations of the ontology's terms (--terms, a JSON file, or a module loaded by the file: URL of its path so that it loads on Windows, that exports terms as objects with term, cites and file or as the records of an audit of terms; commons for commons' own ontologies), the rungs with their homes (--rungs, export const rungs, each with id, label, provedBy and, for the trace, homes), the cases of a quality record (--runs, 0021-ifqs) and the specifications (--specs); --trace MUST read --terms as well, so that the chain of a Done when follows a harness's own terms (amended 2026-11-18).
Enforced (check): .github: cd commons/mizan && bun test suite/ — mizan-harness-requests.test.ts: the change requests as JSON, the terms as JSON or as a module loaded by the file URL of a path with a space (audit records too), the rungs with homes and the specs are read; a missing file, a module with no terms and a bad format are named; --trace reads --terms
Proved by: mizan/suite/mizan-harness-requests.test.ts
Tests: passed: suite/mizan-harness-requests.test.ts the offline trace follows each capability's requirements to terms, code and tests on each ; passed: suite/mizan-harness-requests.test.ts the terms come from a module loaded by its file URL, as audit records, and the usage error
Cited by: changes/terms-file, Mizan