IF Commons GitHub

Quality evidence

0001Draft

0001-quality-evidence · owner if · domain commons

Test runs: Capture (runtime)

FR-001checkno test run

Where IFC_TEST_RECORD names a file, each test process MUST append its records to it as OTLP JSON lines as each test ends, so that a process that dies keeps what it finished; a test that started and did not end before its process exited MUST be recorded as cancelled. Where it is not set, records MUST go to the installed pipeline (commons 0006-signals) if any, and otherwise be kept in memory for the process.

Enforced (check): .github: cd commons/quality && bun test suite/ — host-test-run.test.ts: records appended per test, a killed process gives cancelled

Written in: quality/about.ts, quality/library.ts, quality/tools/check.ts, quality/tools/pack.ts

Cited by: Test evidence

Test runs: The run (runtime and tools)

FR-002checkno test run

src/host/test-run.ts MUST run a suite: start one trace with a test run span, run bun test or node --test (chosen, one or both in turn) with TRACEPARENT and IFC_TEST_RECORD set, pass the runner's own output on, gather every process's records into one OTLP JSON file for the run (<out>/<trace id>.otlp.json) with the run's span, and say where it is. src/test-cli.ts (ifc test) MUST be its command line.

Enforced (check): .github: cd commons/quality && bun test suite/ — host-test-run.test.ts: one record file per run, gathered from child processes

Written in: quality/src/host/test-run.ts, quality/src/test-cli.ts

Cited by: host/test-run, Quality, Test evidence

FR-003checkno test run

A run MUST fail (exit 1) when a test failed, when a runner exited non-zero, when a test is cancelled, or when a requirement of the list given (--requirements, one id per line or a spec-kit enforcement register's rows of mechanism check) is neither proven by a test of the run nor declared reviewed with its reason; the run's span MUST say which, by test.suite.run.status and ifc.test.unproven.

Enforced (check): .github: cd commons/quality && bun test suite/ — host-test-run.test.ts: the exit rule, an unproven requirement fails

Cited by: Test evidence

FR-004checkno test run

The record of a run MUST be the evidence: kept as written, read only through the decoder of commons 0006-signals FR-004, and its digest the SHA-256 of its bytes.

Enforced (check): .github: cd commons/quality && bun test suite/ — host-test-run.test.ts: the record read back by the decoder, its digest

Cited by: host/test-run, Quality, Test evidence

Test runs: Reports (kernel)

FR-005checkno test run

src/test-report.ts MUST read a run's record into a typed model (the run, its installation record, its tests, its requirements) and render it, purely, as: TAP version 14 (a plan, ok and not ok numbered, # SKIP and # TODO with their reasons, a YAML diagnostic block for a failure with its message, expected, actual and requirements, one subtest per file); JUnit XML (one testsuite per file and runtime, testcase with classname and time in seconds, failure, skipped, and the requirements as properties); CTRF JSON (its results.tool, summary and tests, the requirements and risk under extra); SARIF 2.1.0 (each failed test a result at its file, with the requirement as a rule); and OSCAL 1.2.3 assessment results (commons 0007-grc FR-017) with one observation per test and one finding per requirement.

Enforced (check): .github: cd commons/quality && bun test suite/ — test-report.test.ts: TAP 14, JUnit XML, CTRF, SARIF and OSCAL renderings

Cited by: Test evidence

FR-006checkno test run

The library MUST render a test completion report, in Markdown and in HTML that needs nothing outside itself: the summary; the installation record; a requirement trace matrix (each requirement, the tests that prove it and their outcomes, or that it was reviewed, waived or left unproven); the incidents (each failure, cancellation and skip with its reason); high-risk requirements and whether they have a signed review; the conclusion; and the signatures on the run with their meaning and role.

Enforced (check): .github: cd commons/quality && bun test suite/ — test-report.test.ts: the completion report in Markdown and HTML with the trace matrix

Cited by: Test evidence

FR-007checkno test run

The counts in every rendering of a record (tests, passed, failed, skipped, todo, cancelled) MUST be equal to the model's, and a rendering MUST hold no time or value that is not in the record, so that rendering a record twice gives the same bytes.

Enforced (check): .github: cd commons/quality && bun test suite/ — test-report.test.ts: counts equal across renderings (property), rendering twice the same bytes

Cited by: Test evidence

Test runs: Evidence (kernel and runtime)

FR-008checkno test run

A run MUST append the digest of its record to an evidence ledger (commons 0007-grc FR-007) with the kind test-run, and MAY sign it: an in-toto Statement v1 whose subject is the record and whose predicate is the in-toto Test Result (https://in-toto.io/attestation/test-result/v0.1: the result PASSED, WARNED or FAILED, the configuration as resource descriptors, and the passed, warned and failed tests), in a DSSE envelope, and the signature entered in the ledger with its meaning (executed, reviewed or approved), its role and its time, so that the signature is linked to its record.

Enforced (check): .github: cd commons/quality && bun test suite/ — host-test-run.test.ts: the ledger entry and a signed in-toto Test Result

Cited by: host/test-run, Quality, Test evidence

FR-009checkno test run

ifc test verify MUST check that a record's digest is in the ledger, that the ledger's chain is whole, and that each envelope given verifies with the key given and names the record's digest; it MUST fail and say which when any does not.

Enforced (check): .github: cd commons/quality && bun test suite/ — host-test-run.test.ts: verify fails on a changed record, a broken chain, a bad signature

Cited by: host/test-run, Quality, Test evidence

FR-010checkno test run

A requirement whose tests are of high risk MUST be reported as needing a signed review, and ifc test verify --require-review MUST fail until a signature of meaning reviewed is in the ledger for the run.

Enforced (check): .github: cd commons/quality && bun test suite/ — host-test-run.test.ts: --require-review for high-risk requirements

Cited by: Test evidence

Quality: Principles

FR-011checkpassing

Everything the quality system reports MUST be reported in OpenTelemetry (commons 0006-signals): runs, results, probes and measures are spans, log records and metrics through one pipeline, and no second channel MAY carry a result that the pipeline does not.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-branch.test.ts: the quality branch holds OTLP records and nothing else (a result as JUnit XML is refused by the chain); that no other channel carries a result in a run's pipeline stays with 0006-signals

Proved by: quality/suite/quality-branch.test.ts, quality/suite/quality-ladder.test.ts

Tests: passed: suite/quality-branch.test.ts the branch holds records and nothing else: a result in another form (JUnit XML) is not evi

Cited by: Intellectual Frontiers Quality System

FR-012checkpassing

Nothing authorizes itself: what produces a result MUST NOT be what accepts it, a check MUST NOT waive or close its own failure, and an agent that opened a nonconformance MUST NOT approve the closure of its CAPA (commons 0020-ifccm FR-018 to commons 0020-ifccm FR-020).

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-ledger.test.ts, quality-system.test.ts: a CAPA is closed only by a named person: an automated run, an agent, the one that opened it and, where a regulated domain is declared, the author of the corrective change (read from Git) are each refused

Proved by: quality/suite/quality-ladder.test.ts, quality/suite/quality-ledger.test.ts, quality/suite/quality-system.test.ts

Tests: passed: suite/quality-ledger.test.ts a CAPA is verified by the run that passes its named test after the corrective change, neve; passed: suite/quality-system.test.ts run as programs: a failed run opens a nonconformance, `quality record` verifies the CAPA t

Cited by: Intellectual Frontiers Quality System

FR-013checkpassing

A planned case, check or requirement that did not run MUST be recorded as ifqs:NotRun (written not_run) with the reason, and MUST NOT be counted as passed, silently skipped or left out; the count of not_run MUST be shown wherever the counts of passed and failed are.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-record.test.ts, quality-command.test.ts: a planned case that did not run is not_run with its reason, never passed, refused without a reason, counted in the TAP, JUnit, CTRF, SARIF and completion renderings and by `quality record`

Proved by: quality/suite/quality-command.test.ts, quality/suite/quality-ladder.test.ts, quality/suite/quality-ledger.test.ts, quality/suite/quality-record.test.ts, quality/suite/quality-redaction.test.ts, quality/suite/quality-regulated.test.ts

Written in: quality/src/pure/render.ts, quality/src/quality.ts

Tests: passed: suite/quality-command.test.ts the record of a real run is kept on the quality branch, verified, found broken after a rew; passed: suite/quality-command.test.ts a case that did not run with no reason, a missing option and an unknown command are usage ; passed: suite/quality-record.test.ts a case that did not run and gives no reason is refused when the record is read; passed: suite/quality-record.test.ts a case that did not run is recorded not_run with its reason, rendered as CTRF other, count

Cited by: Quality, pure/render, Intellectual Frontiers Quality System

FR-014checkpassing

Every piece of evidence MUST carry its grade (ifqs:EvidenceGrade), and every rendering that shows evidence, or a count of requirements proved, MUST show the grade with it; a count of proved requirements with no grade MUST NOT be shown.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-ladder.test.ts, quality-system.test.ts: a count of proved requirements is shown with the grade it is counted at and the review debt beside it, and refused without either; the completion report, the register view and the index carry both

Proved by: quality/suite/quality-ladder.test.ts, quality/suite/quality-ledger.test.ts, quality/suite/quality-system.test.ts

Written in: quality/src/pure/ladder.ts

Tests: passed: suite/quality-ladder.test.ts a count of proved requirements is shown with its grade and the review debt beside it, and ; passed: suite/quality-system.test.ts the register is shown with the grade and day of each row's evidence and checked against th

Cited by: Quality, pure/ladder, pure/render, Intellectual Frontiers Quality System

FR-015checkpassing

WHEN a result that a requirement relies on fails, or a proof of it is stale (FR-030), the system MUST open a nonconformance (ifqs:Nonconformance) itself, with the requirement, the evidence it arises from and the reason, and MUST NOT wait for a person to notice.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-ladder.test.ts, quality-ledger.test.ts, quality-system.test.ts: a failed run and a stale proof open a nonconformance by themselves (once each), with the requirement, the evidence and the reason; freshness --open writes them to the quality branch

Proved by: quality/suite/quality-ladder.test.ts, quality/suite/quality-ledger.test.ts, quality/suite/quality-system.test.ts

Written in: quality/src/commands.ts, quality/src/host/report.ts, quality/src/pure/ledger.ts

Tests: passed: suite/quality-ladder.test.ts the system opens a nonconformance itself from a failed run and from a stale proof, once fo; passed: suite/quality-ledger.test.ts on a real repository a failed run opens a nonconformance by itself, a CAPA is verified by ; passed: suite/quality-system.test.ts a proof goes stale where a file of its chain or the requirement's own line changed after i

Cited by: commands, host/report, Quality, pure/ledger, Intellectual Frontiers Quality System

Quality: What it is held to

FR-016checkpassing

WHERE a requirement's tests are of high risk (commons 0008-test-evidence FR-001), the requirement MUST NOT be counted proved below grade ifqs:E4, and otherwise MUST NOT be counted proved below ifqs:E3, so that the assurance asked for follows the risk, as the FDA's guidance on Computer Software Assurance asks; WHERE a harness declares a regulated domain and has declared production (commons 0020-ifccm FR-010), every requirement of it MUST need ifqs:E4, whatever its risk, from the day it declares production (that day included). The grade needed is a pure function of the risk, the declaration and the day (gradeNeeded(risk, declaration, today): none of the three is read from the clock or a file inside it), and the ladder, the Trust page and the tier claim (FR-040) MUST use it, a tier claim being refused where a requirement of the tier is held by a mechanism but proved below the grade needed.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-ladder.test.ts: a requirement is counted proved at E3, and at E4 where one of its tests is of high risk (an E3 run of a high-risk test is not counted); quality-regulated.test.ts: gradeNeeded is E4 for every requirement of a harness that declares a regulated domain and production (the day is an argument), the ladder, the tier claim and quality tier use it

Proved by: quality/suite/quality-ladder.test.ts, quality/suite/quality-regulated.test.ts

Written in: quality/src/host/declaration.ts

Tests: passed: suite/quality-ladder.test.ts a requirement is counted proved at E3, and at E4 where one of its tests is of high risk; passed: suite/quality-regulated.test.ts the tier claim of a regulated harness in production is refused where a requirement of the ; passed: suite/quality-regulated.test.ts quality tier reads the declaration: a regulated harness in production is refused a tier it; passed: suite/quality-regulated.test.ts gradeNeeded: E3, E4 for high risk, and E4 for every requirement where the harness declares; passed: suite/quality-regulated.test.ts the declaration is read from the harness's own file and a real E3 run kept on a real quali and 1 more

Cited by: host/declaration, Quality, pure/ladder, Intellectual Frontiers Quality System

FR-017checkpassing

A test MAY name the quality characteristic it proves, in the words of ISO/IEC 25010, as the record attribute ifc.test.characteristic, and a report of a run MUST bear the document names of ISO/IEC/IEEE 29119-3 (the test completion report of FR-006, the test status report of a run in progress and the test incident report of each failure, cancellation and not_run).

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-record.test.ts: the runtime records ifc.test.characteristic (an ISO/IEC 25010 word) and the reports bear the 29119-3 document names (completion, status, incident)

Proved by: quality/suite/quality-command.test.ts, quality/suite/quality-record.test.ts

Tests: passed: suite/quality-command.test.ts the record of a real run is kept on the quality branch, verified, found broken after a rew; passed: suite/quality-record.test.ts a test names its characteristic and a report bears the document names of ISO/IEC/IEEE 2911; passed: suite/quality-record.test.ts the characteristic is on the test's record (ifc.test.characteristic) and is one of ISO/IEC; passed: suite/quality-record.test.ts the runtime records the characteristic a test names

Cited by: Quality, pure/render, Intellectual Frontiers Quality System

Quality: The canonical record (it extends commons 0008-test-evidence)

FR-018checkpassing

The canonical result of a run MUST be the record of commons 0008-test-evidence FR-002 to FR-002 (OTLP/JSON, the OpenTelemetry test conventions), one file per run and one log record per case, and the body of a case's log record MUST be a CTRF test object (name, status and duration, and the other CTRF fields the case has); JUnit XML, TAP, CTRF documents, SARIF and OSCAL (FR-005) MUST be rendered from it on demand and MUST NOT be kept as evidence.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-record.test.ts, quality-command.test.ts: the body of each case's log record is a CTRF test object; JUnit, CTRF, SARIF and TAP are rendered on demand, byte for byte the same, and not kept

Proved by: quality/suite/quality-command.test.ts, quality/suite/quality-record.test.ts

Written in: quality/src/pure/record.ts

Tests: passed: suite/quality-command.test.ts the record of a real run is kept on the quality branch, verified, found broken after a rew; passed: suite/quality-record.test.ts a rendering is made on demand from the record and is the same bytes each time; passed: suite/quality-record.test.ts the body of a case's log record is a CTRF test object, and the file reads back as the reco

Cited by: assessor/verify-pack, Quality, pure/record, pure/render, tier2-commands, Intellectual Frontiers Quality System

FR-019checkpassing

The record's outcome (ifc.test.outcome) MUST also take the value not_run, with its reason (ifc.test.reason), in addition to those of commons 0008-test-evidence FR-001; a requirement whose only proofs are not_run is unproven (FR-003), and a CTRF rendering MUST give it the status other.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-record.test.ts: ifc.test.outcome takes not_run with ifc.test.reason, CTRF renders it as other, and a requirement whose only proof is not_run is unproven; the outcome words equal the ifqs ontology's

Proved by: quality/suite/quality-record.test.ts

Written in: quality/src/pure/names.ts

Tests: passed: suite/quality-record.test.ts a case that did not run is recorded not_run with its reason, rendered as CTRF other, count

Cited by: pure/names, Intellectual Frontiers Quality System

FR-020checkpassing

A check of Mizan (the specification rules, the trace and layers checks, the changes check of commons 0020-ifccm) MUST leave its result in the same record, each rule a case and each finding a failed case with its rule id, file and line, so that its findings render as SARIF results.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-record.test.ts: checkRun leaves each rule as a case and each finding as a failed case with rule id, file and line, rendered as SARIF results (a rule that could not run is not_run); the Mizan and changes commands calling it are Planned, M2 and M7 of issue #10

Proved by: quality/suite/quality-changes-record.test.ts, quality/suite/quality-record.test.ts

Tests: passed: suite/quality-changes-record.test.ts a run of the changes check leaves each rule as a case and each finding as a failed case wi; passed: suite/quality-record.test.ts a check leaves its rules as cases and its findings as failed cases with rule id, file and

Cited by: Quality, pure/record, pure/render, tier2-commands, Intellectual Frontiers Quality System

Quality: Git is the evidence

FR-021checkpassing

A run's record MUST be kept as one immutable file at quality/evidence/YYYY/MM/DD/<trace id>.otlp.json on an orphan branch named quality, committed by signed commits that only append; a harness MUST refuse a force-push or a rewrite of the branch, a file MUST never be changed after its commit, and a correction MUST be a new run.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-branch.test.ts, quality-command.test.ts: one new file per run at quality/evidence/YYYY/MM/DD/<trace id>.otlp.json on an orphan branch in a commit that only appends, never replaced, signed through the host's SSH signing, a force-push and a deletion refused by a repository set to refuse them

Proved by: quality/suite/quality-branch.test.ts, quality/suite/quality-command.test.ts, quality/suite/quality-ladder.test.ts, quality/suite/quality-ledger.test.ts

Written in: quality/src/host/branch.ts, quality/src/host/git.ts, quality/src/pure/chain.ts, quality/src/pure/primitives.ts, quality/src/pure/time.ts

Tests: passed: suite/quality-branch.test.ts the branch holds records and nothing else: a result in another form (JUnit XML) is not evi; passed: suite/quality-branch.test.ts a commit that edits or deletes a file of the branch, or adds anything else, is found and n; passed: suite/quality-branch.test.ts a commit signed through the host's SSH signing is graded E4 and verifies against the allow; passed: suite/quality-branch.test.ts a file kept is never changed or replaced: the same run again is refused and the branch is ; passed: suite/quality-branch.test.ts a force-push or a deletion of the quality branch is refused by a repository set to refuse and 5 more

Cited by: host/branch, host/git, Quality, pure/chain, pure/time, Intellectual Frontiers Quality System

FR-022checkpassing

The resource of each file MUST carry ifc.quality.previous.sha256, the SHA-256 of the file before it on the branch (64 zeros for the first), so that a file removed, inserted or changed is found by the chain, and verification MUST name the first file that does not match (as commons 0007-grc FR-007 does for a ledger).

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-branch.test.ts, quality-record.test.ts: ifc.quality.previous.sha256 on every resource (64 zeros first) and the verifier names the first file that does not match

Proved by: quality/suite/quality-branch.test.ts, quality/suite/quality-command.test.ts, quality/suite/quality-ledger.test.ts, quality/suite/quality-record.test.ts

Tests: passed: suite/quality-branch.test.ts a commit that edits or deletes a file of the branch, or adds anything else, is found and n; passed: suite/quality-branch.test.ts a file of the branch changed by one byte is found: the first file whose chain does not mat; passed: suite/quality-branch.test.ts each file names the SHA-256 of the file before it, 64 zeros for the first, and a chain tha; passed: suite/quality-command.test.ts the record of a real run is kept on the quality branch, verified, found broken after a rew; passed: suite/quality-ledger.test.ts a ledger file changed after it was kept, a file removed, and an event that does not follow and 1 more

Cited by: Intellectual Frontiers Quality System

FR-023checkpassing

WHEN a run is kept, a Git note under refs/notes/quality on the tested commit MUST give the evidence file's path, its SHA-256 and its grade, so that a commit shows its evidence without being changed; a commit with no note MUST be shown as having no evidence (ifqs:E0).

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-branch.test.ts: a note under refs/notes/quality on the tested commit gives the file's path, SHA-256 and grade; no note is E0 and a note that does not match its file breaks the evidence

Proved by: quality/suite/quality-branch.test.ts, quality/suite/quality-command.test.ts

Tests: passed: suite/quality-branch.test.ts a commit with no note has no evidence (E0), and a note whose SHA-256 differs from its file; passed: suite/quality-branch.test.ts a Git note under refs/notes/quality on the tested commit gives the evidence file's path, i; passed: suite/quality-command.test.ts the record of a real run is kept on the quality branch, verified, found broken after a rew

Cited by: host/branch, host/git, Quality, pure/chain, Intellectual Frontiers Quality System

FR-024checkpassing

The index of runs, for search, trends and the public page, MUST be derived from the quality branch, MUST be rebuildable from it alone, and MUST NOT be a source of evidence; a harness MAY keep it in a database.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-ledger.test.ts, quality-system.test.ts: the index is derived from the quality branch, deterministic, checkable with --check, and rebuilt in a repository that holds only the branch to the same bytes

Proved by: quality/suite/quality-ledger.test.ts, quality/suite/quality-system.test.ts

Written in: quality/src/pure/index-file.ts

Tests: passed: suite/quality-ledger.test.ts on a real repository a failed run opens a nonconformance by itself, a CAPA is verified by ; passed: suite/quality-system.test.ts the index is derived from the branch, deterministic, checkable against the file on disk, a

Cited by: assessor/pack, commands, host/report, Quality, pure/index-file, Intellectual Frontiers Quality System

FR-025checkpassing

A file MUST be redacted before it is committed (commons 0006-signals FR-006) and MUST name no person (commons 0008-test-evidence FR-003), because a committed file cannot be changed.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-record.test.ts: secrets and e-mail addresses are redacted before a record is kept and a record that names a person is refused

Proved by: quality/suite/quality-record.test.ts, quality/suite/quality-redaction.test.ts

Tests: passed: suite/quality-record.test.ts a record is redacted of secrets and e-mail addresses before it is kept, and one that names; passed: suite/quality-redaction.test.ts a run kept with a secret and an e-mail address in a failure message is written redacted, a; passed: suite/quality-redaction.test.ts events of every kind written to a real quality branch hold no secret and no e-mail address; passed: suite/quality-redaction.test.ts the ledger redacts every text of an event of every kind at the source, Tier 1 and Tier 2;

Cited by: Quality, pure/ledger, pure/record, Intellectual Frontiers Quality System

Quality: The evidence ladder

FR-026checkpassing

Evidence MUST be graded, from ifqs:E0 to ifqs:E5: ifqs:E0 none (a requirement with no evidence), ifqs:E1 stated (a person or an agent says it is met), ifqs:E2 reviewed (a review is recorded against the requirement), ifqs:E3 tested (an automated run proved it and the record exists), ifqs:E4 attested (the run is kept on the quality branch, chained, signed and linked to its commit, FR-021 to FR-023) and ifqs:E5 observed (a probe of the system in operation reports it); a requirement's grade MUST be the highest grade of its fresh evidence.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-ladder.test.ts, quality-system.test.ts, ifqs-ontology.test.ts: the six grades E0 to E5 exist in order with their ranks; a requirement is graded the highest grade of its fresh evidence (a statement E1, a review E2, a run E3 or E4, a probe E5), and stale evidence does not count

Proved by: quality/suite/quality-branch.test.ts, quality/suite/quality-ladder.test.ts, quality/suite/quality-system.test.ts

Written in: quality/src/host/gather.ts

Tests: passed: suite/quality-branch.test.ts a commit signed through the host's SSH signing is graded E4 and verifies against the allow; passed: suite/quality-branch.test.ts a commit with no note has no evidence (E0), and a note whose SHA-256 differs from its file; passed: suite/quality-ladder.test.ts a requirement's grade is the highest grade of its fresh evidence: a statement E1, a review; passed: suite/quality-system.test.ts a statement is E1, a review E2 (an agent's said so and no higher), a probe's typed result

Cited by: host/branch, host/gather, Quality, pure/chain, pure/ladder, pure/names, Intellectual Frontiers Quality System

FR-027checkpassing

The proof register of a specification kit (the enforcement register, commons 0003-mizan FR-005) MUST be shown with the grade and the day of the evidence of each row, generated from the evidence and never written by hand.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-ladder.test.ts, quality-system.test.ts: quality register shows the proof register with the grade, the day and the freshness of each row, generated and checked against the file

Proved by: quality/suite/quality-ladder.test.ts, quality/suite/quality-system.test.ts

Tests: passed: suite/quality-ladder.test.ts the proof register is shown with the grade and the day of each row's evidence, generated, ; passed: suite/quality-system.test.ts the register is shown with the grade and day of each row's evidence and checked against th

Cited by: commands, Quality, Intellectual Frontiers Quality System

FR-028checkpassing

A harness MUST report its review debt (ifqs:ReviewDebt) as a number: the count of requirements whose best fresh evidence is ifqs:E1 or ifqs:E2, counted at a stated revision; it MUST be shown beside every count of proved requirements, and it MUST NOT grow from one revision of the default branch to the next without a Decision.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-ladder.test.ts, quality-system.test.ts: the review debt is the count of requirements held at E1 or E2, shown beside every count of proved requirements, and growth with no Decision fails

Proved by: quality/suite/quality-ladder.test.ts, quality/suite/quality-system.test.ts

Tests: passed: suite/quality-ladder.test.ts a count of proved requirements is shown with its grade and the review debt beside it, and ; passed: suite/quality-system.test.ts a statement is E1, a review E2 (an agent's said so and no higher), a probe's typed result

Cited by: host/report, Quality, Intellectual Frontiers Quality System

FR-029checkpassing

WHERE a review (ifqs:E2) is made by an agent, the record MUST say that it was an agent's, and it MUST be graded no higher than ifqs:E2.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-ladder.test.ts, quality-system.test.ts: a review by an agent is recorded as an agent's and graded E2 at most; a person's sample is recorded as a sample

Proved by: quality/suite/quality-ladder.test.ts, quality/suite/quality-system.test.ts

Tests: passed: suite/quality-ladder.test.ts a review made by an agent is said so in the record and graded no higher than E2; passed: suite/quality-system.test.ts a statement is E1, a review E2 (an agent's said so and no higher), a probe's typed result

Cited by: Quality, pure/ladder, pure/ledger, Intellectual Frontiers Quality System

Quality: Freshness

FR-030checkpassing

A proof MUST be ifqs:Fresh, ifqs:Due or ifqs:Stale (ifqs:FreshnessState): by time, as commons 0007-grc FR-011 judges evidence against a cadence, and by change, being stale where a file in the requirement's trace chain (its text, term, code or test, commons 0020-ifccm FR-014) changed after the revision of the run; a stale proof MUST open a nonconformance (FR-015) and MUST NOT count at its grade.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-ladder.test.ts, quality-system.test.ts: a proof is Fresh, Due or Stale by its cadence and Stale by change where a file of its chain, the requirement's own line or its commit's place in the history changed (real Git); the freshness words are also held by ifqs-ontology.test.ts

Proved by: quality/suite/quality-ladder.test.ts, quality/suite/quality-system.test.ts

Written in: quality/src/pure/chain-files.ts, quality/src/pure/freshness.ts

Tests: passed: suite/quality-ladder.test.ts a proof is fresh within its cadence, due in its last tenth, stale past it, and stale by ch; passed: suite/quality-system.test.ts a proof goes stale where a file of its chain or the requirement's own line changed after i

Cited by: commands, host/gather, Quality, pure/chain-files, pure/freshness, pure/time, Intellectual Frontiers Quality System

Quality: Nonconformance and CAPA

FR-031checkpassing

A nonconformance MUST carry its requirement, the evidence it arises from, its reason, who opened it (the system or a role) and its state (ifqs:NonconformanceOpen or ifqs:NonconformanceClosed), and MUST be linked to a Problem change request (commons 0020-ifccm FR-021).

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-ledger.test.ts: a nonconformance carries its requirement, evidence, reason, opener and state, and is linked to a Problem change request (an unlinked one is listed as such)

Proved by: quality/suite/quality-ledger.test.ts

Written in: quality/src/host/ledger-branch.ts

Tests: passed: suite/quality-ledger.test.ts on a real repository a failed run opens a nonconformance by itself, a CAPA is verified by ; passed: suite/quality-ledger.test.ts a nonconformance carries its requirement, evidence, reason, opener and state, is linked to

Cited by: host/ledger-branch, Quality, pure/ledger, Intellectual Frontiers Quality System

FR-032checkpassing

A nonconformance MUST be closed only through a CAPA that is closed (FR-035), never by editing its state.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-ledger.test.ts: no event edits a state; the event that closes a nonconformance follows only a closed CAPA

Proved by: quality/suite/quality-ledger.test.ts

Tests: passed: suite/quality-ledger.test.ts on a real repository a failed run opens a nonconformance by itself, a CAPA is verified by ; passed: suite/quality-ledger.test.ts a nonconformance carries its requirement, evidence, reason, opener and state, is linked to

Cited by: Intellectual Frontiers Quality System

FR-033checkpassing

A corrective and preventive action (ifqs:Capa) MUST state the corrective action, MUST name the test that verifies it (a test that exists and proves the requirement) and MUST be in one state of ifqs:CapaOpen, ifqs:CapaVerified and ifqs:CapaClosed, in that order.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-ledger.test.ts, quality-system.test.ts: a CAPA states its corrective action and names a test that exists and proves the requirement (a name that does not exist is refused)

Proved by: quality/suite/quality-ledger.test.ts

Tests: passed: suite/quality-ledger.test.ts on a real repository a failed run opens a nonconformance by itself, a CAPA is verified by ; passed: suite/quality-ledger.test.ts a nonconformance carries its requirement, evidence, reason, opener and state, is linked to

Cited by: Intellectual Frontiers Quality System

FR-034checkpassing

WHEN the test a CAPA names passes in a run at a revision that holds the last commit of the corrective change (the revision after it, or that commit itself, whose code is the corrected code), the CAPA MUST become ifqs:CapaVerified, and its verification MUST NOT be recorded in any other way.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-ledger.test.ts, quality-system.test.ts: a CAPA becomes verified only by the run that passes its named test at a revision that holds the corrective change (quality record does it); a failing, earlier or unrelated run verifies nothing

Proved by: quality/suite/quality-ledger.test.ts, quality/suite/quality-system.test.ts

Tests: passed: suite/quality-ledger.test.ts on a real repository a failed run opens a nonconformance by itself, a CAPA is verified by ; passed: suite/quality-ledger.test.ts a CAPA is verified by the run that passes its named test after the corrective change, neve; passed: suite/quality-system.test.ts run as programs: a failed run opens a nonconformance, `quality record` verifies the CAPA t

Cited by: Intellectual Frontiers Quality System

FR-035checkpassing

A CAPA MUST become ifqs:CapaClosed only from ifqs:CapaVerified and only by the approval of a named person, recorded as a Decision with the person and the day; an automated run closes the verification step and a person closes the CAPA, and where commons 0020-ifccm FR-020 applies the person MUST NOT be the author of the corrective change.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-ledger.test.ts, quality-system.test.ts: a CAPA is closed only from verified and only by a named person's Decision with the person and the day; its nonconformance closes with it

Proved by: quality/suite/quality-ledger.test.ts, quality/suite/quality-system.test.ts

Tests: passed: suite/quality-ledger.test.ts on a real repository a failed run opens a nonconformance by itself, a CAPA is verified by ; passed: suite/quality-ledger.test.ts a CAPA is verified by the run that passes its named test after the corrective change, neve; passed: suite/quality-system.test.ts run as programs: a failed run opens a nonconformance, `quality record` verifies the CAPA t

Cited by: Intellectual Frontiers Quality System

FR-036checkpassing

A nonconformance and its CAPA MUST appear in the index and on the public page (commons 0022-trust) from the moment they are opened, and a nonconformance that closed MUST stay in the record with its CAPA.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-ledger.test.ts, quality-system.test.ts: the index lists a nonconformance and its CAPA from the moment they are opened, and a closed one stays; the public page is 0022-trust's, Planned, M9

Proved by: quality/suite/quality-ledger.test.ts, quality/suite/quality-system.test.ts

Tests: passed: suite/quality-ledger.test.ts on a real repository a failed run opens a nonconformance by itself, a CAPA is verified by ; passed: suite/quality-system.test.ts the index is derived from the branch, deterministic, checkable against the file on disk, a

Cited by: host/ledger-branch, Quality, pure/index-file, pure/ledger, Intellectual Frontiers Quality System

Quality: Objectives

FR-037checkpassing

A success criterion MUST be a quality objective (ifqs:QualityObjective): a metric named as OpenTelemetry names a metric (commons 0006-signals FR-013), a target, a unit, an error budget and the window it is spent in; its measure MUST be computed from the evidence and MUST NOT be typed in.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-ladder.test.ts: the success criteria of 0021-ifqs are read as objectives (a metric named as OpenTelemetry names it, a target, a unit, an error budget, a window) whose measure is computed from the evidence and emitted as OpenTelemetry metrics

Proved by: quality/suite/quality-ladder.test.ts

Written in: quality/src/pure/objectives.ts

Tests: passed: suite/quality-ladder.test.ts an objective is a metric with a target, a unit, an error budget and a window, computed fro; passed: suite/quality-ladder.test.ts the success criteria of the real specification are read as objectives, and commons declare

Cited by: host/report, Quality, pure/objectives, Intellectual Frontiers Quality System

FR-038checkpassing

WHEN an objective's error budget is spent within its window, the system MUST open a nonconformance (FR-015); WHILE budget remains, the remaining budget MUST be shown with the objective.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-ladder.test.ts, quality-system.test.ts: a spent error budget opens a nonconformance of its own, and the remaining budget is shown with the objective

Proved by: quality/suite/quality-ladder.test.ts, quality/suite/quality-system.test.ts

Tests: passed: suite/quality-ladder.test.ts an objective is a metric with a target, a unit, an error budget and a window, computed fro; passed: suite/quality-system.test.ts run as programs: a failed run opens a nonconformance, `quality record` verifies the CAPA t

Cited by: host/report, Quality, Intellectual Frontiers Quality System

FR-039checkpassing

A harness SHOULD declare objectives for the share of its requirements at ifqs:E3 or above, its review debt, its count of not_run cases, the age of its oldest open nonconformance and the number of its stale proofs.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-ladder.test.ts: commons declares the suggested objectives (the share at E3, the review debt, not_run, the oldest open nonconformance, the stale proofs, the figures with no grade)

Proved by: quality/suite/quality-ladder.test.ts

Tests: passed: suite/quality-ladder.test.ts the success criteria of the real specification are read as objectives, and commons declare

Cited by: host/gather, Quality, pure/objectives, Intellectual Frontiers Quality System

Quality: Tiers

FR-040checkpassing

A harness MUST state the tier it claims (ifqs:QualityTier), ifqs:Tier0 (evidence exists: FR-018 to FR-025), ifqs:Tier1 (the system reports itself: FR-026 to FR-039) or ifqs:Tier2 (people see and prove: the console of commons 0021-ifqs FR-037 and FR-041 to FR-044), and MUST claim a tier only where every requirement of it and of the tiers below it is met.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-ladder.test.ts, quality-system.test.ts: quality tier judges a claim against the requirements of the tier and of those below it in the register

Proved by: quality/suite/quality-ladder.test.ts, quality/suite/quality-regulated.test.ts, quality/suite/quality-system.test.ts

Written in: quality/src/pure/tier.ts

Tests: passed: suite/quality-ladder.test.ts a tier is claimed only where every requirement of it and of the tiers below is held by a m; passed: suite/quality-regulated.test.ts the tier claim of a regulated harness in production is refused where a requirement of the ; passed: suite/quality-system.test.ts the register is shown with the grade and day of each row's evidence and checked against th

Cited by: commands, Quality, pure/tier, Intellectual Frontiers Quality System

FR-041checkpassing

WHERE a harness claims ifqs:Tier2, a person's attestation MUST be a recorded sample: what was sampled, the rule and seed that chose it, the result of each, the role and the day, signed.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-attestation.test.ts, quality-tier2-command.test.ts: a person's attestation is a recorded sample (the rule and seed, the population's count and digest, the items, the result of each, the person's name and role and the day) kept as chained records, drawn again from its seed; signing is the commit's, by Git

Proved by: quality/suite/quality-attestation.test.ts, quality/suite/quality-tier2-command.test.ts

Written in: quality/src/attestation/host.ts, quality/src/attestation/rules.ts, quality/src/attestation/sample.ts, quality/src/mod.ts, quality/src/pure/tier2-events.ts, quality/src/tier2-commands.ts

Tests: passed: suite/quality-attestation.test.ts a person's attestation of a sample is a chained record: the sample, the rule and seed, the; passed: suite/quality-attestation.test.ts a sample is drawn by a rule and a seed: the same seed gives the same items, another seed a; passed: suite/quality-tier2-command.test.ts plans, samples, mutation reports and the agents' reviews are recorded through the command

Cited by: attestation/host, attestation/rules, attestation/sample, Quality, pure/tier2-events, tier2-commands, trust/view, Intellectual Frontiers Quality System

FR-042checkpassing

WHERE a harness claims ifqs:Tier2, a test plan MAY be pre-registered, committed and signed before the run it governs, naming its cases and acceptance criteria; the run MUST then report each case not in the plan, and each planned case not run as ifqs:NotRun.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-attestation.test.ts, quality-tier2-command.test.ts: a plan is registered on the branch before its run, the run records its hash (ifc.quality.plan.sha256), and a run that followed it has no finding while a plan registered after, an unknown plan, a case outside it and a planned case not run are named; notRunOfPlan makes the not_run cases

Proved by: quality/suite/quality-attestation.test.ts, quality/suite/quality-tier2-command.test.ts

Written in: quality/src/attestation/plan.ts

Tests: passed: suite/quality-attestation.test.ts a plan is registered before its run and the run records its hash: a run that followed it h; passed: suite/quality-tier2-command.test.ts plans, samples, mutation reports and the agents' reviews are recorded through the command

Cited by: attestation/plan, Quality, tier2-commands, Intellectual Frontiers Quality System

FR-043checkpassing

WHERE a harness claims ifqs:Tier2, a run MAY mutate the code that a test proves and record whether the test failed, and the strength of a proof that results MUST be shown beside its grade.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-attestation.test.ts, quality-tier2-command.test.ts: a mutation report of the tool it names becomes a record, the strength of each proof is shown beside its grade and a strength below the floor lowers a run's grade one rung; the run itself is the tool's

Proved by: quality/suite/quality-attestation.test.ts, quality/suite/quality-tier2-command.test.ts

Written in: quality/src/attestation/mutation.ts

Tests: passed: suite/quality-attestation.test.ts a mutation report becomes a record naming its tool, each requirement's strength is shown b; passed: suite/quality-tier2-command.test.ts plans, samples, mutation reports and the agents' reviews are recorded through the command

Cited by: attestation/mutation, Quality, tier2-commands, Intellectual Frontiers Quality System

FR-044checkpassing

WHERE a harness claims ifqs:Tier2, an agent MAY perform a review mechanism, graded as FR-029 says, and a person MUST sample the agents' reviews (FR-041) at a rate the harness states.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-attestation.test.ts: an agent's review is graded E2, below a test run's E3, a person samples the agents' reviews at the stated rate, and a sample owed, an unattested sample and a review a person found wanting are findings

Proved by: quality/suite/quality-attestation.test.ts, quality/suite/quality-tier2-command.test.ts

Written in: quality/src/attestation/agents.ts

Tests: passed: suite/quality-attestation.test.ts an agent's review is graded below a test run, and a person samples the agents' reviews at ; passed: suite/quality-tier2-command.test.ts plans, samples, mutation reports and the agents' reviews are recorded through the command

Cited by: attestation/agents, attestation/host, attestation/rules, Quality, pure/tier2-events, tier2-commands, Intellectual Frontiers Quality System

Quality: The grade of kept evidence

FR-045checkpassing

A file MUST claim no more than ifqs:E3 for itself (ifc.quality.grade), because what makes it ifqs:E4 is what happens to it after it is written; the grade of kept evidence MUST be the one its note gives, which MUST be ifqs:E4 only where the commit that keeps the file is signed, the chain verifies and the note matches the file's SHA-256, ifqs:E3 where the file is kept and any of these is not so but nothing is broken, and ifqs:E0 where the chain does not verify or the note does not match its file; a note MUST be the lines path, sha256 and grade, one such paragraph for each run kept for the commit, the last being the newest.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-branch.test.ts: a run kept unsigned is E3 and one kept in a signed commit E4 (SSH key made by ssh-keygen), a note is path, sha256 and grade with one paragraph per run, and a note that does not match its file or a chain that does not verify is E0

Proved by: quality/suite/quality-branch.test.ts

Tests: passed: suite/quality-branch.test.ts a commit signed through the host's SSH signing is graded E4 and verifies against the allow; passed: suite/quality-branch.test.ts a commit with no note has no evidence (E0), and a note whose SHA-256 differs from its file; passed: suite/quality-branch.test.ts a Git note under refs/notes/quality on the tested commit gives the evidence file's path, i

Cited by: Intellectual Frontiers Quality System

Quality: Where Tier 1 keeps what it records

FR-046checkpassing

The records of Tier 1 (a nonconformance opened, linked and closed, a CAPA opened, verified and closed, and a statement, a review or a probe's typed result kept as evidence) MUST each be one new file quality/records/NNNNNN-<kind>.json on the quality branch, in a commit that only appends, redacted as FR-025 asks and chained to the file before it by its digest (64 zeros for the first) as FR-022 chains the evidence files, so that a file changed, removed or inserted is found by the branch's verifier; a state MUST be the fold of its events and MUST NOT be a field that is edited, so that no event closes a nonconformance but the one that follows a closed CAPA.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-ledger.test.ts: each event is one redacted file quality/records/NNNNNN-<kind>.json on the quality branch, chained to the file before it, found when changed, removed or inserted, and signed where Git is set to sign

Proved by: quality/suite/quality-ledger.test.ts

Tests: passed: suite/quality-ledger.test.ts a ledger file changed after it was kept, a file removed, and an event that does not follow; passed: suite/quality-ledger.test.ts the ledger's commits are signed through the host's Git signing, and the branch verifies as; passed: suite/quality-ledger.test.ts each event is one file named by its sequence number and kind, redacted of secrets, read ba

Cited by: host/ledger-branch, Quality, pure/ledger, Intellectual Frontiers Quality System

FR-047checkpassing

A proof MUST be held to a cadence by its kind of evidence (FR-030), by default 30 days for a run, 7 days for a probe, 90 days for a statement and a year for a review, and a harness MAY state its own.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-ladder.test.ts: the default cadences are 30 days for a run, 7 for a probe, 90 for a statement and a year for a review

Proved by: quality/suite/quality-ladder.test.ts

Tests: passed: suite/quality-ladder.test.ts a proof is fresh within its cadence, due in its last tenth, stale past it, and stale by ch

Cited by: Intellectual Frontiers Quality System

Quality: Where Tier 2 keeps what it records

FR-048checkpassing

The records of Tier 2 (a test plan registered, a sample drawn, a person's attestation of it and a mutation run) MUST each be a file of the ledger of FR-046, in its chain, and an event that does not follow what came before MUST be refused and written nowhere: an attestation of a sample that gives no result on an item sampled, a result on an item not sampled, no named person, or a second attestation; a plan with no case or a case with no acceptance criterion; a mutation row that does not account for its mutants. A sample MUST record its rule, its seed and the count and digest of its population, so that it can be drawn again, and a run that is governed by a plan MUST name it by the SHA-256 of the plan (ifc.quality.plan.sha256).

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-attestation.test.ts: the records of Tier 2 are files of the ledger in its chain and an event that does not follow is refused (an attestation without a result on each item, no name, a second one; a plan with no case or a case with no acceptance criterion; a mutation row that does not account for its mutants); a sample is drawn again from its seed and a run names its plan by hash

Proved by: quality/suite/quality-attestation.test.ts

Tests: passed: suite/quality-attestation.test.ts a person's attestation of a sample is a chained record: the sample, the rule and seed, the; passed: suite/quality-attestation.test.ts a plan is registered before its run and the run records its hash: a run that followed it h

Cited by: Intellectual Frontiers Quality System

FR-049checkpassing

The strength of a proof (FR-043) MUST be the share of its mutants that its tests detected, and a strength below the floor the harness states (60 % where it states none, and 80 % where it declares a regulated domain and has declared production, a floor it states for itself never lowering that one; a pure function of the declaration and the day, mutationFloor) MUST lower the grade of a proof that is a run by one rung, E4 to E3 and E3 to E2, with both shown; a grade that is not a run's, and a proof that no mutation run measured, MUST keep its grade and say which.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-attestation.test.ts: the strength of a proof is the share of its mutants detected, and below the floor a run's grade is lowered one rung with both shown; a proof no mutation run measured keeps its grade and says so; quality-regulated.test.ts: the floor is 600, 800 for a regulated harness in production (a stated floor never lowers it) and it decides whether the grade is lowered

Proved by: quality/suite/quality-attestation.test.ts, quality/suite/quality-regulated.test.ts

Tests: passed: suite/quality-attestation.test.ts a mutation report becomes a record naming its tool, each requirement's strength is shown b; passed: suite/quality-regulated.test.ts quality tier reads the declaration: a regulated harness in production is refused a tier it; passed: suite/quality-regulated.test.ts the floor of strength is 600, 800 where the harness declares a regulated domain and produc

Cited by: attestation/mutation, host/declaration, Quality, Intellectual Frontiers Quality System

FR-050checkpassing

A harness's record (ifccm.declaration.ts, commons 0020-ifccm FR-010) MUST be able to state the retention period of its evidence in days (retentionDays, a whole number of at least one), and the period a harness states MUST NOT be shorter than the longest retention that applies to its evidence. Evidence MUST be kept on the quality branch for that period and, once the period of the oldest evidence has passed, MUST be archived by a Git tag on the tip of the branch (quality archive --tag NAME), never deleted: no command of the quality system deletes a file, a commit, a tag or the branch, and a tag that exists MUST NOT be moved or replaced. Where the record states no period the command MUST refuse and say so. The period and the day are arguments of the pure judgement; the command reads the day from the clock.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-retention.test.ts: the record states retentionDays (a whole number of at least one, read from ifccm.declaration.ts); the period of the oldest evidence has passed on the day it ends and not before (the period and the day are arguments); quality archive --tag tags the tip of a real quality branch, never over a tag that exists, refuses where no period is stated, and deletes nothing (no option does: --delete is a usage error); that the period is not shorter than the longest that applies to the evidence is the harness's to state and no check reads it

Proved by: quality/suite/quality-retention.test.ts

Written in: quality/src/host/archive.ts, quality/src/pure/retention.ts

Tests: passed: suite/quality-retention.test.ts judgeRetention: the period of the oldest evidence has passed on the day it ends and after ; passed: suite/quality-retention.test.ts quality archive --tag tags the tip of the branch once the period of the oldest evidence ha; passed: suite/quality-retention.test.ts the record states the retention period as a typed field: a whole number of days of at leas

Cited by: host/archive, Quality, pure/retention, Intellectual Frontiers Quality System

FR-051checkpassing

The review debt of FR-028 MUST be counted apart for what rests on an agent's statement or review (reviewDebtByAgent) and for what rests on a person's (reviewDebtByPerson), because an agent's review is graded below a test run (FR-029); the total MUST remain, as the sum of the two, and a count of proved requirements, the proof register, the index and the Trust page MUST show the total with both.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-ladder.test.ts: the review debt of agents and of a person are counted apart, add up to the total and are both shown in the count; quality-trust.test.ts: the page's JSON and HTML carry both

Proved by: quality/suite/quality-ladder.test.ts, quality/suite/quality-trust.test.ts

Tests: passed: suite/quality-ladder.test.ts the review debt of agents is counted apart from a person's: the two add up to the total, a; passed: suite/quality-trust.test.ts the page is generated from the evidence: each requirement with its grade, freshness, day a

Cited by: pure/ladder, Intellectual Frontiers Quality System

Trust: The Trust page

FR-052checkpassing

A Trust page MUST be generated, never written by hand, from the evidence of a harness (the files of the quality branch and the index derived from them, FR-021) and its specifications, and the generator's --check MUST fail where the page differs from what the evidence makes.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-trust.test.ts, quality-tier2-command.test.ts: the page is generated from the quality branch and --check fails where it differs, a page edited by hand included

Proved by: quality/suite/quality-tier2-command.test.ts, quality/suite/quality-trust.test.ts

Written in: quality/src/assessor/host.ts, quality/src/trust/host.ts, quality/src/trust/html.ts, quality/src/trust/view.ts

Tests: passed: suite/quality-tier2-command.test.ts quality trust writes the page and its JSON for the public, --check passes on them and fail; passed: suite/quality-trust.test.ts the page is generated from the evidence: each requirement with its grade, freshness, day a

Cited by: assessor/host, Quality, tier2-commands, trust/host, trust/html, trust/view, Trust

FR-053checkpassing

The page MUST show, for the revision it was made at, each requirement with its grade (ifqs:EvidenceGrade), its freshness (ifqs:FreshnessState) and the day and run of its last proof, the review debt (ifqs:ReviewDebt), each objective with its target and the error budget that remains (ifqs:QualityObjective), and the count of not_run cases beside the counts of passed and failed.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-trust.test.ts: each requirement with its grade, freshness, day and run, the review debt, the objectives with their budgets and the counts of passed, failed and not_run; one self-contained HTML file

Proved by: quality/suite/quality-trust.test.ts

Tests: passed: suite/quality-trust.test.ts the page is generated from the evidence: each requirement with its grade, freshness, day a; passed: suite/quality-trust.test.ts the page file is the one a reader's browser gets: one self-contained HTML document with em

Cited by: Trust

FR-054checkpassing

The page MUST show failures: each failed case, each open nonconformance with its age and each open CAPA MUST be listed before any success, and the page MUST NOT drop, hide or reorder a failure to improve a figure.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-trust.test.ts: failed cases, cases that did not run, open nonconformances with their age and open CAPA come before any figure or success, and none is dropped

Proved by: quality/suite/quality-trust.test.ts

Tests: passed: suite/quality-trust.test.ts failures are listed before any success: the failed case, the case that did not run, the op

Cited by: Trust

FR-055checkpassing

The page MUST state its scope (the harness, the revision, the day it was generated and the span of evidence it covers) and what it does not cover, and MUST NOT state that a harness conforms to, is certified to or complies with a standard, a regulation or a control.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-trust.test.ts, quality-tier2-command.test.ts: the scope, the revision, the day and the span, and what is not covered; a statement of conformity, certification or compliance in what the harness wrote is refused

Proved by: quality/suite/quality-tier2-command.test.ts, quality/suite/quality-trust.test.ts

Tests: passed: suite/quality-tier2-command.test.ts quality trust writes the page and its JSON for the public, --check passes on them and fail; passed: suite/quality-trust.test.ts the page states its scope and what it does not cover, and the generator refuses a page tha

Cited by: Trust

FR-056checkpassing

WHEN the evidence a page was made from is older than its harness's cadence for it (commons 0007-grc FR-011), the page MUST say that it is stale and by how long.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-trust.test.ts: where the newest run is older than the cadence of a run (30 days, 0021-ifqs FR-044) the page says that it is stale and by how many days

Proved by: quality/suite/quality-trust.test.ts

Tests: passed: suite/quality-trust.test.ts a page whose newest run is older than the cadence of a run says that it is stale and by ho

Cited by: Quality, trust/html, trust/view, Trust

Trust: Audiences and redaction

FR-057checkpassing

Each rendering of evidence MUST be made for one audience (ifqs:Audience): ifqs:Public (the page; a figure, an identifier, a grade and a failure's requirement and reason), ifqs:Assessor (the pack of FR-060) or ifqs:Internal (the harness's own console).

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-trust.test.ts: a rendering is made for one audience, and the audiences are the code list ifqs:Audience (Public, Assessor, Internal)

Proved by: quality/suite/quality-trust.test.ts

Written in: quality/src/trust/audience.ts

Tests: passed: suite/quality-trust.test.ts a rendering is for one audience: the public page leaves out a customer's name, an address,

Cited by: Quality, trust/audience, trust/view, Trust

FR-058checkpassing

A rendering for ifqs:Public MUST leave out what commons 0006-signals FR-006 redacts, the names of people, customers and hosts, the paths and names of private repositories and any value a failure message holds beyond its requirement and reason, and MUST say how many values it redacted, so that a redaction is never silent.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-trust.test.ts, quality-tier2-command.test.ts: the public page leaves out a customer's name, an address, a host, a path and a failure's message, and says how many values it redacted

Proved by: quality/suite/quality-tier2-command.test.ts, quality/suite/quality-trust.test.ts

Tests: passed: suite/quality-tier2-command.test.ts quality trust writes the page and its JSON for the public, --check passes on them and fail; passed: suite/quality-trust.test.ts a rendering is for one audience: the public page leaves out a customer's name, an address,

Cited by: Trust

FR-059checkpassing

Redaction MUST be deterministic and MUST NOT change a figure: the same evidence and the same audience MUST give the same bytes, and a count, a grade or a digest of a rendering for a narrower audience MUST equal the same figure of a wider one.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-trust.test.ts, quality-pack.test.ts: the same evidence and audience give the same bytes, and the counts, grades and digests of the public page equal the internal one's

Proved by: quality/suite/quality-pack.test.ts, quality/suite/quality-trust.test.ts

Tests: passed: suite/quality-pack.test.ts the page and the pack are made from the same evidence in one run: each figure of the page ; passed: suite/quality-trust.test.ts a rendering is for one audience: the public page leaves out a customer's name, an address,

Cited by: Quality, trust/audience, trust/host, trust/html, trust/view, Trust

Trust: The assessor pack

FR-060checkpassing

An assessor pack (ifqs:AssessorPack) MUST be a self-contained bundle for one revision and one span of time: the evidence files of that span with their chain (FR-022), the notes that link them to commits, the specifications at the tested revisions, the traceability matrix, the OSCAL assessment results of the runs (FR-005), the ledger and the signatures with the public keys that verify them, and a manifest giving each file's SHA-256 and media type.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-pack.test.ts: the evidence files of the span with their chain, the ledger, the notes, the specifications at the tested revisions, the traceability matrix, the OSCAL results of the runs, the index, the signature and its keys, the verifier and a manifest of each file's SHA-256 and media type

Proved by: quality/suite/quality-pack.test.ts, quality/suite/quality-tier2-command.test.ts

Written in: quality/src/assessor/pack.ts

Tests: passed: suite/quality-pack.test.ts a pack holds the evidence files with their chain, the ledger, the notes, the specification; passed: suite/quality-tier2-command.test.ts quality pack writes a signed pack, its tar with the SHA-256 and the DCAT distribution, and

Cited by: assessor/pack, Quality, tier2-commands, Trust

FR-061checkpassing

A pack MUST give an assessor what the page leaves out for the public (full failure messages, run files and signed envelopes) with only secrets and personal data redacted (FR-058, FR-059), and MUST be marked with its audience and the redactions it made.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-pack.test.ts: the assessor's pack holds the full failure messages and the run files, marked with its audience and its redactions; a file that holds a secret refuses the pack and an e-mail address already in a kept file is named in the manifest, since changing a kept file would break its chain

Proved by: quality/suite/quality-pack.test.ts

Tests: passed: suite/quality-pack.test.ts a pack holds the evidence files with their chain, the ledger, the notes, the specification

Cited by: Trust

FR-062checkpassing

The page and the pack of a revision MUST be made from the same evidence in one run, so that a figure of the page equals the same figure computed from the pack, and a test MUST compare them.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-pack.test.ts: the page and the pack are made from one collected evidence, and each figure of the page equals the same figure computed from the pack

Proved by: quality/suite/quality-pack.test.ts

Tests: passed: suite/quality-pack.test.ts the page and the pack are made from the same evidence in one run: each figure of the page

Cited by: assessor/host, assessor/verify-pack, Quality, Trust

FR-063checkpassing

A pack MUST be offered as a download of a file (a DCAT distribution, commons 0019-mizan-integrations FR-018), with its SHA-256 beside it.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-pack.test.ts, quality-tier2-command.test.ts: the pack as a deterministic tar with its SHA-256 beside it and a DCAT distribution that names it

Proved by: quality/suite/quality-pack.test.ts, quality/suite/quality-tier2-command.test.ts

Tests: passed: suite/quality-pack.test.ts a pack is offered as a deterministic tar with its SHA-256 beside it and a DCAT distributio; passed: suite/quality-tier2-command.test.ts quality pack writes a signed pack, its tar with the SHA-256 and the DCAT distribution, and

Cited by: assessor/pack, Quality, Trust

Trust: Offline verification

FR-064checkpassing

A person MUST be able to verify a pack with no network and no account: the command MUST check the manifest's digests, the hash chain of the evidence files, the signature of each signed envelope against the keys in the pack, that each note names a file the pack holds, and that the figures of the pack's summary equal the figures computed from its files, and MUST name the first thing that fails.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-pack.test.ts, quality-tier2-command.test.ts: with no network, the manifest's digests, the chains, the signature of each envelope against the keys of the pack, the notes and the figures, naming the first thing that fails

Proved by: quality/suite/quality-pack.test.ts, quality/suite/quality-tier2-command.test.ts

Written in: quality/src/assessor/verify-pack.ts, quality/src/assessor/verify.ts

Tests: passed: suite/quality-pack.test.ts a pack verifies offline: a changed file is named, a broken chain is named, a key the pack ; passed: suite/quality-pack.test.ts the keys of an allowed-signers file made by ssh-keygen are read, and a line is made for a ; passed: suite/quality-pack.test.ts the verifier is small typed TypeScript with no import, shipped in the pack, and runs from ; passed: suite/quality-tier2-command.test.ts quality pack writes a signed pack, its tar with the SHA-256 and the DCAT distribution, and

Cited by: assessor/verify-pack, assessor/verify, Quality, tier2-commands, Trust

FR-065checkpassing

A verification that cannot check part of the pack (a key that is not in the pack, a file the manifest lists and the pack lacks) MUST report that part as not_run with the reason, and MUST NOT report the pack as verified.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-pack.test.ts, quality-tier2-command.test.ts: a key the pack lacks, a file the manifest lists and the pack lacks and an unsigned pack are not_run with the reason, and the pack is not reported verified

Proved by: quality/suite/quality-pack.test.ts, quality/suite/quality-tier2-command.test.ts

Tests: passed: suite/quality-pack.test.ts a pack verifies offline: a changed file is named, a broken chain is named, a key the pack ; passed: suite/quality-tier2-command.test.ts quality pack writes a signed pack, its tar with the SHA-256 and the DCAT distribution, and

Cited by: assessor/verify-pack, Trust

FR-066checkfailing

The verifier MUST be small, typed TypeScript that runs on Bun and Node 26 with no dependency, and MUST be included in the pack so that the pack can check itself.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-pack.test.ts: the verifier is one typed file with no import, shipped in the pack with its command, run from inside the pack on this runtime and on Node 26

Proved by: quality/suite/quality-pack.test.ts, tests/release/quality-assessor-package.test.ts

Tests: passed: suite/quality-pack.test.ts the verifier is small typed TypeScript with no import, shipped in the pack, and runs from ; failed: tests/release/quality-assessor-package.test.ts the packed and installed Quality finds the verifier's two files from dist/assessor under N

Cited by: assessor/pack, assessor/verify-pack, assessor/verify, Quality, Trust

Trust: What a pack cannot redact

FR-067checkpassing

Redaction MUST be at the source: every writer of a file kept on the quality branch (the records of runs, the events of the ledger of every kind, plans, samples, attestations, mutation runs and the notes) MUST redact the file of secrets and e-mail addresses before it is kept (FR-025), a person's name being data that stays. A file kept MUST NOT be changed to redact it for a pack, because its digest is in a chain; the pack's refusal is the backstop for a file kept before this rule or by another writer: a pack MUST refuse a kept file that still holds a secret, naming it, so that its source is fixed and kept again, and MUST name in its manifest the personal data (an e-mail address) that a kept file retains; the files a pack makes itself MUST be redacted and the redactions counted (FR-061).

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-pack.test.ts: a kept file that holds a secret refuses the pack and names the file; personal data a kept file retains is named in the manifest; the files the pack makes are redacted and counted; quality-redaction.test.ts: redaction is at the source: the ledger's events of every kind (Tier 1 and Tier 2), a run kept with a secret and an e-mail address, its note and the commit messages of the branch hold neither (a person's name stays)

Proved by: quality/suite/quality-pack.test.ts, quality/suite/quality-redaction.test.ts

Tests: passed: suite/quality-pack.test.ts a pack holds the evidence files with their chain, the ledger, the notes, the specification; passed: suite/quality-redaction.test.ts a run kept with a secret and an e-mail address in a failure message is written redacted, a; passed: suite/quality-redaction.test.ts events of every kind written to a real quality branch hold no secret and no e-mail address; passed: suite/quality-redaction.test.ts the ledger redacts every text of an event of every kind at the source, Tier 1 and Tier 2; ; passed: suite/quality-redaction.test.ts a person's own e-mail address as the name of the person is redacted; a name is kept

Cited by: pure/ledger, Trust

FR-068checkpassing

The page for ifqs:Public MUST name an open nonconformance by its identifier, the identifier of its requirement, its state, its age and a code from the closed list of causes (failed, stale, probe-failed, budget-spent), and MUST NOT show the text of the requirement, the reason the nonconformance was opened, the text of the corrective action of its CAPA or any other text of its record (a CAPA is named by its identifier, its state and the named test); the renderings for ifqs:Assessor and ifqs:Internal MUST show the text of the requirement as the specifications state it at the tested revision, the reason and the corrective action. What the public page withholds is counted among its redactions (FR-058).

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-trust-capa.test.ts: the Public page names a CAPA by identifier, state and named test and withholds its corrective-action text, counted among the redactions; quality-trust.test.ts: the public page names an open nonconformance by its identifier, its requirement's identifier and a cause code only (a private marker in its reason and the requirement's sentence never reach it), the Assessor and Internal pages show the requirement's text read from the specifications at the tested revision and the reason; the corrective action text of a CAPA is not yet withheld from the public page

Proved by: quality/suite/quality-trust-capa.test.ts, quality/suite/quality-trust.test.ts

Written in: quality/src/trust/requirement-text.ts

Tests: passed: suite/quality-trust-capa.test.ts the Public page names a CAPA by its identifier, state and named test and withholds the tex; passed: suite/quality-trust.test.ts requirementTextOf reads a requirement's text from a specification, with the lines that con; passed: suite/quality-trust.test.ts the public page names an open nonconformance by its identifier, its requirement's identifi

Cited by: Quality, trust/requirement-text, Trust

FR-069checkfailing

When the pack is made, the verifier's two source files MUST be found from the module that makes it in the source layout and in the published layout (the compiled dist/assessor/ of the installed package, which ships the files in src/assessor/), on Bun and on Node 26, and where a file is in neither place the pack MUST be refused with a typed error naming the file and the places looked in.

Enforced (check): .github: cd commons/quality && bun test suite/ — quality-verifier-locator.test.ts: the verifier files are found beside the module and in the src/assessor of the package from its compiled dist/assessor, and a missing file is a typed error naming the places; tests/release/quality-assessor-package.test.ts (the release): the packed tarball, installed, makes the pack on Node 26 and on Bun

Proved by: quality/suite/quality-verifier-locator.test.ts, tests/release/quality-assessor-package.test.ts

Tests: passed: suite/quality-verifier-locator.test.ts the verifier's files are found beside the module, in the src/assessor of the package from ; failed: tests/release/quality-assessor-package.test.ts the packed and installed Quality finds the verifier's two files from dist/assessor under N

Acceptance scenarios

  1. Given a suite and a requirements list, When ifc test run runs it on Bun and on Node, Then one OTLP record of the run is written with its reports, and the run fails where a requirement is neither proven nor declared reviewed, per FR-002, FR-003 and FR-004.
  2. Given a record with a case that did not run, When it is rendered, Then the case is not_run with its reason and is counted apart from passed and failed, per FR-013 and FR-019.
  3. Given a record, When it is kept on the quality branch, Then it is one new file chained to the file before it and a note on the tested commit gives its path, digest and grade, per FR-021, FR-022 and FR-023.
  4. Given a failed run or a stale proof, When the ledger is read, Then a nonconformance is open by itself, and it closes only through a closed CAPA, per FR-015, FR-032 and FR-035.
  5. Given the evidence of a span, When the Trust page and the assessor pack are made, Then each figure of the page equals the same figure computed from the pack and the pack verifies offline, per FR-059, FR-062 and FR-064.

Out of scope

  • The ontology of the quality system (ifqs:), which is the library ontology's (@intellectual-frontiers/ontology/ifqs).
  • The record of one test and the registration of tests, which are the library test's (@intellectual-frontiers/test).
  • A harness's own console and the publication of commons' own Trust page, which are planned in commons 0021-ifqs and commons 0022-trust.

Edge cases

  • A repository with no quality branch: its commits are at ifqs:E0, per FR-021, FR-022 and FR-023.
  • A record that names a person or holds a secret: refused before it is committed, per FR-025.
  • A run killed before a test ended: the test is cancelled, per FR-001.

Assumptions

  • Git, and ssh-keygen where evidence is signed, are installed where the quality branch is kept; a test that needs either is skipped where it is not.
  • A role is enough to say who approved a closure in this public repository; a harness that must name people adds them in its own records.

Open questions

  • None.

Key entities

  • Run - one trace of a suite with its record, reports and ledger entry.
  • Quality branch - the append-only branch that keeps each record as one immutable file.
  • Ledger - the chained events of nonconformances, CAPA, samples, plans and attestations.
  • Trust page - the page made for one audience from the evidence.
  • Assessor pack - the signed archive of the evidence with its verifier.

Success criteria

SC-001success criterion

Every claim of proof on the page of a harness can be followed to an evidence file whose chain verifies.

SC-002success criterion

A failure appears as a nonconformance without a person having to notice it.

SC-003success criterion

No figure of proof is shown without its grade and its review debt.

Review & acceptance checklist

  • [x] Every requirement is testable (MUST / MUST NOT), not aspirational
  • [x] No company fact is asserted here
  • [x] Every open item is marked, not silently decided

Cited by

assessor/host, assessor/pack, assessor/verify-pack, assessor/verify, attestation/agents, attestation/host, attestation/mutation, attestation/plan, attestation/rules, attestation/sample, commands, host/archive, host/branch, host/declaration, host/gather, host/git, host/ledger-branch, host/report, host/test-run, Quality, pure/chain-files, pure/chain, pure/freshness, pure/index-file, pure/ladder, pure/ledger, pure/names, pure/objectives, pure/record, pure/render, pure/retention, pure/tier, pure/tier2-events, pure/time, tier2-commands, trust/audience, trust/host, trust/html, trust/requirement-text, trust/view, Test evidence, Intellectual Frontiers Quality System, Trust

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