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.

See what each part does, where its inputs come from and what you can do with its result. Start with the job you want, or follow one module without adopting the whole Factory.

Factory is local infrastructure in development. A module diagram describes its responsibility; it does not prove a complete Workflow, live provider or customer outcome. Current acceptance and evidence.

Choose your view

  • Workflow diagrams

    Follow fixture verification, repository delivery, research, marketing, operations, guidance, notifications, planning, repair, access and work coordination. Every flow names its inputs, result and remaining boundaries.

  • Recording, ownership and fixture checks

    Calendar; Command journal; Execution; Attempt fence / workspace; Local fixture worker; Evidence / Assurance; Guarded verification / recovery.

  • Repository delivery components

    Factory workflow; Implementation Workflow; Verification Workflow; Confined executor; Checkout Git; Delivery; Producers; Repository sealing / export and integration; Repository collector; Repository Assurance; Product gate and delivery records.

  • Projects and operational understanding

    Portfolio; Dashboard; Project guidance; Required actions and blockers; Branch health; Owner policy; Owner digest; Service access; Operational signals; Prevention register; Work items.

  • Research and planning components

    Research semantics; Knowledge; Milestone objectives; Milestone research handoff; Milestone work brief; Research jobs; Intelligence; Lifecycle schedule; Discovery sources; Temporal Planning; Capacity Planning; Material Timing.

  • Proposals and provider boundaries

    Provider diagnostics; Provider event delivery; Proposal ownership; Guidance acceptance; Provider events; Provider subscriptions; Provider Events RPC; Provider Guidance tools.

  • Marketing components

    Marketing Workflow.

Read a module diagram

Read downwards: input supplier → information to feed → responsibility → output → consumer. Arrows describe information passed by a caller. They are not automatic execution, permission or a package dependency. Each diagram has a text equivalent and an original SVG you can open, zoom or save. No animation is required to read it.

Reuse a component safely

  1. Pick the output your project needs; check the module's responsibility and boundary.
  2. Open its exact contract for typed fields, bounds, supported host and failure states. The human guide links its installed adoption instructions where an entry exists.
  3. Supply your own identities, storage, clock, permissions and collaborators as that contract requires. A source module does not automatically have an installed package entry.
  4. Keep the original command identity after a lost reply. Unknown, partial and Inconclusive results carry information; they cannot be treated as zero, failure or permission to retry.
  5. Check the independent adoption gate and current evidence before relying on the component in another project. Local component proof does not establish the complete Factory lifecycle.

Find one module

ModuleInformation flowPurpose and exact inputs
Research semanticsDiagramGuide · Contract
KnowledgeDiagramGuide · Contract
Factory workflowDiagramGuide · Contract
Implementation WorkflowDiagramGuide · Contract
Verification WorkflowDiagramGuide · Contract
CalendarDiagramGuide · Contract
Milestone objectivesDiagramGuide · Contract
Milestone research handoffDiagramGuide · Contract
Milestone work briefDiagramGuide · Contract
Research jobsDiagramGuide · Contract
Provider diagnosticsDiagramGuide · Contract
Provider event deliveryDiagramGuide · Contract
Command journalDiagramGuide · Contract
ExecutionDiagramGuide · Contract
Attempt fence / workspaceDiagramGuide · Contract
Local fixture workerDiagramGuide · Contract
Evidence / AssuranceDiagramGuide · Contract
Guarded verification / recoveryDiagramGuide · Contract
Confined executorDiagramGuide · Contract
Checkout GitDiagramGuide · Contract
DeliveryDiagramGuide · Contract
ProducersDiagramGuide · Contract
Repository sealing / export and integrationDiagramGuide · Contract
Repository collectorDiagramGuide · Contract
Repository AssuranceDiagramGuide · Contract
Product gate and delivery recordsDiagramGuide · Contract
PortfolioDiagramGuide · Contract
DashboardDiagramGuide · Contract
Project guidanceDiagramGuide · Contract
Required actions and blockersDiagramGuide · Contract
Branch healthDiagramGuide · Contract
Owner policyDiagramGuide · Contract
Owner digestDiagramGuide · Contract
Service accessDiagramGuide · Contract
Operational signalsDiagramGuide · Contract
Prevention registerDiagramGuide · Contract
Work itemsDiagramGuide · Contract
IntelligenceDiagramGuide · Contract
Lifecycle scheduleDiagramGuide · Contract
Discovery sourcesDiagramGuide · Contract
Temporal PlanningDiagramGuide · Contract
Capacity PlanningDiagramGuide · Contract
Material TimingDiagramGuide · Contract
Proposal ownershipDiagramGuide · Contract
Guidance acceptanceDiagramGuide · Contract
Provider eventsDiagramGuide · Contract
Provider subscriptionsDiagramGuide · Contract
Provider Events RPCDiagramGuide · Contract
Provider Guidance toolsDiagramGuide · Contract
Marketing WorkflowDiagramGuide · Contract

Keep the guide accurate

The diagrams and these pages are generated together from editorial data, using the shared design tokens. Adding a module guide without an information-flow entry fails the coverage check. Documentation ownership keeps API and acceptance facts in their existing authoritative records.

Source: docs/explanation/visual-understanding.md