Visual understanding · Workflow diagrams
These are information-flow diagrams, not import graphs. Arrows mean a caller passes or records information; they do not imply automatic dispatch. Contracts own exact field names and bounds; the build review owns current acceptance.
- 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
Factory workflow
Feed it: One bounded Product prefix with original Research, owner Guidance, Knowledge plan, Delivery, worker, integration and Marketing inputs. Supplier: Caller preparing explicit native stage requests and owners.
Use its result: Complete or stopped stage records with original identities and separate current support. Consumer: Caller preparing the next suffix or inspecting exact historical replay.
Boundary: Stateless bounded local candidate, with no new journal, allowance, retries or authority. Missing preparation stops; unknown effects block progression. No live provider, release or customer benefit is qualified.
Human guide · Exact contract · Open full-size diagram
Implementation workflow
Feed it: Original one-Attempt job, source and worker snapshots, pins, fixed Budget and shared Delivery paths. Supplier: Caller holding the original frozen Slice and native Product authority.
Use its result: Native sealed Candidate or refused, interrupted, waiting or unknown result. Consumer: Independent Verification Workflow or caller inspecting historical execution.
Boundary: Worker output is untrusted and cannot verify itself or permit integration. Original replay never launches again; unresolved host observations keep exposure reserved. No live Producer is qualified.
Human guide · Exact contract · Open full-size diagram
Verification workflow
Feed it: Original bound store, frozen Slice, exact Candidate, proof pins, real collectors and fixed check allowance. Supplier: Caller with an externally sealed native owned Repository Candidate.
Use its result: Verified, Failed or Inconclusive proof with separately recomputed current validity. Consumer: Delivery integration gate and read-only Assessment.
Boundary: A copied report or historical Verified result grants no current integration permission. Profiled unknown collection is never retried; no imported project, live provider or release is qualified.
Human guide · Exact contract · Open full-size diagram
Confined executor
Feed it: Pinned Node program, read-only snapshots, limits and cancellation. Supplier: Repository collector or caller.
Use its result: Process observations; refused or unresolved execution. Consumer: Repository collector or caller.
Boundary: No network, writable path or child processes. Hard RAM/disk limits and cleanup after observer loss are unproved.
Human guide · Exact contract · Open full-size diagram
Checkout git
Feed it: Canonical checkout, committed file path and inspected commit ID. Supplier: Delivery binding for a registered primary checkout.
Use its result: Committed text or a whole-read refusal. Consumer: Delivery binding copies selected source files.
Boundary: R7 source candidate awaiting acceptance. No working-tree bytes, hooks, filters or network fetch; linked worktrees and oversized or malformed input refuse.
Human guide · Exact contract · Open full-size diagram
Delivery
Feed it: Registered checkout, owned store, explicit grant, frozen Slice, authored proposal and fixed bounds. Supplier: Caller composing disposable synthetic Products.
Use its result: Original Candidate, proof and integration receipt with historical outcome and current validity. Consumer: Individual factory:delivery stages, ordered local run or prepared Factory workflow.
Boundary: Bounded public local candidate with independently reviewed stage/concert evidence. Unknown integration blocks new work; no live model, release or customer benefit is qualified. Current combined gates belong to the build review.
Human guide · Exact contract · Open full-size diagram
Producers
Feed it: Pinned brief, snapshots, model request, limits and transport. Supplier: Caller with admitted work.
Use its result: Untrusted Proposal, usage or unknown outcome. Consumer: Caller that validates and seals with Repository.
Boundary: Live model transports remain unavailable or unqualified. A Proposal grants neither authority nor a pass.
Human guide · Exact contract · Open full-size diagram
Repository sealing / export and integration
Feed it: Proposed text edits, base commit, frozen inputs and Action identity. Supplier: Caller with proposed edits.
Use its result: Sealed Candidate, snapshots and integration observation. Consumer: Collector, Assurance and delivery controller.
Boundary: Fresh Factory-owned local repositories only. Unknown integration never permits a blind retry; Git and SQLite are separate.
Human guide · Exact contract · Open full-size diagram
Repository collector
Feed it: Sealed Candidate, base, checks, fixture snapshots, fence and current gate reads. Supplier: Native Delivery or caller with a frozen Slice.
Use its result: Complete check Evidence and collection outcomes. Consumer: Repository Assurance through native Delivery or external Verification.
Boundary: Checks each side against its pinned input. Issues no Verdict and runs no Git operation; native Delivery owns current admission, complete reference retention and recovery.
Human guide · Exact contract · Open full-size diagram
Repository assurance
Feed it: Sealed manifests, Slice checks, exact pins and all stored Evidence. Supplier: Caller assembling stored proof.
Use its result: Repository Verdict and proof details. Consumer: Product gate and delivery records.
Boundary: Pure judgement starts no work. Model review is reserved and Inconclusive; writable trusted storage is not cryptographic proof.
Human guide · Exact contract · Open full-size diagram
Product gate and delivery records
Feed it: Product/store binding, grant, frozen Slice, allowance and proof. Supplier: Authorised delivery controller.
Use its result: Admission, delivery records, Receipt and derived Assessment. Consumer: Caller performing local integration.
Boundary: The gate owns permission; Repository performs the effect. Native local Delivery is composed; unknown integration blocks later moves. Complete live, release and customer delivery remain open.
