Factory docs, home
Page navigation

See the input → responsibility → output diagram.

What it does for you: It runs one of the Factory's four built-in test fixtures as a real process, with limits on time and output. It records exactly what happened as Evidence and leaves the judgement to Assurance.

A squat teal bob with a compact toolbox.

Meet the tinkerer. Small experiment, tidy bench. Runs a bounded built-in fixture and records what happened. Meet the whole Plumb family.

How it links: It takes a pinned request, a live fence hold and a private workspace from Guarded verification / recovery and Attempt fence / workspace, for one Attempt as Execution names it. It gives the stored process Evidence to Evidence / Assurance.

Honest limits:

  • It runs only the fixed fixtures (pass, fail, hang, noisy). It is not a sandbox for arbitrary code.
  • If a process cannot be confirmed stopped, or its folder holds something unexpected, the worker leaves it in place and says so. It does not claim cleanup.
  • It was tested on one macOS host with Node 26.8.1. Power loss has not been tested.

Status: Accepted for fixed trusted fixtures. Acceptance and evidence.

Contract and limits

A separate application can try the private fixture-resource package, providing its own Journal, Evidence store and recovery context. This draft uses a distinct compiled protocol and was accepted locally on 1 October 2026. Historical source runs remain readable and are never silently upgraded.

Source: docs/guide/local-fixture-worker.md