Frame
Bicycle Model A  >   Frame

Frame Audit view

Provenance — database /opt/truke/kf/data/kf.db  ·  49 items, 54 edges, 127 revisions  ·  last write 2026/09/05 19:57:45.133  ·  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

Requirements0
Rows in total1
Headings (not checks; no status)1
Rolled up beneath0
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

1 items beneath this scope. The ten most recently written:
ItemModifiedBy
Frame 2025/05/01 evalUser
All, by date CSV
Add &since=YYYY-MM-DD for a drift report against the opening meeting.

Events on the record

0
major
0
minor
0
observations
0
events in all
Grades are tags, so these counts are of what the organization has graded — an ungraded event carries none of them and appears only in the total.

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.
  • 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.



KF  ·  49 items, 54 edges, 127 revisions  ·  last write 2026/09/05 19:57:45.133  ·  config rev 019ec013-99e4-77f4-89db-d53d0eb57028