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.

Visual understanding

Choose a complete job, then check which steps your application must supply. These diagrams show responsibility order, not a promise that Factory dispatches each step. Proposed steps have no complete working Workflow; other steps may be separately implemented without a controller joining them. Scope statements below are part of each diagram's meaning.

Verify and recover a fixture

Scope: Working local composition.

Start with: Supply a built-in fixture, Run ID, state directory and fixed Budget.

Working local composition. Start with: Supply a built-in fixture, Run ID, state directory and fixed Budget. CLI freezes fixture and resource pins → Execution records Run and owner → Fence / workspace protects Attempt → Fixture worker stores observations → Assurance judges stored Evidence → Controller settles or recovers Attempt. Historical fixture Verdict plus separately recomputed current validity. Boundary: Recovery waits on held ownership, settles a valid report or fences an orphan. Cancellation is recorded before stopping work; exhausted or unresolved work cannot become a pass.

Result: Historical fixture Verdict plus separately recomputed current validity.

Boundary: Recovery waits on held ownership, settles a valid report or fences an orphan. Cancellation is recorded before stopping work; exhausted or unresolved work cannot become a pass.

Start here · Contract / detail 2 · Open full-size diagram

Implement and verify a repository change

Scope: Bounded native stages and local concert candidate; complete live delivery open.

Start with: Supply frozen Need/Slice, original base, owned store, explicit current authority, independent checks and fixed Budget.

Bounded native stages and local concert candidate; complete live delivery open. Start with: Supply frozen Need/Slice, original base, owned store, explicit current authority, independent checks and fixed Budget. Caller freezes Slice and grant → Original confined worker proposes untrusted edits → Repository seals exact Candidate → Independent collector runs base and Candidate checks → Repository Assurance derives Verdict → Gate rechecks proof and current authority → Repository records guarded original local move → Delivery derives read-only Assessment. Candidate, repository Verdict, sender receipt, current validity and derived Assessment remain separate results. Boundary: Individual stages, the Delivery ordered CLI and prepared Factory workflow reuse native owners; no new allowance or retry owner is created. Refused proof prevents integration; unknown original D5 is reconciled before progression. Local receipt establishes neither release nor customer benefit.

Result: Candidate, repository Verdict, sender receipt, current validity and derived Assessment remain separate results.

Boundary: Individual stages, the Delivery ordered CLI and prepared Factory workflow reuse native owners; no new allowance or retry owner is created. Refused proof prevents integration; unknown original D5 is reconciled before progression. Local receipt establishes neither release nor customer benefit.

Start here · Contract / detail 2 · Contract / detail 3 · Contract / detail 4 · Open full-size diagram

Research a commissioned question

Scope: Native collection and separately commissioned semantic candidate; live autonomous Research open.

Start with: Supply approved source addresses, original question/scope, qualified transport/cache and fixed allowance; semantic work needs its own original commission and native quote pins.

Native collection and separately commissioned semantic candidate; live autonomous Research open. Start with: Supply approved source addresses, original question/scope, qualified transport/cache and fixed allowance; semantic work needs its own original commission and native quote pins. Caller commissions original source collection → Optional Schedule admits occurrence → Discovery reads allowed sources → Native collections retain novelty and coverage → Injected triager proposes sourced Signals → Native quotes constrain injected synthesis → Explicit caller shadow policy evaluates proposal. Retained captures, citations and semantic Signals/synthesis, with parked or explicitly policy-evaluated shadow; no work admission. Boundary: Collection itself makes zero model calls. Semantic ports supply no authority; unverifiable quotes cannot support findings. Unknown contacts keep their full shared reservation and are never repeated. No live source/provider or nightly schedule is commissioned.

Result: Retained captures, citations and semantic Signals/synthesis, with parked or explicitly policy-evaluated shadow; no work admission.

Boundary: Collection itself makes zero model calls. Semantic ports supply no authority; unverifiable quotes cannot support findings. Unknown contacts keep their full shared reservation and are never repeated. No live source/provider or nightly schedule is commissioned.

Start here · Contract / detail 2 · Contract / detail 3 · Open full-size diagram

Draft fact-supported marketing

Scope: Bounded public local drafting candidate; complete publishing Workflow open.

Start with: Supply typed current facts, audience/channel brief, fact-age policy and asOf; optional injected drafter gets original fixed bounds.

Bounded public local drafting candidate; complete publishing Workflow open. Start with: Supply typed current facts, audience/channel brief, fact-age policy and asOf; optional injected drafter gets original fixed bounds. Caller supplies facts and brief → Pure rules screen wording and fact pins → Original job records drafting reservation → Drafting port proposes placeholders → Same rules check proposed wording → Pack retains citations and refusals → Later reads revalidate current facts. Draft pack with block-by-block fact trace and refusal reasons; original historical text stays unchanged. Boundary: Unknown drafting calls consume their bound and are never repeated. Availability needs release/probe evidence; benefit needs supported outcome evidence. Publication, channel authority and live observations remain separate open gates.

Result: Draft pack with block-by-block fact trace and refusal reasons; original historical text stays unchanged.

Boundary: Unknown drafting calls consume their bound and are never repeated. Availability needs release/probe evidence; benefit needs supported outcome evidence. Publication, channel authority and live observations remain separate open gates.

Start here · Contract / detail 2 · Open full-size diagram

Read health and form an owner update

Scope: Local reporting components; no automatic polling or delivery.

Start with: Supply a commissioned reader, exact branch checks, workflow history, Product registry and reporting clock.

Local reporting components; no automatic polling or delivery. Start with: Supply a commissioned reader, exact branch checks, workflow history, Product registry and reporting clock. Branch health reads scoped GitHub facts → Journal keeps health and episodes → Portfolio receives optional blockers → Attention projects reported actions → Owner digest forms cited update → Dashboard presents recorded views. Attributed health, reported blockers and a cited digest with explicit coverage. Boundary: These arrows describe available caller wiring. No commissioned live poll, scheduler or sender is running. Failed source reads keep coverage unknown; reload cannot verify a blocker resolution.

Result: Attributed health, reported blockers and a cited digest with explicit coverage.

Boundary: These arrows describe available caller wiring. No commissioned live poll, scheduler or sender is running. Failed source reads keep coverage unknown; reload cannot verify a blocker resolution.

Start here · Contract / detail 2 · Contract / detail 3 · Open full-size diagram

Offer and apply original Guidance

Scope: Locally proved components; no qualified live tool host.

Start with: Supply exact original proposal/command identity, registry, current permission and a qualified shared physical fence.

Locally proved components; no qualified live tool host. Start with: Supply exact original proposal/command identity, registry, current permission and a qualified shared physical fence. Caller proposes immutable generation → First offer fixes ownership forever → Tool host carries original identity → Receiver checks current authority → Project guidance commits once → Inspect reconciles original history. An actual Guidance revision or a refusal/unknown outcome attached to the same original command. Boundary: A transport acknowledgement is not domain acceptance. Lost replies never permit replacement or a new command; the original history must be reconciled. Read and write permission are checked separately.

Result: An actual Guidance revision or a refusal/unknown outcome attached to the same original command.

Boundary: A transport acknowledgement is not domain acceptance. Lost replies never permit replacement or a new command; the original history must be reconciled. Read and write permission are checked separately.

Start here · Contract / detail 2 · Contract / detail 3 · Open full-size diagram

Project events, verify subscriptions and own bounded notification transport

Scope: Native sender source candidate; installed behavioural and live delivery gates open.

Start with: Supply committed source facts, authenticated identities, exact current permission, private storage, physical exclusion and bounded connector.

Native sender source candidate; installed behavioural and live delivery gates open. Start with: Supply committed source facts, authenticated identities, exact current permission, private storage, physical exclusion and bounded connector. Branch health commits source event → Event projector validates source pin → Subscription host verifies signed callback challenge → Native notification aggregate fixes first occurrence → Sender reserves before any native contact → Current authority recheck admits bounded transport → Original attempt retains receipt or uncertainty. Projected event, subscription receipt and sender transport outcome remain distinct; domain effect is unobserved. Boundary: The host owns authenticity, private URL/key handling, physical authority fence and original occurrence. Unknown or lost-ack contact never permits another send; bounded definite-response retries keep the same body and lifetime ceiling. Controlled TLS proof qualifies neither public DNS nor customer delivery.

Result: Projected event, subscription receipt and sender transport outcome remain distinct; domain effect is unobserved.

Boundary: The host owns authenticity, private URL/key handling, physical authority fence and original occurrence. Unknown or lost-ack contact never permits another send; bounded definite-response retries keep the same body and lifetime ceiling. Controlled TLS proof qualifies neither public DNS nor customer delivery.

Start here · Contract / detail 2 · Contract / detail 3 · Contract / detail 4 · Open full-size diagram

Evaluate a plan before proposing work

Scope: Pure evaluators and ownership kernel; complete planner planned.

Start with: Supply attributed dates, dependency evidence, native-unit quota observations, material facts and explicit scenarios.

Pure evaluators and ownership kernel; complete planner planned. Start with: Supply attributed dates, dependency evidence, native-unit quota observations, material facts and explicit scenarios. Temporal evaluates date constraints → Capacity evaluates conditional ranges → Material Timing evaluates eligible slots → Caller interprets conflicts and unknowns → Caller may record pinned proposal → Future dispatcher needs separate authority. Inspectible constraints, deficits, unknowns and possibly a retained proposal; no automatic Commitment. Boundary: The first three evaluators are separate inputs to caller planning, not an automatic pipeline. Intelligence selection qualifies no provider. No forecast reserves quota, dispatches work or approves publication.

Result: Inspectible constraints, deficits, unknowns and possibly a retained proposal; no automatic Commitment.

Boundary: The first three evaluators are separate inputs to caller planning, not an automatic pipeline. Intelligence selection qualifies no provider. No forecast reserves quota, dispatches work or approves publication.

Start here · Contract / detail 2 · Contract / detail 3 · Contract / detail 4 · Open full-size diagram

Investigate and repair an operational Signal

Scope: Intake exists; complete Repair Workflow planned.

Start with: Supply caller-authenticated redacted observations, collection identity, current permission and authorised production evidence.

Intake exists; complete Repair Workflow planned. Start with: Supply caller-authenticated redacted observations, collection identity, current permission and authorised production evidence. Caller authenticates and redacts source → Signal intake records observation and progress → Proposed investigation establishes cause → Proposed repair uses Implementation → Proposed independent Verification → Proposed release and recovery → Proposed observation checks outcome. Today: unassessed Signals and honest historical coverage. Repair and measured recovery remain proposed. Boundary: A Signal proves neither cause nor customer impact. Restoring production requires separate live authority and evidence; this design supplies no production connector or writeback.

Result: Today: unassessed Signals and honest historical coverage. Repair and measured recovery remain proposed.

Boundary: A Signal proves neither cause nor customer impact. Restoring production requires separate live authority and evidence; this design supplies no production connector or writeback.

Start here · Contract / detail 2 · Open full-size diagram

Discover service access prerequisites

Scope: Mapping and bounded listing components; complete operations Workflow planned.

Start with: Supply Product bindings, names-only repository scans, catalogue and authorised listing ports; keep secrets outside records.

Mapping and bounded listing components; complete operations Workflow planned. Start with: Supply Product bindings, names-only repository scans, catalogue and authorised listing ports; keep secrets outside records. Caller supplies names-only observations → Service map binds references to Product → Need names environment and purpose → Access evaluates permitted routes → Proposed owner setup fills missing access → Proposed verification checks real use. A service map and ready/missing/unknown/refused prerequisite answer. Boundary: A complete recent listing can establish absence; partial lists cannot. An existing vault item does not prove usable fields. Mapping never registers accounts, reveals credentials or grants delivery permission.

Result: A service map and ready/missing/unknown/refused prerequisite answer.

Boundary: A complete recent listing can establish absence; partial lists cannot. An existing vault item does not prove usable fields. Mapping never registers accounts, reveals credentials or grants delivery permission.

Start here · Contract / detail 2 · Open full-size diagram

Choose one work lane and inspect leftovers

Scope: Work ownership and read-only lane reporting.

Start with: Supply project-scoped task keys, intended files, holder and read-only branch/worktree facts.

Work ownership and read-only lane reporting. Start with: Supply project-scoped task keys, intended files, holder and read-only branch/worktree facts. Coordinator proposes a work item → Register checks duplicate claims → Holder records branch and worktree → Coordinator updates item disposition → Lane reader reports merged or stale work → Person reviews proposed cleanup. Recorded work ownership or conflict; cited lane findings and proposed actions. Boundary: A lane that cannot be read stays unknown. Dirty work must be preserved before removal. The register neither deletes lanes nor authorises delivery.

Result: Recorded work ownership or conflict; cited lane findings and proposed actions.

Boundary: A lane that cannot be read stays unknown. Dirty work must be preserved before removal. The register neither deletes lanes nor authorises delivery.

Start here · Contract / detail 2 · Open full-size diagram

Follow the complete value lifecycle

Scope: Target architecture; complete live Factory lifecycle unproved.

Start with: Start with a sourced Need and explicit Product objective, acceptance, current authority and outcome measurement plan.

Target architecture; complete live Factory lifecycle unproved. Start with: Start with a sourced Need and explicit Product objective, acceptance, current authority and outcome measurement plan. Need states a customer problem → Owner prepares Guidance and selected plan → Slice freezes bounded acceptance → Candidate holds proposed exact bytes → Verdict judges independent technical proof → Receipt records original authorised action → Assessment checks attributed observations → Reviewed Knowledge preserves evidence and loss. The bounded local concert joins prepared native stages; a supported customer outcome still requires its own observation. Boundary: Native Research semantics, Guidance, Knowledge and local Delivery are available as bounded candidates. Live release/recovery, customer outcome validation and simplification/retirement remain open Workflows with separate authority and independent proof. Historical local success cannot qualify them.

Result: The bounded local concert joins prepared native stages; a supported customer outcome still requires its own observation.

Boundary: Native Research semantics, Guidance, Knowledge and local Delivery are available as bounded candidates. Live release/recovery, customer outcome validation and simplification/retirement remain open Workflows with separate authority and independent proof. Historical local success cannot qualify them.

Start here · Contract / detail 2 · Contract / detail 3 · Contract / detail 4 · Open full-size diagram

Source: docs/explanation/visual-workflows.md