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
- Dashboard
- Project guidance
- Required actions and blockers
- Branch health
- Owner policy
- Owner digest
- Service access
- Operational signals
- Prevention register
- Work items
Portfolio
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
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
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
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
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
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
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
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
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
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
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.
