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
-
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 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
- Pick the output your project needs; check the module's responsibility and boundary.
- 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.
- Supply your own identities, storage, clock, permissions and collaborators as that contract requires. A source module does not automatically have an installed package entry.
- 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.
- 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
| Module | Information flow | Purpose and exact inputs |
|---|---|---|
| Research semantics | Diagram | Guide · Contract |
| Knowledge | Diagram | Guide · Contract |
| Factory workflow | Diagram | Guide · Contract |
| Implementation Workflow | Diagram | Guide · Contract |
| Verification Workflow | Diagram | Guide · Contract |
| Calendar | Diagram | Guide · Contract |
| Milestone objectives | Diagram | Guide · Contract |
| Milestone research handoff | Diagram | Guide · Contract |
| Milestone work brief | Diagram | Guide · Contract |
| Research jobs | Diagram | Guide · Contract |
| Provider diagnostics | Diagram | Guide · Contract |
| Provider event delivery | Diagram | Guide · Contract |
| Command journal | Diagram | Guide · Contract |
| Execution | Diagram | Guide · Contract |
| Attempt fence / workspace | Diagram | Guide · Contract |
| Local fixture worker | Diagram | Guide · Contract |
| Evidence / Assurance | Diagram | Guide · Contract |
| Guarded verification / recovery | Diagram | Guide · Contract |
| Confined executor | Diagram | Guide · Contract |
| Checkout Git | Diagram | Guide · Contract |
| Delivery | Diagram | Guide · Contract |
| Producers | Diagram | Guide · Contract |
| Repository sealing / export and integration | Diagram | Guide · Contract |
| Repository collector | Diagram | Guide · Contract |
| Repository Assurance | Diagram | Guide · Contract |
| Product gate and delivery records | Diagram | Guide · Contract |
| Portfolio | Diagram | Guide · Contract |
| Dashboard | Diagram | Guide · Contract |
| Project guidance | Diagram | Guide · Contract |
| Required actions and blockers | Diagram | Guide · Contract |
| Branch health | Diagram | Guide · Contract |
| Owner policy | Diagram | Guide · Contract |
| Owner digest | Diagram | Guide · Contract |
| Service access | Diagram | Guide · Contract |
| Operational signals | Diagram | Guide · Contract |
| Prevention register | Diagram | Guide · Contract |
| Work items | Diagram | Guide · Contract |
| Intelligence | Diagram | Guide · Contract |
| Lifecycle schedule | Diagram | Guide · Contract |
| Discovery sources | Diagram | Guide · Contract |
| Temporal Planning | Diagram | Guide · Contract |
| Capacity Planning | Diagram | Guide · Contract |
| Material Timing | Diagram | Guide · Contract |
| Proposal ownership | Diagram | Guide · Contract |
| Guidance acceptance | Diagram | Guide · Contract |
| Provider events | Diagram | Guide · Contract |
| Provider subscriptions | Diagram | Guide · Contract |
| Provider Events RPC | Diagram | Guide · Contract |
| Provider Guidance tools | Diagram | Guide · Contract |
| Marketing Workflow | Diagram | Guide · 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.
