Factory docs, home
Page navigation

Reference document, shown as written except that local paths appear as placeholders. Where it describes the Factory as intended, read it as design, not current state: only local infrastructure is accepted, no release, customer value or scheduled automation is established, and all 27 customer-value epics remain open. Current state: Factory model.

One family, twenty module personalities and four little record companions. Every character keeps Plumb’s hanging loop, collar, pointed body and warm expression. Stature, eyes, colour and a signature prop make the job easier to recognise. These are editorial teaching characters, not agents, services or progress indicators. Read each module’s own status for what exists.

Asset catalogue · Family specification and generation prompts · Construction and use

Module personalities

  • 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.
  • An indigo bob with curious eyes and a labelled specimen. Evidence / Assurance · The curator — “Show me what happened.” Keeps observations attributable and separate from the judgement made from them. Full-size PNG.
  • A slender blue bob passing a violet relay baton. Execution · The conductor — “One owner, one baton.” Tracks Run and Attempt ownership, including how each ends. 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 broad blue bob behind a single-latch gate. Attempt fence / workspace · The gatekeeper — “This workspace has one owner.” Gives an Attempt a private workspace and a fence against stale ownership. Full-size PNG.
  • A periwinkle bob with a loupe and folded report. Guarded verification / recovery · The double-checker — “Read it again before you settle.” Checks evidence under ownership and recovers unfinished fixture Attempts. Full-size PNG.
  • A stout blue bob carrying a gear under glass. Confined executor · The experimenter — “Keep the experiment contained.” Runs one bounded program against read-only snapshots. Full-size PNG.
  • An indigo bob carrying a tied, sealed parcel. Repository · The packer — “The exact parcel, every time.” Seals Candidate bytes and guards a local branch move; reconciles an uncertain result. Full-size PNG.
  • A teal bob with spectacles and tabbed index cards. Portfolio · The organiser — “Every fact has a place.” Registers projects and collects what their sources report. Full-size PNG.
  • A wide-eyed blue bob holding a three-pane window. Dashboard · The host — “A clear window onto the work.” Presents sourced progress, usage and actions without inventing missing results. Full-size PNG.
  • A slender violet bob with a map and compass. Project guidance · The navigator — “Keep the agreed direction in view.” Keeps versioned project values so guidance can be named precisely. Full-size PNG.
  • A small azure bob raising a single bookmark. Required actions and blockers · The spotter — “Here is what needs your attention.” Brings reported required actions and blockers into one list. Full-size PNG.
  • A playful violet bob with a pencil and blank sketchbook. Producers · The sketcher — “Here is an idea to examine.” Asks a model for proposed edits; a proposal is not an accepted change. Full-size PNG.
  • An indigo bob inspecting a parcel through a lens. Repository Assurance · The examiner — “Check this Candidate independently.” Judges repository Candidates from their stored Evidence and exact pins. Full-size PNG.
  • A broad teal bob beside a ticketed turnstile. Product gate and delivery records · The steward — “Make room for the right small slice.” Bounds admitted delivery work and keeps delivery records. Full-size PNG.
  • A periwinkle bob carrying sample jars on a tray. Repository collector · The field collector — “Bring back observations, not guesses.” Runs a Candidate’s checks in the sandbox and stores what it observed. 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.
  • A round teal bob with a numberless clock. Lifecycle schedule · The timekeeper — “A named check at the right time.” Keeps proposed check schedules; a schedule record does not prove a job ran. Full-size PNG.
  • A curious azure bob with a small telescope. Discovery sources · The explorer — “What does the source actually say?” Reads commissioned public pages and keeps checkable quotations. Full-size PNG.
  • A slate-blue bob carrying two distinct keys. Service access · The custodian — “Know where access belongs.” Maps services and credential references by name, never by secret value. Full-size PNG.

Little record companions

These compact companions explain objects that travel between modules. They do not represent additional components. Keep them in teaching material; actual Verdicts, Assessments, access decisions and failure messages stay plain.

  • A tiny blue bob with a request slip. Command companion · Command — “One request, one identity.” A request with a stable identity; the journal returns its recorded answer on retry. Full-size PNG.
  • A tiny violet bob holding a parcel. Candidate companion · Candidate — “These are the proposed bytes.” A sealed proposal to inspect; it is not yet an accepted or released change. Full-size PNG.
  • A tiny teal bob with a paper scroll. Receipt companion · Receipt — “Record what was observed.” A record of an observed result; an uncertain effect stays uncertain. Full-size PNG.
  • A tiny periwinkle bob comparing two cards. Assessment companion · Assessment — “Compare the result with the intent.” Compares observed outcomes with the intended result; activity alone is not value. Full-size PNG.

Recognise without colour

Each character has a distinct prop and a written canonical name. Colour is personality, never status, seniority or capability. Keep the complete transparent canvas; do not crop away the hanging loop or the prop. Use a module portrait at 192 px or larger, a companion at 96 px or larger, and the existing identity mark for navigation. A neighbouring explanation remains understandable with images disabled.

Source: docs/brand/plumb-family.md