Capture status
Wait
Looking for recent Mission Control activity in this workspace.
Setup path
Connect Mission Control before compliance setup.
This path is deliberately short: install capture, make one Mission Control request, and confirm activity in Primust. Use regulations setup later when you are ready to bind frameworks and obligations.
Steps3Blocking0
Last activity
None
Last 7 day workspace window.
This is the first-run tour for a CISO or security owner who wants visibility into Mission Control work before deciding which controls to map.
Guided setup
Three steps to visible activity.
The hook captures bounded governance metadata and commitment hashes. Prompts, source content, and model outputs stay out of Primust.
1Install hook
Run the initializer
On a developer machine with Claude Code, Codex, or Cursor installed, run the Primust initializer. It validates auth, detects supported hosts, and wires capture.
pip install primust primust init
2Smoke test
Make one agent request
Ask Claude Code, Codex, or Cursor to inspect a small file, summarize a diff, or draft a harmless change. Close the task so the session evidence can land.
The goal is not enforcement. The goal is to prove the capture path from developer machine to dashboard.
3Checking
Confirm in Primust
Looking for recent Mission Control activity in this workspace.
Ready for control mapping?
Once activity is visible, bind a governance program only if the customer wants regulatory coverage, obligation compilation, and control-plan approval.