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.

Factory separates recording work, running checks and judging results. Use these explanations to understand one part. Each links to its exact contract and limits. The build review owns acceptance evidence.

This page is level 4 of the map; start at the Factory at a glance for how the parts compose into Workflows. These parts belong to the Module → Workflow → Factory adoption architecture. Local acceptance does not yet prove standalone use. See independent adoption requirements and gaps before choosing a part for another system.

See every module's information flow and the workflow diagrams.

Modules

Meet the modules

Distinct personalities, one recognisable Plumb family. Each portrait uses a prop to explain its module's job. Meet the illustrated modules and little record companions.

  • A wide blue bob, round spectacles and a ribbon-bound ledger. Command journal · The archivist. "Remembers the promise." Writes an accepted Command, result and Events together; a retry gets the recorded answer. Full-size PNG.
  • A squat teal bob with a compact toolbox. Local fixture worker · The tinkerer. "Small experiment, tidy bench." Runs a bounded built-in fixture and records what happened. Full-size PNG.
  • A tall violet bob comparing cards with a tuning fork. Intelligence · The matcher. "Which tool fits this task?" Records which modules may use models and why; selection is not qualification. Full-size PNG.

Module guides

  • Factory workflow Composes explicit prepared prefixes through thirteen native stage kinds under their original owners; bounded local individual-stage and concert proof is independently accepted in the joint qualification. Exact-main CI and complete live Workflow adoption remain separate.

    In progress

  • Knowledge Keeps permitted lessons with current source checks, protected context and independently reviewed loss; bounded installed K1 proof is independently accepted in the joint qualification. Broader Planning and live-adoption gates remain open.

    In progress

  • Command journal Records each Command once, with its result and Events.

    Accepted

  • Evidence / Assurance Keeps what was observed and gives a Verdict.

    Accepted

  • Execution Records who owns each Run and Attempt, and how each ended.

    Accepted

  • Local fixture worker Runs a built-in test fixture and records what happened.

    Accepted

  • Attempt fence / workspace Gives each Attempt one gate and a private workspace.

    Accepted

  • Guarded verification / recovery Checks a fixture under one owner and settles crashed Attempts.

    Accepted

  • Confined executor Runs one small program in a macOS sandbox and reports what it saw.

    Accepted

  • Repository sealing / export and integration Seals a Candidate and moves a local branch at most once.

    Accepted

  • Portfolio Registers local projects and shows what sources report.

    Accepted

  • Dashboard A browser page on this computer for progress, usage, actions and values.

    Accepted

  • Project guidance Up to eight core values per project, kept as revisions.

    Accepted

  • Required actions and blockers One list of what sources report needs attention.

    Accepted

  • Producers (Claude and OpenAI) Asks an AI model once for proposed edits; neither Claude Code nor OpenAI can run live yet.

    Accepted

  • Repository Assurance Judges a repository Candidate from stored Evidence; the Delivery draft composes it.

    Accepted

  • Verification workflow Verifies caller-owned external seals and recovers exact original proof witnesses without re-collection; bounded local native and installed proof is independently accepted in the joint qualification. Exact-main CI and complete live Workflow adoption remain separate.

    In progress

  • Implementation workflow Runs one caller-bound original worker attempt, retains temporal host Evidence and seals a validated Candidate; bounded local native and installed proof is independently accepted in the joint qualification. Exact-main CI and live-provider adoption remain separate.

    In progress

  • Delivery composition (D4) Binds, freezes, seals and verifies authored work through existing gates; source composition in progress, with combined acceptance still open.

    In progress

  • Checkout Git (R7) Reads bounded committed blobs for binding; source reader in progress, with independent acceptance still open.

    In progress

  • Product gate and delivery records Decides what delivery work a Product may start, and keeps each delivery record once.

    Accepted

  • Repository collector Runs a Candidate's checks in the sandbox and stores what it saw; the Delivery draft composes it.

    In progress

  • Intelligence Says which modules may use an AI model, which one and why; most never do. Accepted, with its changes for the proposed discovery and post-development design; no model is qualified yet.

    Accepted

  • Lifecycle schedule Keeps the timetable of the proposed nightly checks, one named check at a time; nothing runs on a schedule yet.

    In progress

  • Discovery sources Reads the public pages you commission and keeps checkable quotes; tried only on this computer; accepted on independent review, and nothing uses it yet.

    Accepted

  • Service access Maps the outside services a Product uses and where their credentials live, by name only; increment 1, on test files.

    Accepted

  • Owner policy Records asks, answers and reported minutes; keeps stated rules without applying them.

    Accepted

  • Branch health Reads a branch's checks and workflow history and records unresolved failures; no live polling is running.

    Accepted

  • Owner digest Turns recorded facts into cited updates on the Dashboard; nothing is scheduled or sent.

    Accepted

  • Capacity Planning Shows conditional native-unit ranges, deficits and unknowns under explicit assumptions; reserves no quota.

    Accepted

  • Operational Signals Accepts caller-authenticated redacted observations with durable identities and honest historical coverage.

    Accepted

  • Provider events Projects a scoped notification about one committed fact, with current caller permission.

    Accepted

  • Provider subscriptions Keeps bounded private subscription lifecycle and signed verification through caller-owned ports; no live MCP host or application delivery.

    Accepted

  • Temporal Planning Checks attributed dates against dependencies, retaining disagreements and unknowns.

    Accepted

  • Material Timing Checks proposed material slots against pinned calendar rules and caller-approved facts.

    Accepted

  • Proposal ownership Keeps immutable proposals and permanent first-offer ownership; starts no delivery.

    Accepted

  • Guidance acceptance Applies one original offered Guidance command and reconciles recorded history under current permission.

    Accepted

  • Provider event requests Routes list, subscribe and unsubscribe to the existing caller-owned host; no server or application delivery.

    Accepted

  • Provider Guidance tools Inspects one original proposal or asks its existing receiver to apply it under current permission; no new authority or automatic retry.

    Accepted

  • Prevention register Says whether the prevention for each recorded failure cause is in place in each project, from reads it is given; it can now save its answers and the owner's exemptions, in a draft awaiting review, with nothing rolled out.

    In progress

  • Marketing Workflow Renders copy only from typed, current facts and refuses unsupported claims block by block, and can run as a resumable job that lets a drafting tool propose wording the same rules check; bounded local native and installed proof is independently accepted in the joint qualification; live drafting and publication remain unqualified.

    In progress

  • Work items Keeps one list per project of who is doing which work, turns away a second claim on the same work, and reports branches that are finished or abandoned; it deletes nothing.

    In progress

  • Milestone objectives Keeps owner intent and independently reviewed plans with source-attributed dates; Research, admission and resource ETA remain separate gates.

    In progress

  • Provider event delivery Sends one retained notification through a separately commissioned caller; no live connector is established.

    In progress

  • Provider diagnostics Attributes retained provider facts without changing the original outcome.

    In progress

  • Research semantics Analyses retained native quotes under a separate caller commission and shared allowance; injected structured collaborators propose inert findings, never feature admission.

    In progress

  • Research jobs Retains one commissioned collection with attributed citations; selecting work is separate.

    In progress

  • Research into a milestone plan Prepares a draft from retained Research for independent review; implementation admission remains unavailable.

    In progress

  • From a plan to a work brief Copies one selected generation into an attributed draft; grants no dispatch or resource dates.

    In progress

  • Calendar Shares civil-date arithmetic and fixed zone conversion rules; caller modules retain domain limits.

    In progress

Source: docs/explanation/modules.md