Factory docs, home
Page navigation

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.

Module studies, plate 2: five Plumb studies for the isolation, delivery and visibility modules, each labelled with its module's name.

Plate 2, position 4, Plumb the registrar: an index-card drawer with blank tabs. The plate is shown whole.

How it links: Takes durable storage from Command journal, facts and usage receipts from explicit imports, and repository checks from the Dashboard · 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 (local review, 28 September 2026). Six local projects are registered for metadata only. This is not a release or customer benefit, and the epics it serves remain open.

Agent reference →

Source: docs/guide/portfolio.md