Factory docs, home
Page navigation

See the input → responsibility → output diagram.

What it does for you: It keeps one card per project: a register of your local projects, each tied to one verified Git checkout, so renaming a branch or a project never confuses which is which. It then shows what sources have reported, such as activity, checks, blockers and model usage. When a number is only partial or unknown, it says so and gives the reason, instead of a false zero.

A teal bob with spectacles and tabbed index cards.

Meet the organiser. Every fact has a place. Registers projects and collects what their sources report. Meet the whole Plumb family.

How it links: It takes durable storage from Command journal, facts and usage receipts from explicit imports, and repository checks from the Dashboard. It gives read-only views to Dashboard, current blockers and source trouble to Required actions and blockers, and the project list to Project guidance.

Honest limits:

  • It knows only what it inspects or is given: Git metadata from registered local checkouts, and imported facts. It collects nothing from GitHub, releases, billing or customers. Registering a project grants no right to change, release or spend.
  • A count is exact only when a source declares complete coverage. Cost is the provider's estimate for recorded sessions, not a bill.

Status: Accepted for local metadata registration and sourced facts. Acceptance and evidence.

Contract and limits

The private adoption draft lets another local application supply its own journal, Git checkouts, facts and query windows. It keeps the same identity checks and honest Counts. Independent review passed; the draft was merged on 1 October 2026 after an Opus 5.5 review and accepted locally the same day by the owner-designated acceptance reviewer after a Fable 5.1 review.

Shared value implementation: common contracts. Owning errors, limits, stored identities and authority remain as specified above.

Source: docs/guide/portfolio.md