PM Hub

The spec says what should exist. The PM Hub shows what actually does. It’s a read-only view over everything the CLI writes back while your agent builds, reachable from the project’s navigation rail.

What you see

• The functionality board. Every functionality with its real status: todo, in_progress, code-complete, or done, straight from the ledger transitions your CLI reports.
• Verification badges. A functionality shows a verified checkmark only when a verifier actually ran and checked it against its acceptance criteria. Work that was marked done without verification shows as untested, honestly, rather than pretending.
• Deviations. Places where the implementation intentionally departs from the spec, each with its own lifecycle (accepted, resolved, deferred, or reopened) so nothing gets quietly forgotten.
• Field notes and reports. The narrative of the build: what happened during each chunk of work, in the words the agent recorded at the time.

Why it’s read-only

The PM Hub is a lens, not a control panel. Statuses come from the CLI because that’s where the truth is, in the repo, next to the code. If the board disagrees with reality, the fix is in the build loop (run cubedot push to flush pending write-backs), not in the UI.

Who it’s for

Anyone who’d otherwise ask “how’s it going?” A PM, a founder, or you tomorrow morning can open the PM Hub and see progress, verification coverage, and open deviations without touching the repo.