Validation Pack: AOR-4, consumer catalog and import resolution

Unit: applied-ontology-readiness Plan section: AOR-4 Decision: ADR-A88, Proposed

Invariant

Every LATTICE document loads with its import closure from a checkout, with no machine-specific configuration, and an applied ontology can reach LATTICE by chaining its own catalog to LATTICE’s.

Test cases

ID Given / When / Then Level +/-
AOR4-01 this repository / check / no problems L1 +
AOR4-02 fixture tree, a imports b / generate, check, load a’s closure from a’s stub / consistent, b’s term present L1 +
AOR4-03 root catalog with b’s entry removed / check, load / drift reported, closure raises L1 -
AOR4-04 entry mapping b’s IRI to a’s file / check / “does not declare it” L1 -
AOR4-05 stub hand-edited / check / exactly one drift problem L1 -
AOR4-06 a imports an IRI nothing declares / check / exactly one unresolved-import problem L1 -
AOR4-07 two files declare one IRI / scan / refused L1 -
AOR4-08 a known-defect entry for a file with no problem / check / stale-entry problem L1 -
AOR4-09 generation run twice / compared / identical L2 +
AOR4-10 Behaviour spec closure through the root catalog / loaded / terms from Foundation, Vocabulary, Quantification, Party, Eligibility, Instrument and Behaviour present L1 +
AOR4-11 an applied ontology in a temporary directory, its own catalog chaining to LATTICE’s by relative path / closure loaded / elg:Condition present L1 +

One command

mise run check:ontology-catalog

Pass: 11 passed, then ontology catalog consistent, 7 known defect(s) reported.

Artefacts to inspect

Adversarial probe (run by the agent)

Making Catalog.lookup ignore nextCatalog failed AOR4-02 and AOR4-11. Disabling the entry-declares-IRI comparison failed AOR4-04. Restoring the file returned 11 passes.

Manual step for the human

Follow Loading LATTICE in Protégé: open ontology/behaviour/spec/behaviour.ttl and confirm the import closure loads with no missing-import prompt, then run the negative control. This settles ADR-A88’s open question on relative nextCatalog support. If it fails, the fallback is full per-directory catalogs, generated by the same tool.

Deliberate non-coverage