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. Working local composition.
- Implement and verify a repository change. Bounded native stages and local concert candidate; complete live delivery open.
- Research a commissioned question. Native collection and separately commissioned semantic candidate; live autonomous Research open.
- Draft fact-supported marketing. Bounded public local drafting candidate; complete publishing Workflow open.
- Read health and form an owner update. Local reporting components; no automatic polling or delivery.
- Offer and apply original Guidance. Locally proved components; no qualified live tool host.
- Project events, verify subscriptions and own bounded notification transport. Native sender source candidate; installed behavioural and live delivery gates open.
- Evaluate a plan before proposing work. Pure evaluators and ownership kernel; complete planner planned.
- Investigate and repair an operational Signal. Intake exists; complete Repair Workflow planned.
- Discover service access prerequisites. Mapping and bounded listing components; complete operations Workflow planned.
- Choose one work lane and inspect leftovers. Work ownership and read-only lane reporting.
- Follow the complete value lifecycle. Target architecture; complete live Factory lifecycle unproved.
Verify and recover a fixture
Scope: Working local composition.
Start with: Supply a built-in fixture, Run ID, state directory and fixed Budget.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
