Case Study

Yes — prismctl is exactly what we need, and it supersedes most of INIT-001 from the master plan. Here's the verdict:

What prism-control gives us

It's a Product Delivery Control Plane: canonical Dolt-backed store for cross-repo initiatives, per-repo RMIs, lease-based work claims, and delivery evidence — headless, library-first, with CLI and MCP surfaces sharing one service layer. It's already proven: INIT-PRISMCONTROL-001 and INIT-UIFORGE-001 are both tracked to delivery_complete, and all 11 repos from our master plan are already registered (market-spec, omnisignal, signal-spec, omniskill, aha-studio, prism, prism-roadmap, productcontext, productbuildershq-context, aha-go, prism-control).

How it answers our open questions

┌──────────────────────────────────────┬───────────────────────────────────────────────────────────────────────────────────────┐ │ Our INIT-001 plan │ prism-control's answer │ ├──────────────────────────────────────┼───────────────────────────────────────────────────────────────────────────────────────┤ │ Initiative type in prism-roadmap │ Already exists in the DB — prismctl initiative │ ├──────────────────────────────────────┼───────────────────────────────────────────────────────────────────────────────────────┤ │ ROADMAP.json as deterministic source │ Better: the Dolt DB is the source of truth; prismctl roadmap import/generate/diff │ │ of truth │ syncs ROADMAP.md both ways, and work ready auto-warns on drift. No ROADMAP.json │ │ │ needed │ ├──────────────────────────────────────┼───────────────────────────────────────────────────────────────────────────────────────┤ │ trace/check command for cross-repo │ prismctl roadmap diff, prismctl validate, and prismctl ingest (scans commits for │ │ drift │ Refs: RMI-... trailers as evidence) │ ├──────────────────────────────────────┼───────────────────────────────────────────────────────────────────────────────────────┤ │ initiatives/ JSON files in │ Superseded by the DB; the master plan doc stays as narrative │ │ productbuildershq-context │ │ └──────────────────────────────────────┴───────────────────────────────────────────────────────────────────────────────────────┘

Proposed adoption steps

  1. Rewrite INIT-001 in the master plan as "adopt prism-control" — now just: import roadmaps, add CLAUDE.md pointers to each repo.
  2. Create our initiatives in prismctl following its naming (INIT--001): e.g. INIT-MARKETSPEC-001, INIT-SIGNALLAYER-001, INIT-AHASTUDIO-001, INIT-PRISM-001, INIT-OMNISKILL-001.
  3. Import the five ROADMAP.md files we wrote via prismctl roadmap import (assigning stable RMI-- IDs).
  4. Add the PRISM Control pointer section to each repo's CLAUDE.md so future sessions find claimable work via prismctl work ready.
  5. From then on, all work follows the session protocol: plan → claim → execute with Refs: trailers → complete with evidence.

Want me to proceed with steps 1–4?