Factory docs, home
Page navigation

What it does for you: It keeps what the local fixture worker observed for each check as a record named by its own contents and pinned to the exact Candidate, Run and Attempt. A record that has been altered on disk is refused when read. Assurance then reads the named records back and gives a Verdict: Verified, Failed or Inconclusive. A check that plainly failed gives Failed. Anything missing, altered or unclear never counts as a pass.

Module studies, plate 1: six Plumb studies for the records-and-runs modules, each labelled with its module's name.

Plate 1, position 2, Plumb the curator: a glass specimen case with a blank tag. The plate is shown whole.

How it links: Takes observations from the Local fixture worker, pinned to Execution Runs and Attempts, and stores those of the Repository collector (accepted, not yet called) · Gives Verdicts to Guarded verification / recovery, which re-checks them later against the same records.

Honest limits:

  • It trusts the local collector. Anyone who can write the store's folder can add well-formed records, and the collector name is a label, not proof of identity.
  • A Verdict covers only the records it was given, on local synthetic fixtures. It is not a release, production or customer claim, and survival after power loss is not tested.

Status: Accepted for trusted local fixtures (local review, 28 September 2026). Local development only; the epics it serves remain open.

Agent reference →

Source: docs/guide/evidence-assurance.md