Use the local dashboard to inspect recorded project progress, actions and usage. It does not run product delivery.
Build the browser package with npm --prefix apps/dashboard run build, then start node src/dashboard-server.ts --journal <local Portfolio journal> --port 4317. Use an existing journal; do not recreate it. Check that the port is free first. Restart your server after rebuilding because it loads assets at startup. Open http://127.0.0.1:4317.
Confirm that the Portfolio loads and that each displayed figure names its source or explains why it is unknown. Open a project to see its evidence, repository state and values.
Modules
See the modules contract.
Protocol
See the protocol contract.
Where decisions live
See the where decisions live contract.
Current sources
See the current sources contract.
API
See the api contract.
Attention
Use the central Actions list to open the source report and next action. Required actions reference defines how the list is derived.
Blocker resolution guide
/projects/:id/blockers/:blockerId shows:
- the prerequisite, affected work, who can act and why remedies cannot progress;
- the steps to resolve, from the source's optional details or its
nextAction; - the remedies tried and their evidence;
- the report history.
Evidence is text; it is never opened or fetched. Three outcomes are kept apart:
- Reload facts reads recorded facts again and says so. It tests nothing.
- Recheck is
unsupported: no trusted collector checks blocker prerequisites. The repository check checks availability only and never resolves a blocker. - Resolved is only a source recording it. That shows as
reported, orreported-with-evidencewhen the source cites evidence; neither is presented as verified.
Presentation rules
- Overview. Each row shows the project, its stated focus, verified runs with their current validity, and repository availability with check time. Branch and revision are on the project page.
- Current focus. Lists stated focus and open blockers; a blocker row opens its resolution guide. No source ranks next work yet, so the list is not presented as an ordered queue.
- Actions. A central list across projects, with concise counts, required actions separated from notices, and a link from each item to its guide or project. Reload is labelled read-only.
- Core values. The project page shows the current values, revision and provenance. The editor can add, reword, reorder, retire and restore values. Its behaviour:
- Feedback is per field and concise.
- A conflict keeps the losing draft and shows both sides. Choosing to keep the draft is explicit; it is never silently rebased.
- A failed or uncertain save keeps its operation ID, so a retry cannot record twice.
- Connections to finish. Each incomplete source shows its name, a short state and a caption that acknowledges imported facts. Reasons and capability are in a details disclosure. No control implies that a source can be connected from the browser.
- Usage. Invocations are allocated by date. Undated invocations and cumulative sessions are shown separately and never assigned to a period. Costs are provider-reported estimates: not billing, and not spending in a period.
- Brand. The Factory mark sits beside the wordmark. Plumb appears only in the empty Portfolio, below the factual message, when that read succeeded and reports nothing needing attention. Both are decorative, byte-identical copies of the reviewed files in
apps/dashboard/public/brand, served from the static manifest. Sources and hashes: design system.
Tests
See the tests contract.
Confirmed transient journal contention now supplies Retry-After: 1 on GET/HEAD only. Missing, unsupported, corrupt or unreadable stores retain their safe responses without transient retry advice. Commands keep original-ID recovery and receive no read retry hint. The narrow Source correction and its exact 210-entry installed package passed independent review; the correction record retains their evidence. Broader integration checks remain separate.
