Factory docs, home
Page navigation

Pre-release documentation. Proposed designs are labelled in the page; acceptance evidence is maintained in the build review. Local paths appear as placeholders. Current state: Build review.

Derivatives of Plumb (factory-brand-v1) for the Factory's modules and decision domains. These are editorial concept studies. They are not product features, status indicators or evidence of progress. Construction: geometry. Reviewed images: assets.

Current family: thirty-five modules and four companions

Meet the Plumb family is the current editorial set. Each module guide has its own standalone portrait; the gallery pairs canonical names with a personality, recognisable prop and explanation of the job. The machine-readable specification records all mappings and prompts.

The owner requested more individual features and colours on 29 September 2026. This extends the original prop-only direction: stature, eye shape and spacing, spectacles and editorial colour can now vary while the hanging line, collar and pointed body stay recognisable. See construction and use.

Portrait coverage follows the thirty-five human module guides, including modules still in progress. A character says nothing about acceptance or completion. Command, Candidate, Receipt and Assessment have smaller teaching companions; they are records or concepts, not extra services. Repository's single module portrait covers sealing and integration together.

The original plates below remain historical design assets, intact and available. Their acceptance wording is a dated snapshot, not the current module status.

Accepted local modules: two family plates

The dispositions and rows below come from the local implementation review as of 2026-09-28. Acceptance means independently reviewed local infrastructure. It is not a completed epic, a release or a customer benefit.

Every row maps to real source. None of these modules is a separate service.

Each module has exactly one labelled position on one of two plates:

  • Plate 1: six modules for records and runs.
  • Plate 2: five modules for isolation, delivery and visibility.

Both plates use pale blue rounded-square tiles.

Plate · positionAccepted module (canonical label)Maps toSourceDispositionPropNickname
1 · 1Command journalDurable facts and messages (design)src/journal.ts, src/canonical-json.tsAccepted local reads and writesbound ledger with a ribbon bookmarkPlumb with the ledger
1 · 2Evidence / AssuranceEvidence store foundation; Assurance judgementsrc/evidence.ts, src/assurance.tsAccepted for trusted local fixturesglass specimen case with a blank tagPlumb the curator
1 · 3ExecutionExecution foundation: Run and Attempt lifecycle, durable cancellationsrc/execution.tsAccepted for trusted local supervisionrelay batonPlumb with the baton
1 · 4Local fixture workerExecution: bounded worker Attempts on fixed fixturessrc/local-worker.ts, src/fixture-child.ts, src/fixture-gate.ts, src/fixture-manifest.tsAccepted for fixed trusted fixturessmall closed toolboxPlumb at the bench
1 · 5Attempt fence / workspaceExecution: per-Attempt ownership and private workspacesrc/attempt-fence.ts, src/attempt-workspace.tsAccepted for trusted local POSIX fixtureslow garden gate with a latchPlumb at the gate
1 · 6Guarded verification / recoveryAssurance verification under Execution ownership, with bounded replacementsrc/guarded-verification.ts, src/attempt-ledger.tsAccepted for trusted fixturesround loupe over a folded blank reportPlumb double-checks
2 · 1Confined executorExecution: one bounded program against read-only snapshotssrc/confined-executor.tsAccepted for the tested stateless macOS boundarytiny gear under a glass clochePlumb under glass
2 · 2Repository sealing / exportOperations: exact prospective Candidate and manifestsrc/repository.tsAccepted for fresh owned local repositoriesparcel tied with string and a plain round sealPlumb seals the parcel
2 · 3Repository integrationOperations: guarded local ref update with reconciliationsrc/repository.tsAccepted as a local effect primitiverailway points leverPlumb at the points
2 · 4PortfolioOperations-owned registry and read-only sourced viewssrc/portfolio.ts, src/portfolio-inventory.tsAccepted for local metadata registration and sourced factsindex-card drawer with blank tabsPlumb the registrar
2 · 5DashboardLocal browser interface: typed contract, pure projection, HTTP composition, presentation (dashboard)src/dashboard-contract.ts, src/dashboard-view.ts, src/dashboard-server.ts, apps/dashboard/srcAccepted local browser interfacean empty window frame on a small standPlumb at the window

The composition and support files src/local-factory.ts, src/cli.ts, src/factory-support.ts and src/errors.ts belong to the modules they compose, so they get no study of their own.

Family v2 covers all documented modules, including work in progress, without implying acceptance. The historical plate membership above is retained for provenance; current scope and status remain on each module guide.

Decision domains: documented derivatives

These are the domains from the design. No domain has a completed customer-value epic. These studies are documented only, and no domain image is planned yet. When one is made, it uses a pale blue circle backdrop.

Canonical domainDecidesPropNickname
PlanningObjectives, Outcomes, Assessments, priority, retirementblank folded map and small compassPlumb the scout
DeliveryDesign, implementation and repair of a Slicehand plane lifting one curl of shavingPlumb the joiner
AssuranceIndependent Scenarios, checks and Verdictsspirit level with a round loupePlumb the inspector
OperationsIntegration, release, health, rollback, recoverysmall unlit signal lanternPlumb the keeper
GrowthDocs, site and launch from confirmed release factsoversized pen nib over a blank cardPlumb the scribe

Completed-epic asset rule

On 2026-09-28 all 27 epics (E01–E27) were open, so no completed-epic pack exists.

A pack becomes due only when an epic closes with independent closure evidence. The pack's first line links to that evidence: the Assessment, Verdict or Receipt.

A pack contains:

  1. A caption: the epic ID and canonical title, plus a factual one-line outcome copied from the evidence. It never claims more than a Supported Assessment.
  2. The study for the surface the epic changed. Reuse an existing study where one exists, or make one new study under this art direction.
  3. A record in assets: consistency, accessibility and truth-state checks, with provenance.

If the epic has no visible surface, the pack records "no visible change; no artwork". An epic closed as learning after a rejected or inconclusive result gets no celebratory asset.

Source: docs/brand/modules.md