Prototype build

Provenance — database /opt/truke/kf/data/kf.db · 49 items, 54 edges, 127 revisions · last write 2026/09/05 18:14:52.416 · configuration revision 019ec013-99e4-77f4-89db-d53d0eb57028 (2026/06/13 08:22:50.596)

Record these in the audit plan. Any edit to the requirement library during the audit period is itself a finding.

Compliance register

Requirements	0
Rows in total	1
Headings (not checks; no status)	1
Rolled up beneath	0
Reconciliation	0 + 0 = 0 vs 0 reconciled

Open the register CSV XLSX

Before quoting any of these numbers: `done` is not conformity, `missing` is not "no evidence exists", and a `done` row with obligations still open beneath it is not four-fifths done. The register page glosses each status where it is read.

Recent changes

3 items beneath this scope. The ten most recently written:

Item	Modified	By
Pilot production	2026/08/01	evalUser
Validation and endurance testing	2026/08/01	evalUser
Prototype build	2026/08/01	evalUser

All, by date CSV

Add &since=YYYY-MM-DD for a drift report against the opening meeting.

Events on the record

major

minor

observations

events in all

Where else to look

The risk model — the scales, the rules in order, and which values carry no definition. Re-derive a rating without asking anyone.
Revisions of this item — time, author and the author's own statement of what changed, with a diff per revision.
Dashboard — the register counted per component, as numbers.

Documents in scope — the records themselves.
Actions in scope — processes, requirements and the work owed.
Objects in scope — what the organization is made of.

Free-text search within scope — the cross-read: the same asset id, batch number or date appearing in two records with no edge between them is where the findings that matter come from, and no query finds it for you.
Export this session's trail — every page opened and every tool called, to file with the audit.

Prototype build Audit view

Compliance register

Recent changes

Events on the record

Where else to look