Imports MUST point one way: the engine imports nothing of the library; governance imports the engine; the logical schema imports governance and the engine; the physical schema imports the logical schema, governance and the engine; the lifecycle (what changes a database from one physical schema to the next) imports the physical and logical schemas, governance and the engine; a dialect imports the physical and logical schemas, governance and the engine; an extension of SQL imports the lifecycle as well imports the physical and logical schemas, governance and the engine; a model and an extension that needs no database import governance and the engine, and a model may also import the models it requires (0028-modules FR-006), the imports among models making no cycle; and the command line imports any of them. An import that climbs, or reaches around, MUST be a finding.
Enforced (check): .github: cd commons/data && bun run verify — suite/layers.test.ts: the real tree has no finding of the layers check, and verify runs the check against its baseline; suite/layers.test.ts: an import that climbs is layers/above, and one that reaches around is layers/around; suite/layers.test.ts: an extension does not import another unit of its own class, and a suite and the command line import what they need
Proved by: data/suite/layers.test.ts
Written in: data/engine/api.ts, data/governance/api.ts, data/sql/physical/api.ts, data/tools/layers.ts
Tests: passed: suite/layers.test.ts the real tree has no finding of the layers check, and verify runs the check against its ba; passed: suite/layers.test.ts an extension does not import another unit of its own class, and a suite and the command li; passed: suite/layers.test.ts an import that climbs is layers/above, and one that reaches around is layers/around
Cited by: Arca, the party model