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 · 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.

Portfolio

Input supplier: Registration and trusted imports. Input: Product identity, verified checkout and attributed observations. Portfolio: Keep sourced facts and derive counts with their coverage. Output: Product views, facts, usage and exact/partial/unknown counts. Consumer: Dashboard, Attention and Factory adapters. Boundary: Metadata inspection supplies no delivery authority. A reported release or blocker resolution is not verified customer value.

Feed it: Product identity, verified checkout and attributed observations. Supplier: Registration and trusted imports.

Use its result: Product views, facts, usage and exact/partial/unknown counts. Consumer: Dashboard, Attention and Factory adapters.

Boundary: Metadata inspection supplies no delivery authority. A reported release or blocker resolution is not verified customer value.

Human guide · Exact contract · Open full-size diagram

Dashboard

Input supplier: Caller-owned reads and commands. Input: Portfolio, Attention, Guidance, Digest and configured milestone views. Dashboard: Serve a guarded local browser interface. Output: Rendered views; guarded Portfolio and configured milestone requests. Consumer: Person using the loopback interface. Boundary: Reads start no checks. Milestone commands need a configured qualified owner; closing a page cannot settle an uncertain effect.

Feed it: Portfolio, Attention, Guidance, Digest and configured milestone views. Supplier: Caller-owned reads and commands.

Use its result: Rendered views; guarded Portfolio and configured milestone requests. Consumer: Person using the loopback interface.

Boundary: Reads start no checks. Milestone commands need a configured qualified owner; closing a page cannot settle an uncertain effect.

Human guide · Exact contract · Open full-size diagram

Project guidance

Input supplier: Explicit Product owner under an exact current GuidanceEditFence. Input: Original owner request, expected revision, up to eight ordered values and bounded rationale. Project guidance: Preserve old pins; prospectively cut over one Product to atomic values and rationale. Output: Immutable Guidance revision and pin, or attributed append-only rationale supplement. Consumer: Dashboard, Knowledge, milestone planning and read/inspect/replay-only migrated adapters. Boundary: Values and rationale grant no Delivery authority. Legacy pins remain unchanged and have no original rationale; recollection is a dated supplement. No live migration or automatic owner decision is qualified.

Feed it: Original owner request, expected revision, up to eight ordered values and bounded rationale. Supplier: Explicit Product owner under an exact current GuidanceEditFence.

Use its result: Immutable Guidance revision and pin, or attributed append-only rationale supplement. Consumer: Dashboard, Knowledge, milestone planning and read/inspect/replay-only migrated adapters.

Boundary: Values and rationale grant no Delivery authority. Legacy pins remain unchanged and have no original rationale; recollection is a dated supplement. No live migration or automatic owner decision is qualified.

Human guide · Exact contract · Open full-size diagram

Required actions and blockers

Input supplier: Sourced conditions; Factory Portfolio. Input: Reported blockers, repository states and source coverage. Required actions and blockers: Project reported required actions and resolution guides. Output: Actions list, owner-required items and quieter notices. Consumer: Dashboard and caller. Boundary: Missing data creates no invented action. Owner-required needs a source naming the owner and its reason.

Feed it: Reported blockers, repository states and source coverage. Supplier: Sourced conditions; Factory Portfolio.

Use its result: Actions list, owner-required items and quieter notices. Consumer: Dashboard and caller.

Boundary: Missing data creates no invented action. Owner-required needs a source naming the owner and its reason.

Human guide · Exact contract · Open full-size diagram

Branch health

Input supplier: Caller-owned GitHub reader. Input: Exact branch head, checks, workflow runs and coverage. Branch health: Record health and failure episodes; optionally mirror blockers. Output: Red, green or unknown health and episode history. Consumer: Portfolio, Owner digest and event projector. Boundary: No commissioned live polling. Green requires exact-head evidence; an episode is an observation, not a diagnosed cause.

Feed it: Exact branch head, checks, workflow runs and coverage. Supplier: Caller-owned GitHub reader.

Use its result: Red, green or unknown health and episode history. Consumer: Portfolio, Owner digest and event projector.

Boundary: No commissioned live polling. Green requires exact-head evidence; an episode is an observation, not a diagnosed cause.

Human guide · Exact contract · Open full-size diagram

Owner policy

Input supplier: Owner or reporting channel. Input: Asks, answers, stated minutes, coverage and confirmed rule drafts. Owner policy: Keep ask history and evaluate bounded confirmed rules. Output: Weekly counts, open asks and ask/ruled/unknown decision. Consumer: Local ledger/digest commands and future callers. Boundary: Rules exclude pushes, payments, accounts and terms. No Factory operation consults them yet; recording an answer grants no authority.

Feed it: Asks, answers, stated minutes, coverage and confirmed rule drafts. Supplier: Owner or reporting channel.

Use its result: Weekly counts, open asks and ask/ruled/unknown decision. Consumer: Local ledger/digest commands and future callers.

Boundary: Rules exclude pushes, payments, accounts and terms. No Factory operation consults them yet; recording an answer grants no authority.

Human guide · Exact contract · Open full-size diagram

Owner digest

Input supplier: Attributed caller reads. Input: Product registry, health history, owner-required coverage and clock. Owner digest: Form cited exception batches and bounded weekly updates. Output: Recorded digest, batches and their coverage gaps. Consumer: Dashboard and local digest command. Boundary: Sends nothing and starts no schedule. Stale health stays historical; incomplete coverage cannot mean nothing needs attention.

Feed it: Product registry, health history, owner-required coverage and clock. Supplier: Attributed caller reads.

Use its result: Recorded digest, batches and their coverage gaps. Consumer: Dashboard and local digest command.

Boundary: Sends nothing and starts no schedule. Stale health stays historical; incomplete coverage cannot mean nothing needs attention.

Human guide · Exact contract · Open full-size diagram

Service access

Input supplier: Names-only caller scans and listings. Input: Product bindings, service catalogue and credential locations. Service access: Map services and references; assess a required access route. Output: Service map, findings and ready/missing/unknown/refused route. Consumer: Caller deciding whether prerequisites are met. Boundary: References never carry secret values. Vault item presence does not prove usable fields; no credential grants or live service operations.

Feed it: Product bindings, service catalogue and credential locations. Supplier: Names-only caller scans and listings.

Use its result: Service map, findings and ready/missing/unknown/refused route. Consumer: Caller deciding whether prerequisites are met.

Boundary: References never carry secret values. Vault item presence does not prove usable fields; no credential grants or live service operations.

Human guide · Exact contract · Open full-size diagram

Operational signals

Input supplier: Authenticated, authorised caller. Input: Redacted observations, source identity, collection progress and clock. Operational signals: Record unassessed Signals and progress with durable identities. Output: Signals, replay results and honest coverage. Consumer: Future investigation or Repair caller. Boundary: Caller owns authentication and redaction. No live provider or Repair Workflow; immutable storage cannot promise timed erasure.

Feed it: Redacted observations, source identity, collection progress and clock. Supplier: Authenticated, authorised caller.

Use its result: Signals, replay results and honest coverage. Consumer: Future investigation or Repair caller.

Boundary: Caller owns authentication and redaction. No live provider or Repair Workflow; immutable storage cannot promise timed erasure.

Human guide · Exact contract · Open full-size diagram

Prevention register

Input supplier: Caller-supplied repository reads. Input: Guardrail templates, recorded causes, visibility and exemptions. Prevention register: Evaluate prevention presence; retain results and exemptions. Output: Present, absent, exempted, not-applicable or unknown facts. Consumer: Caller reviewing prevention coverage. Boundary: Implementation awaiting acceptance; no package entry, live read or rollout. Presence is not proof a cause is repaired.

Feed it: Guardrail templates, recorded causes, visibility and exemptions. Supplier: Caller-supplied repository reads.

Use its result: Present, absent, exempted, not-applicable or unknown facts. Consumer: Caller reviewing prevention coverage.

Boundary: Implementation awaiting acceptance; no package entry, live read or rollout. Presence is not proof a cause is repaired.

Human guide · Exact contract · Open full-size diagram

Work items

Input supplier: Coordinator and read-only Git lane reader. Input: Task keys, files, holder, branch, worktree and lane facts. Work items: Record claims, refuse duplicate work and classify old lanes. Output: Work ownership, conflicts and proposed lane actions. Consumer: Coordinator choosing work or reviewing cleanup. Boundary: Implementation awaiting acceptance; no live register or package entry. Records work ownership, not delivery authority. Deletes nothing; unreadable lanes stay unknown.

Feed it: Task keys, files, holder, branch, worktree and lane facts. Supplier: Coordinator and read-only Git lane reader.

Use its result: Work ownership, conflicts and proposed lane actions. Consumer: Coordinator choosing work or reviewing cleanup.

Boundary: Implementation awaiting acceptance; no live register or package entry. Records work ownership, not delivery authority. Deletes nothing; unreadable lanes stay unknown.

Human guide · Exact contract · Open full-size diagram

Source: docs/explanation/visual-operations.md