The library ontology MUST hold the ontologies of commons as typed values over the library rdf: Mizan (mz), IFCCM, IFQS, IFR, the audit of packaging and the software supply chain, each a folder of src/ with a mod.ts, and the data of the standards they cite.
Enforced (check): .github: cd commons/ontology && bun run verify — the package is built, inspected and packed, the suite runs, and the library's own trace and spec kit are held
Every class, property and code list of an ontology MUST be stated once in its module, and the generators of Turtle, RDF/XML, SHACL and JSON Schema MUST be made from those values, not from a copy (commons 0012-ontology).
Enforced (check): .github: cd commons/ontology && bun test suite/ — ifccm-ontology.test.ts: the classes and properties of IFCCM are values of the library, and the tests of the other ontologies in commons/ts/tests read them by package name
The ontologies MUST import only core and rdf by package name and each other by relative path, so that an ontology is read without a harness.
Enforced (check): .github: cd commons/ontology && bun test suite/ — ontology-boundaries.test.ts: the modules import only core and rdf and the library's own modules
The library MUST be published to npm as compiled modules with their declarations, one entry for the package (., which names the ontologies as namespaces) and one for each module.
Enforced (check): .github: cd commons/ontology && bun run verify — the package is built, inspected and packed by tools/pack.ts; tests/commons-packages.test.ts installs the tarball, runs every entry on Node 26 and Bun and type-checks a consumer
The decision to publish the ontologies as one library is 0032-libraries-by-concernFR-008: the ontology of IFR extends the one of IFQS, which extends Mizan's, so no one of them could be a file of the library that uses it without a cycle.