IF Commons GitHub

Commons (6 of 6)

3 specifications, 95 requirements. All libraries

0036 Distribution

RequirementMechanismWhoNote
FR-001checkbun test suite/metapackages.test.ts: AGENTS.md states the rule of consuming commons by a published package and no other way
FR-002checkbun test suite/hygiene.test.ts: each form the rule forbids is a finding with its code, and a repository in order has none
FR-003checkbun test suite/metapackages.test.ts: the root package.json is private and AGENTS.md states the rule and the distribution
FR-004checkbun test suite/metapackages.test.ts: every library declares github and npm, a manifest of github alone is read and one of npm alone is refused, and the metapackages declare both
FR-005checkbun test suite/metapackages.test.ts: the five metapackages are folders named for their set with a manifest that names bundle, a bundle that is not the folder is refused, and the name of the metapackage is not linked to a checkout
FR-006checkbun test suite/metapackages.test.ts: the set of a role is the role's in ROLE_OF, commons holds the four, a library with no role is a problem, a library held back is in none
FR-007checkbun test suite/metapackages.test.ts: the dependencies are the members at their exact versions, the generated files are what the manifests make and --check writes nothing
FR-008checkbun test suite/metapackages.test.ts: the packer stages and inspects a metapackage and packs it, and the plan raises it after the members it depends on whenever a member is raised
FR-009checkbun test suite/releasing.test.ts: the package a manifest publishes is the one the record, the registry check and the publication use, and the tag is the library's
FR-010checkbun test suite/hygiene.test.ts: the six findings are made from manifests, lockfiles, the installed tree and imports, each with its code
FR-011checkbun test suite/hygiene.test.ts: the core is pure, bun.lock and package-lock.json give the same duplicates and a missing lockfile is a finding
FR-012checkbun test suite/hygiene.test.ts: the verb ends in 1 only on a failure, a warning alone ends in 0, and --json is one document
FR-013checkbun test suite/hygiene.test.ts: the repository of commons is not reported for its own packages
FR-014review0036-distribution FR-010kept by the check of the exact pins (E-HYGIENE-RANGE and E-HYGIENE-DUPLICATE)
FR-015checkbun test suite/metapackages.test.ts: a metapackage is after its members in the release plan
FR-016nonePlanned: the manifest of a workspace does not say which packages are private yet
FR-017checkbun test suite/package.test.ts: the package @intellectual-frontiers/docs is a library with the command ifc-docs
FR-018checkbun test suite/metapackages.test.ts: the README has the section and the metapackage table, the guide exists with one entry in docs.config.ts
FR-019checkbun test suite/pack-commons.test.ts: the mode is one of two, the repository is in single mode, the environment names the other for one run and a value that is no mode is refused
FR-020checkbun test suite/metapackages.test.ts: in single mode the generator of the sets makes no file and finds and removes the files that are there; release-single.test.ts: the plan is the one package's; pack-library.ts and the metapackage packer pack nothing in single mode and work where IFC_DISTRIBUTION names per-library (tests/release/commons-packages.test.ts)
FR-021checkbun test ./tests/release/commons-package.test.tscommons-package.test.ts: the one package is packed from the real libraries (all of them, lab and data included), its tarball inspected, installed with npm and with Bun; and pack-commons.test.ts on a small repository of real files
FR-022checkbun test suite/pack-commons.test.ts: the keys of the exports are ./<library>[/<subpath>] with their types, source and compiled file, an import is rewritten in code and in comment examples and a string is not, and no specifier of the real package names a library by its own package (tests/release/commons-package.test.ts)
FR-023checkbun test suite/pack-commons.test.ts: the dependencies are the union of the libraries' and the drivers', exact, two versions of one package and a range are findings
FR-024checkbun test suite/pack-commons.test.ts: a command is a launcher of the compiled module and a name two libraries declare is a finding; the five commands run on Node from the installed package (tests/release/commons-package.test.ts)
FR-025checkbun test suite/pack-commons.test.ts: a file that does something when it is loaded is found and the package that marks it free of effects is refused; the telemetry host is named in the real package (tests/release/commons-package.test.ts)
FR-026checkbun test ./tests/release/commons-package.test.tscommons-package.test.ts: the real installs with npm and Bun, every entry of every library imported on Node and Bun, a consumer type-checked with and without dom under nodenext and bundler; pack-commons.test.ts: a missing library, an unrewritten specifier, a colliding command and a missing dependency are each found on a copy made to fail
FR-027checkbun test suite/release-single.test.ts: one release of commons, raised by the greatest Impact across all libraries with the rule of major version 0, a held library counted, a version ahead of its tag released as it is, the floor of the keys of exports, the record with its one entry
FR-028checkbun test suite/release-single.test.ts: the registries are github alone, the publication sends the tarball to the GitHub package registry and tags and asks npm for nothing, and with npm in the list sends it there too
FR-029checkbun test suite/pack-commons.test.ts: the tools are derived from the manifests and the sources, a library that needs a package the folder lacks is found in its package.json and in its bun.lock; tests/release/commons-ci.test.ts: a fresh clone with only commons/commons installed passes bun install --frozen-lockfile, bun run verify and bun tools/pack.ts
FR-030checkbun test ./tests/release/commons-package.test.tscommons-package.test.ts: the data of the NIST catalogs, the guides of Docs and the installers of Ergonex are in the tarball and the catalogs load their data from the installed package on Node and on Bun; pack-commons.test.ts: a folder a library reads is shipped beside its sources and its compiled files and the folders of NOT_RUNTIME are not
FR-031checkbun test suite/pack-commons.test.ts: a file that only commons needs internally, a file in dist/ that is no declaration and a file shipped twice are findings of the inspection
FR-032checkbun test suite/pack-commons.test.ts: a package over its budget is a finding, and the staged package is reported by kind and by library
FR-033checkbun test suite/pack-commons.test.ts: a static import of an optional peer is a finding and a dynamic one is not; commons-package.test.ts imports every entry with no optional peer installed
FR-034checkbun test suite/usage.test.ts: the libraries imported, reached and never touched, from the consumer's files and the installed package

0037 Planning

RequirementMechanismWhoNote
FR-001checkbun run verifycommons/planning suite/fold.test.ts, vocabulary.test.ts (0002-planning-core FR-001, FR-002): an item is a sum of the four kinds over the shared core, with the carried fields, and the lists are the ontology's
FR-002nonePlanned, phase 1 in part: the three severities, the four verdicts and the carried value of a source are in commons/planning (0002-planning-core FR-001, FR-002); the statement of the matrix of FR-015 waits for phase 4
FR-003checkbun run verifycommons/planning suite/events.test.ts, records.test.ts (0002-planning-core FR-005, FR-011): the fourteen types of event as a closed union, immutable, no operation that changes or removes one, and the ten types of the monorepo's issue files read as cases of it
FR-004checkbun run verifycommons/planning suite/fold.test.ts (0002-planning-core FR-006): fold is the same for any order and any repeat of the events, by property tests, and the state is never stored
FR-005checkbun run verifycommons/planning suite/actors.test.ts, events.test.ts (0002-planning-core FR-004, FR-005): an agent names its principal, a person names none, an agent with no principal is refused when built and when read, and a context with no person makes no person's or agent's actor
FR-006nonePlanned, phase 1 in part: fold starts an inferred item proposed and confirms it only by a person, by the policy (commons/planning suite/fold.test.ts); the views and queries that do not count a proposal wait for phase 4
FR-007nonePlanned, phase 1 and 2 in part: the ids are made by the hybrid clock of anyfs's merge, the next id is after every id seen and a far-future id is refused (commons/planning suite/ids.test.ts); that an id survives a move between places waits for reconcile, phase 3
FR-008nonePlanned: phase 3
FR-009nonePlanned, phase 1 in part: the cycle check of blocks (commons/planning suite/links.test.ts); the trace to each observation waits for phase 3
FR-010nonePlanned: phase 3
FR-011nonePlanned: phase 3
FR-012nonePlanned, phase 1 in part: fold applies the four authorities to each field over the events, and a person-only field waits as a proposal (commons/planning suite/fold.test.ts); the authority for a source and a field comes with the configuration, phase 6
FR-013nonePlanned: phase 3
FR-014nonePlanned: phase 3
FR-015nonePlanned: phase 4
FR-016nonePlanned: phase 3
FR-017nonePlanned: phase 3
FR-018nonePlanned: phase 3
FR-019nonePlanned: phase 3
FR-020nonePlanned: phase 4
FR-021nonePlanned: phase 4
FR-022checkbun run verifycommons/planning suite/typing.test.ts (0002-planning-core FR-008): the governance and logical sources import no system module and the work runs with the clock, the random source and the network taken away
FR-023nonePlanned: phase 4
FR-024nonePlanned: phase 5
FR-025nonePlanned, phase 2 in part: the issue file, the event object and the summary of the monorepo are decoded, read as an item with all ten types of event and written as they were (commons/planning suite/records.test.ts, and read-only against the monorepo's own files); the source that writes a new event waits for phase 5
FR-026nonePlanned: phase 5
FR-027nonePlanned: phase 5
FR-028nonePlanned: phase 5
FR-029nonePlanned: phase 5
FR-030nonePlanned: phase 5
FR-031nonePlanned: phase 5
FR-032nonePlanned: phase 6
FR-033nonePlanned: phase 3
FR-034nonePlanned: phase 6
FR-035nonePlanned: phase 6
FR-036nonePlanned: phase 6
FR-037nonePlanned: phase 6
FR-038checkbun run verifycommons/planning suite/records.test.ts (0002-planning-core FR-011): one JSON5 file for each event and each item, keys in the order of RFC 8785 section 3.2.3, and a total decoder
FR-039nonePlanned, phase 2 in part: the summary of the monorepo's issues is rendered from items by a pure function (commons/planning suite/records.test.ts); the renderers named by the configuration wait for phase 6
FR-040nonePlanned, phase 0 in part: the library is Kanon with its three layers and its verify runs the check of kanon; the patches, reconcile, the queries and the surfaces wait for phases 3 to 6
FR-041checkbun run verifycommons/planning suite/typing.test.ts (0002-planning-core FR-009): no any, non-null assertion, enum or cast but brand, readonly and exact optional fields held by the compiler, every switch closed
FR-042nonePlanned: phase 5
FR-043nonePlanned: the ontology names every list of the library, held by commons/planning suite/vocabulary.test.ts; the rule over every term of the model waits for phase 4
FR-044checkbun run verifycommons/planning suite/legacy-ids.test.ts (0002-planning-core FR-010): the id of a ULID and of another scheme, the external ids and the actors of a file by the rule of the configuration
FR-045nonePlanned, phase 1 in part: a run's context makes an agent's actor with the basis stored and refuses a person or an agent where there is no person (commons/planning suite/actors.test.ts); the tool server, the headless run and the commit-author case over a real Git repository wait for phase 6
FR-046nonePlanned, phase 2 in part: an issue file's every key is carried or found (commons/planning suite/records.test.ts); the other sources wait for phase 5
FR-047nonePlanned: phase 5

0038 Build policy, findings and never failures

RequirementMechanismWhoNote
FR-001checkbun test suite/0002-libraries-ci-findings: ci-policy.test.ts and ci-findings.test.ts: every step of the real workflows keeps the policy and none can end a job red but a red cause or a gate
FR-002checkbun test suite/0002-libraries-ci-findings: ci-policy.test.ts: the red causes are a closed list and the only steps that can end a cell red are the red causes
FR-003checkbun test suite/0002-libraries-ci-findings: ci-policy.test.ts: every step has a policy, the inventory counts them, and the validation finds a step with none
FR-004checkbun test suite/0002-libraries-ci-findings: ci-policy.test.ts and ci-findings.test.ts: no matrix fails fast, every limit is below its job's, a job after a matrix runs with always(), the wrapper stops a command that does not end
FR-005checkbun test suite/0002-libraries-ci-findings: ci-collect.test.ts: ends 2 only where a cell that ran left no file
FR-006checkbun test suite/0002-libraries-ci-findings: ci-findings.test.ts: the id is stable across lines, runs and messages
FR-007checkbun test suite/0002-libraries-ci-findings: ci-findings.test.ts: open, fixed and accepted are derived from the runs and the acceptances
FR-008checkbun test suite/ci-accepted.test.ts: each rule of an acceptance is found in real files; the check is one of repoctl check; the path is the owner's in CODEOWNERS
FR-009checkbun test suite/library-commit-doctor.test.ts: a staged secret is refused by the commit verb; the license text is made by license.ts and a hand-written one is a stale generated file
FR-010checkbun test suite/0002-libraries-ci-findings: ci-findings.test.ts: publish regardless until 2027-01-31, hold per library for an open error and owner-review-due from 2027-02-01
FR-011checkbun test suite/ci-collect.test.ts: the conclusion is neutral or success and never failure; seen live: findings (tests) neutral on the run of the commit that made it. Branch protection is a setting of GitHub that the owner applies
FR-012checkbun test suite/0002-libraries-ci-findings: ci-history.test.ts: on real git, a file added and never replaced, six writers racing at once
FR-013checkbun test suite/0002-libraries-ci-findings: ci-findings.test.ts: the wrapper exits 0 for a failing test, no output, a missing program and a timeout
FR-014checkbun test suite/0002-libraries-ci-findings: ci-findings.test.ts: the root tests are read per file, each file that ran is a step, a file that stops failing is fixed while another keeps failing; the generated workflow runs each file by itself and its findings are of the module repository

Titles, headings, exports, tables, columns and requirements. Esc closes.