Commons (2 of 6)
8 specifications, 121 requirements. All libraries
0011 Documentation
| Requirement | Mechanism | Who | Note |
|---|---|---|---|
FR-001 | check | bun run verify | conventions.test.ts: the name and ./docs, the dependencies exact and the root package's, no IFC TypeScript dependency, and nothing outside commons/docs but commons/docs.config.ts imports it |
FR-002 | check | bun run verify | the compiler of the package; conventions.test.ts: what each file imports, no any, no non-null assertion, @module and TSDoc |
FR-003 | check | bun run verify | check.test.ts: check writes nothing in the checkout and exits 1 on a finding; two builds give the same bytes; config.test.ts: the commands, the search for docs.config.ts and exit 2 on a bad configuration |
FR-004 | check | bun run verify | conventions.test.ts: commons has no README.md and the site reads only commons' TypeScript and the spec kit |
FR-005 | check | bun run verify | about.test.ts: every package has about.ts naming its areas, no entry point exports it, and --check holds its folders, commands and rules to the code |
FR-006 | check | bun run verify | api.test.ts: the module comment, @remarks, @example, @see, @limits and the tags of an export, read from a fixture |
FR-007 | review | 0011-documentation FR-006 | A reviewer checks that a change to code changes the documentation of its module in the same commit (AGENTS.md says so) |
FR-008 | review | 0011-documentation FR-006 | A reviewer checks that a fact with a shape is a typed value; about.test.ts holds the ones about.ts keeps |
FR-009 | check | bun run verify | site.test.ts: the four sections, the capability cards and an area's limits on the site made from commons |
FR-010 | check | bun run verify | api.test.ts: exports, aliases, namespaces, kinds, signatures and pages by source file, from a fixture |
FR-011 | check | bun run verify | links.test.ts: commons, bare and FR citations become links; another repository's stays text |
FR-012 | check | bun run verify | links.test.ts: {@link} in an area and across areas, and an unknown name found |
FR-013 | check | bun run verify | lenses.test.ts: a lens is a value of Lens that reads what is its library\'s and makes its pages after the order it is given |
FR-014 | check | bun run verify | lenses.test.ts: what a lens cannot describe is a finding of the build, which names the entity |
FR-015 | check | bun run verify | specs.test.ts: a specification's page, its anchors and enforcement, the register and the matrix |
FR-016 | check | bun run verify | markdown.test.ts: every construct of the subset, and anything else shown as its text |
FR-017 | check | bun run verify | html.test.ts: relative links only, nothing from another host, the white reading area; the layout at 360 pixels is reviewed on the published site |
FR-018 | check | bun run verify | check.test.ts: each finding broken in a fixture and named |
FR-019 | check | bun run verify | golden.test.ts: the fixtures' HTML is the committed HTML |
FR-020 | check | bun run verify | workflow.test.ts: docs.yml tests and checks on pull requests and publishes from main with GitHub's Pages actions |
FR-021 | check | bun run verify | package.test.ts: the root package's ./docs and ifc-docs, the command registers the hook before cli.ts; consumer.test.ts: the packed package builds a repository |
FR-022 | check | bun run verify | workflow.test.ts: ifc-typescript.yml's git-dependency job runs the smoke test of IFC TypeScript on three systems with Bun and Node 26, and no workflow makes a release |
FR-023 | check | bun run verify | config.test.ts: a configuration checked into its resolved form, every problem named, found from the working folder up to the repository's root; check.test.ts: commons' configuration builds commons' site |
FR-024 | check | bun run verify | plain-kit.test.ts: both requirement forms, a requirement over two lines, reviewed.tsv, the constitution's page, and a specification two kits hold |
FR-025 | check | bun run verify | links.test.ts: the own prefix and digits, a linked repository's citation to its site, a text-only one, and a possessive qualifier |
FR-026 | check | bun run verify | conventions.test.ts: what ./docs and ifc-docs reach imports no data library and no lens; lenses.test.ts: the lenses as values of Lens |
FR-027 | check | bun run verify | fixture-repo.test.ts: a fixture repository with no about.ts and a plain spec kit builds with no finding |
FR-028 | check | bun run verify | twins.test.ts: every block and inline has a Markdown form, links go to twins, the same page gives the same text; the index for a program; a site is written with a .md beside each .html and llms.txt |
FR-029 | check | bun run verify | layered-lens.test.ts: the layers page, a page for each model, concept and code list, registers and JSON; links resolve and sources are links to lines; the data models are on commons' own site with no finding |
FR-030 | check | bun run verify | pending |
FR-031 | check | bun run verify | library-site.test.ts: a module comment after a // header, kit and area folders, a page and an API for every library, specifications grouped by library |
FR-032 | check | bun run verify | guides.test.ts: a guide that cannot be read is a finding, the sections are in order, every section has its guides with links resolved |
FR-033 | check | bun run verify | guides.test.ts: the library map and the imports of each library are read from the sources |
FR-034 | check | bun run verify | theme.test.ts: dark tokens for the system and for a choice, the button and the script that sets the theme first, the keyboard shortcuts and the print style |
FR-035 | check | bun run verify | explorers.test.ts: the trace under a requirement, the layers of a library, the releases page, and the search filter |
FR-036 | check | bun run verify | newcomer.test.ts: five newcomer questions answered from the site, retired names and history words found, none on commons' site |
FR-037 | check | bun run verify | highlight.test.ts: each language cut into tokens with its colour for both schemes, the same runs every time, and the diagram drawn into the page |
FR-038 | check | bun run verify | ai-guides.test.ts: the AI guides have the headings and a prompt block, and every path, repoctl command, script and specification they name exists |
FR-039 | check | bun run verify | specs.test.ts: the matrix is split by library within the row budget; guides.test.ts: the sections, Programs among them |
FR-040 | check | bun run verify | book.test.ts: commons' five volumes of the Commons Manuals have chapters, anchors that resolve, and no matrix or register, and the same pages give the same files |
FR-041 | check | bun test ./tests/ | commons-site-evidence.test.ts: commons' configuration gives the evidence: the results folder, the GitHub snapshot in it, and the issues of data with their scopes; check.test.ts in commons/docs: the site of commons has the Quality section and the issues of data |
FR-042 | check | bun test ./tests/ | commons-site-evidence.test.ts: the workflow site runs the tests of every library and of the repository on main, keeps each report, fetches the open issues and publishes the site whether or not a test failed |
0012 The ontology in TypeScript
| Requirement | Mechanism | Who | Note |
|---|---|---|---|
FR-001 | review | 0032-libraries-by-concern FR-010 | kept by the library rdf: rdf 0001-rdf FR-001 |
FR-002 | review | 0032-libraries-by-concern FR-010 | kept by the library rdf: rdf 0001-rdf FR-002 |
FR-003 | review | 0032-libraries-by-concern FR-010 | kept by the library rdf: rdf 0001-rdf FR-003 |
FR-004 | review | 0032-libraries-by-concern FR-010 | kept by the library rdf: rdf 0001-rdf FR-004 |
FR-005 | review | 0032-libraries-by-concern FR-010 | kept by the library rdf: rdf 0001-rdf FR-005 |
FR-006 | review | 0032-libraries-by-concern FR-010 | kept by the library rdf: rdf 0001-rdf FR-006 |
FR-007 | review | 0032-libraries-by-concern FR-010 | kept by the library rdf: rdf 0001-rdf FR-007 |
FR-008 | check | bun test ./tests/ | Ontology: the modules import only the kernel's RDF and one another, list their files, and no .ttl is under commons/ontology |
FR-009 | check | bun test ./tests/ | Ontology: no IRI is written as free text in a module; the code lists are the tools' unions |
FR-010 | check | bun test ./tests/ | Ontology: tsc 7 refuses copies with a missing field, a wrong range and a wrong class; Generator: the rules a type cannot state are named and nothing is written |
FR-011 | check | bun test ./tests/ | Generator: packaging.auto.ttl is what the modules make, says its generator and is the same bytes twice |
FR-012 | check | bun test ./tests/ | Ontology: source_sha256 is the SHA-256 of the canonical N-Triples, and a comment changes no generated file |
FR-013 | none | a one-time comparison when the Turtle was converted (7 files, 2874 triples, reported in the commit that converted it); the Turtle it was compared with is deleted in that commit | |
FR-014 | check | bun test suite/ | mizan.test.ts: a term with no record is found and fails whatever the baseline holds; every term of the packaging ontology and of Mizan's vocabulary has a record; the mappings name terms of the pinned schema.org import (the compiler) |
FR-015 | check | bun test suite/ | mizan.test.ts: a code list of 5,000 entries is written to a folder and tsc 7 checks it, with its key type, within 30 seconds |
FR-016 | check | bun test ./tests/ | tests/commons-mizan-ontology.test.ts: the generated Turtle names owl:versionInfo and owl:versionIRI; rdflib reads the version IRI back; mizan.test.ts: the kernel's OwlOntology takes a version IRI |
0013 ACME certificates by DNS-01
| Requirement | Mechanism | Who | Note |
|---|---|---|---|
FR-001 | review | 0032-libraries-by-concern FR-010 | kept by the library net: 0001-net FR-008 |
FR-002 | review | 0032-libraries-by-concern FR-010 | kept by the library net: 0001-net FR-009 |
FR-003 | review | 0032-libraries-by-concern FR-010 | kept by the library net: 0001-net FR-010 |
FR-004 | review | 0032-libraries-by-concern FR-010 | kept by the library net: 0001-net FR-011 |
FR-005 | review | 0032-libraries-by-concern FR-010 | kept by the library net: 0001-net FR-012 |
FR-006 | review | 0032-libraries-by-concern FR-010 | kept by the library net: 0001-net FR-013 |
FR-007 | review | 0032-libraries-by-concern FR-010 | kept by the library net: 0001-net FR-014 |
FR-008 | review | 0032-libraries-by-concern FR-010 | kept by the library net: 0001-net FR-015 |
0014 WebAuthn for a relying party
| Requirement | Mechanism | Who | Note |
|---|---|---|---|
FR-001 | check | bun test suite/ | kernel/cbor.test.ts: RFC 8949 Appendix A vectors read and written back, sorted map keys, an item with its end, each refusal with its byte, a round-trip property |
FR-002 | check | bun test suite/ | kernel/webauthn.test.ts: ES256 and Ed25519 COSE keys read, written, from and to JWK, signatures verified; RS256, a wrong curve, a short coordinate and malformed DER signatures refused |
FR-003 | check | bun test suite/ | kernel/webauthn.test.ts: the creation and request options as JSON, and the RangeErrors of a short challenge, a long user id and a bad credential id |
FR-004 | check | bun test suite/ | kernel/webauthn.test.ts: registrations by ES256 and Ed25519 authenticators played with Web Crypto, several origins, packed self-attestation checked and a chain taken at none |
FR-005 | check | bun test suite/ | kernel/webauthn.test.ts: wrong challenge, origin, RP ID and type, cross-origin, no UP or UV, BS without BE, malformed CBOR, tpm, a none with a statement, another id, RS256 |
FR-006 | check | bun test suite/ | kernel/webauthn.test.ts: authentications by ES256 and Ed25519 credentials, and a counter that stays 0 |
FR-007 | check | bun test suite/ | kernel/webauthn.test.ts: a flipped or short signature, a counter not going up, wrong challenge, origin, RP ID, type, no UV, another credential or key, a non-DER ES256 signature; authenticator data with extensions |
FR-008 | check | bun test suite/ | kernel/webauthn.test.ts: browser JSON read into the response types and verified, refusals naming the path |
0015 Trace and layers
| Requirement | Mechanism | Who | Note |
|---|---|---|---|
FR-001 | check | bun test suite/ | kernel/trace.test.ts: a finding's key without its line, named by its rule, file and what it is about |
FR-002 | check | bun test suite/ | kernel/trace.test.ts: a baseline written sorted with its comments, read as a set; a new finding and a stale entry each fail |
FR-003 | check | bun test suite/ | kernel/trace.test.ts: a judgement told as plain lines, new findings, stale entries and the summary, no colour |
FR-004 | check | bun test suite/ | kernel/trace.test.ts: a spec's status in both forms, its requirements with their lines, and reviewed.tsv's rows of its own |
FR-005 | check | bun test suite/ | kernel/trace.test.ts: Spec: lines with groups, lists, ranges, whole specs and several lines; not inside a string |
FR-006 | check | bun test suite/ | kernel/trace.test.ts: proofs from literals, constants and arrays of constants in proves([...]), and Proves: lines; FR(3) not read |
FR-007 | check | bun test suite/ | kernel/trace.test.ts: a clean tree, then each rule found on a fixture tree, a Draft spec and a reviewed requirement not unproved, .auto. exempt |
FR-008 | check | bun test suite/ | kernel/trace.test.ts: citations of individuals made by a schema with a spec field, none of another schema's, an uncited term found |
FR-009 | check | bun test suite/ | kernel/trace.test.ts: placements by one path, a home naming files and literal characters; unclassified and a tie found |
FR-010 | check | bun test suite/ | kernel/trace.test.ts: imports of every form resolved; above and around found with both files and rungs; same rung and packages not |
FR-011 | check | bun test suite/ | runtime/trace.test.ts: a fixture tree on disk read; its findings held against a baseline written, passing, then failing when stale |
FR-012 | check | bun test suite/ | mizan-harness-requests.test.ts: Spec: and Proves: lines are read in block comments (a line with an asterisk, a one-line block), and a string or a comment after code is not read; the trace check traces a file whose only citation is in a block comment |
0016 The ladder
| Requirement | Mechanism | Who | Note |
|---|---|---|---|
FR-001 | check | bun test ./tests/ | Mizan ontology: the nine rungs are individuals of mz:Rung with number, purpose, required and rely-on edges |
FR-002 | check | bun test ./tests/ | Mizan ontology: rungs 0 to 7 are required, rung 8 is optional and relies on nothing |
FR-003 | check | bun test ./tests/ | Mizan ontology: a rung relies only on rungs below it, and no rung relies on rung 8 |
FR-004 | none | Planned, Phase 2 and 3 of issue #10: the Rung class and the generator check are not built yet | |
FR-005 | none | Planned, Phase 2 and 3 of issue #10: the Rung class and the generator check are not built yet | |
FR-006 | none | Planned, Phase 2 and 3 of issue #10: the Rung class and the generator check are not built yet | |
FR-007 | none | Planned, Phase 2 and 3 of issue #10: the Rung class and the generator check are not built yet | |
FR-008 | check | bun test ./tests/ | Mizan ontology: every rung has one kind of mz:RungKind, rungs 0 to 7 required, 8 optional, 9 observer and 10 environment |
FR-009 | check | bun test ./tests/ | Mizan ontology: rung 9 is an observer that may rely on rungs 0 to 7 and no rung relies on it |
FR-010 | check | bun test ./tests/ | Mizan ontology: rung 10 is an environment that relies on no rung and no rung relies on it |
FR-011 | review | 0017-two-languages FR-007 | Whether a harness that claims a regulated domain has rungs 9 and 10 from the day it declares production is judged by a person until the harness declares its domains as typed data (0020-ifccm) |
0017 Two languages: natural language and TypeScript 7
| Requirement | Mechanism | Who | Note |
|---|---|---|---|
FR-001 | none | Planned, Phase 1 and 3 of issue #10: a statement and controls whose checks are the harness's own, not built yet | |
FR-002 | none | Planned, Phase 1 and 3 of issue #10: a statement and controls whose checks are the harness's own, not built yet | |
FR-003 | none | Planned, Phase 1 and 3 of issue #10: a statement and controls whose checks are the harness's own, not built yet | |
FR-004 | none | Planned, Phase 1 and 3 of issue #10: a statement and controls whose checks are the harness's own, not built yet | |
FR-005 | none | Planned, Phase 1 and 3 of issue #10: a statement and controls whose checks are the harness's own, not built yet | |
FR-006 | none | Planned, Phase 1 and 3 of issue #10: a statement and controls whose checks are the harness's own, not built yet | |
FR-007 | none | Planned, Phase 1 and 3 of issue #10: a statement and controls whose checks are the harness's own, not built yet |
0018 Standards first
| Requirement | Mechanism | Who | Note |
|---|---|---|---|
FR-001 | none | Planned, Phase 2 and 3 of issue #10: the basis fields and the standards rules are not built yet | |
FR-002 | none | Planned, Phase 2 and 3 of issue #10: the basis fields and the standards rules are not built yet | |
FR-003 | check | bun test suite/ | mizan.test.ts: a term on a standard that names none is found; every class of Mizan's vocabulary has a basis (tests/commons-mizan-ontology.test.ts). Required by the compiler for Mizan's OntologyTerm only: the kernel's schemas do not yet require it (0012 FR-014) |
FR-004 | check | bun test suite/ | mizan.test.ts: an unaligned term with no justification is found, and the findings are held by the baseline that only shrinks |
FR-005 | check | bun test suite/ | mizan.test.ts: a decision is missing within 90 days (held by the baseline) and overdue after, which fails whatever the baseline holds; run on commons' own folder; ontology-decisions.test.ts: the twelve terms kept unaligned by the owner's decision of 2026-11-17 each have a Decision that names them, and reach the Turtle |
FR-006 | check | bun test suite/ | mizan-newer.test.ts: a newer version than the pin is a finding (FR-014); a Standard's fields are decoded by the importer (mizan-integrations.test.ts) |
FR-007 | none | Planned, Phase 2 and 3 of issue #10: the basis fields and the standards rules are not built yet | |
FR-008 | check | bun test suite/ | mizan-authority.test.ts: a requirement that names a law and no Authority is found, and commons' own specifications pass (FR-015, FR-016) |
FR-009 | check | bun test suite/ | mizan.test.ts: a plan with no Standards considered section named |
FR-010 | none | Planned, Phase 2 and 3 of issue #10: the basis fields and the standards rules are not built yet | |
FR-011 | none | Planned, Phase 2 and 3 of issue #10: the basis fields and the standards rules are not built yet | |
FR-012 | none | Planned, Phase 2 and 3 of issue #10: the basis fields and the standards rules are not built yet | |
FR-013 | check | bun test suite/ | mizan.test.ts: a deprecated term with no replacement is found, and a specification naming a deprecated term is found saying what replaces it |
FR-014 | check | bun test suite/ | mizan-newer.test.ts: a real local HTTP server serves the pinned bytes (no finding) and then other bytes (one finding with both hashes); a manifest with no latest is not read |
FR-015 | check | bun test suite/ | mizan-authority.test.ts: the convention, what a citation of law is, and the covering of a citation by an authority, each in both directions |
FR-016 | check | bun test suite/ | mizan-authority.test.ts: the three findings of mizan/authority-citation, and commons' own specifications read for real |
FR-017 | check | bun test suite/ | mizan-newer.test.ts: the baseline holds a finding and goes stale when it is fixed, a URL that cannot be fetched exits 2 naming it, and check.ts and import.ts --check run with the network unreachable |