4 specifications, 26 requirements. All libraries
Requirement Mechanism Who Note FR-001check bun run verifysuite/layers.test.ts: every file of the real tree is in a unit and a file in none is layers/unclassified FR-002check bun run verifysuite/layers.test.ts: below may not import above and each unit imports only what its row allows FR-003check bun run verifysuite/layers.test.ts: the package exports the library and its layers FR-004check bun run verifysuite/layers.test.ts: verify runs every check of the library FR-005check bun run verifysuite/layers.test.ts: the release record agrees with the manifest and the package FR-006check bun run verifysuite/layers.test.ts: no source imports a module that reads a file, reaches the network or runs a program
Requirement Mechanism Who Note FR-001check bun run verifysuite/governance.test.ts: tool names and versions are made only by their functions and compared by their numbers FR-002check bun run verifysuite/governance.test.ts: a tool is defined or refused with every reason FR-003check bun run verifysuite/governance.test.ts: the pin policy and the minimum FR-004check bun run verifysuite/governance.test.ts: an artifact has an https address with no credentials, a SHA-256, a format and a folder inside FR-005check bun run verifysuite/governance.test.ts: a tool has bindings and no duplicate binding FR-006check bun run verifysuite/governance.test.ts: no secret in the environment or the program FR-007check bun run verifysuite/governance.test.ts: a catalog refuses duplicates, missing needs, cycles and a program provided twice, and is in order of needs FR-008check bun run verifysuite/governance.test.ts: a tool holds no version or hash of a pin, only the id of the pin FR-009check bun run verifysuite/governance.test.ts: other names of a program, refused where they clash
Requirement Mechanism Who Note FR-001check bun run verifysuite/logical.test.ts: a dialect declares its guarantees as data FR-002check bun run verifysuite/logical.test.ts: meetsIntegrity names every reason a dialect does not meet the control FR-003check bun run verifysuite/logical.test.ts: resolveTools picks the first dialect that can, in the order of needs FR-004check bun run verifysuite/logical.test.ts: a tool no dialect can carry out is refused with every reason, and a source-building dialect is never chosen FR-005check bun run verifysuite/logical.test.ts: planTools says none, install or replace, and counts a path copy only where policy allows FR-006check bun run verifysuite/logical.test.ts: requirementsFor gives requirements of kind tool that an order of archon is built from FR-007check bun run verifysuite/logical.test.ts: the downloads come from a PinSource, a pin with no download or a version below the minimum is a reason, and the library does not read the ontology
Requirement Mechanism Who Note FR-001check bun run verifysuite/ontology.test.ts: a download for a pinned program on a platform FR-002check bun run verifysuite/ontology.test.ts: the ontology's reason for an unknown, unpinned or not pinned download FR-003check bun run verifysuite/ontology.test.ts: every download given is valid under defineDownload FR-004check bun run verifysuite/ontology.test.ts: no version, address or hash in the sources