User Guide
How the current Primust app is organized, how the six-step setup wizard works, and where to go next once the system is live.
If you have access to the app and want to know “where do I click next?”, start here. This page maps the real UI labels to the underlying governance flow.
Start Here
| If you want to... | Open this first |
|---|---|
| Set up a new governed system | /setup/regulations via Governance → Setup Wizard |
| See whether governed runs are landing | Monitoring → Run Explorer |
| Review obligations, controls, and approvals | Governance → Overview |
| Assemble something shareable for auditors or partners | Proof Sharing → Evidence Packs |
| Inspect upstream credential reliance | Proof Sharing → Upstream Credentials |
| Debug coverage or chain issues | Monitoring → Advanced Diagnostics |
How The Sidebar Is Organized
| Section | What it is for |
|---|---|
| Overview | The operating overview page. Use it to see whether governance is active, runs are landing, and proof is ready to share. |
| Governance | The policy and setup side of the product: programs, applicability, obligations, controls, approvals, and the setup wizard. |
| Monitoring | The runtime side: runs, gaps, and deeper diagnostics for chain and coverage issues. |
| Proof Sharing | Evidence Packs and upstream credential review. |
| Manage | Settings, API keys, and basic environment control. |
The Six-Step Setup Wizard
The setup wizard is the canonical onboarding path for consequential or regulated systems. In the current app, the progress indicator is:
Regulations -> Applicability -> Obligations -> Controls -> Approve -> Run| Step | What you do | What Primust creates |
|---|---|---|
| Regulations | Select programs that apply to the system. | Program selection draft |
| Applicability | Confirm role, system class, jurisdictions, and key facts. | ApplicabilitySnapshot |
| Obligations | Review what actually applies and which obligations need runtime or manual evidence. | ObligationPlan |
| Controls | Review executable checks, document gaps, and not-applicable rows. | ControlPlan |
| Approve | Approve the active plan chain with an explicit role and decision. | Approval |
| Run | Copy the run command and start emitting governed runtime evidence. | Active governed execution path |
What Happens After Setup
Governance Overview
Review the posture of the active system portfolio: in-scope systems, approvals, re-approval needs, manual evidence status, and critical gaps.
Programs
See which programs are available and active, and use them to reason about scope.
Applicability
Review immutable applicability snapshots so you know what was in scope when plans were compiled.
Obligations
Inspect the actual requirements and whether they need runtime evidence, manual evidence, or are not applicable.
Control Plans
See which checks are auto-covered, which need code changes, and which need document upload or explicit rationale.
Approvals
Review the decision ledger for plan approval, re-approval, and superseded history.
The Runtime Loop
- Run the instrumented system
- Open Monitoring → Run Explorer
- Check assurance, provable surface, pending upgrades, gaps, and approved plan status
- Open individual runs to inspect obligations, controls, proof artifacts, lineage, and exports
- If gaps exist, use Gap Inbox or the run detail to resolve them
Proof Sharing Flow
- Open Proof Sharing → Evidence Packs
- Select the VPECs you want to include
- Assemble the Evidence Pack
- Export or share the pack, hosted verify link, or other formats as needed
- For upstream dependency review, use Upstream Credentials
Common Honest States You Will See
- No governance programs configured yet means setup has not been completed, not that the system is already compliant.
- No obligation context available or No control plan context available usually means the run predates the active governance chain or was emitted without full setup.
- Proof artifacts will appear here when proofs complete means async upgrades are still pending, not that the core run failed.
- No upstream verifications yet means no upstream VPEC verification activity has been recorded for that org yet.
Fast Paths By Role
| Role | Primary path |
|---|---|
| Developer | Setup Wizard -> Run command -> Run Explorer -> Evidence Packs |
| Security / compliance | Governance Overview -> Applicability -> Obligations -> Control Plans -> Approvals |
| Relying party | Evidence Pack / CLI / verify.html -> Audit Guide |
If you want the shortest implementation path, go to Quickstart. If you want task-based entry points, use Common Scenarios. If you need exact field and route names, use the Technical Reference.