Pretorin Compliance

Upload STIG scan results from a CLI scan run.

Move an in-progress vendor assessment to submitted.

Suggest and return an editable definition from human-authored title/purpose context. Waits for the durable advisory job; never saves, submits, or approves a policy.

Bulk sync all stale inherited controls from their source narratives.

Transition work on an action in an approved canonical Issue plan (see approve_issue_plan).

Trigger AI review for all controls in a family. Reviews each control sequentially and returns aggregated findings. May take 2-4 minutes for large families. Poll get_family_review_results with the job_id.

Trigger AI generation of the policy document from answered questions. By default this also runs AI review in the same durable job. Returns a job ID. Use AFTER answering policy questions. Optionally provide system_id for scope context.

Trigger AI review of policy answers/document. Returns a job ID for polling. Poll get_policy_review_results with the job_id.

Trigger AI generation of the scope document from answered questions. By default this also runs AI review in the same durable job. Returns a job ID for polling. Use AFTER answering scope questions. Poll get_scope_review_results with the job_id until status is 'succeeded'.

Trigger AI review of scope answers. Returns a job ID for polling. Use to check answer quality BEFORE or AFTER generation. Poll get_scope_review_results with the job_id.

Remove an artifact link from a risk.

Deprecated checkpoint compatibility only. Record a legacy Campaign worker phase for observers. Preflight is informational: use degraded or unavailable metadata and continue without sources.

Commit agent-authored working fields for one CCI before approval. Ordinary updates may only set status=in_progress; use approve_cci_implementation for the explicit CCI completion decision. This operation never approves the parent control.

Start or reopen authoring for a control by setting status to in_progress within exactly one active system/framework scope

Completely replace an action on a draft canonical Issue treatment plan.

Completely replace an editable canonical Issue treatment-plan draft.

Push a narrative text update. Normally MCP agents must pass a narrative-producing recipe_context_id and non-empty evidence_ids so narrative claims are tied to evidence. The sole evidence-free form is needs_input_only=true for a trusted initial/interim Campaign worker: omit narrative and recipe_context_id and pass evidence_ids=[]; Pretorin deterministically renders only frozen coordinator-preflight and current objective limitations. It requests review only when the Campaign's frozen publication policy explicitly requires it. preserve_human=true records an accurate human parent without rewriting it; readiness stays pending. Use evidence_citations to preserve claim-level grounding from search_evidence. Citations do not satisfy expectation coverage: complete the plan's evidence-expectation mapping step before composing the narrative. Review is off by default and is only an explicit user-requested exception after the final narrative generation is stable. A normal Plan-attributed single-control save returns the verified mapping gate and expectation-coverage read-back for handoff.

Commit agent-authored working fields for one assessment objective before approval. Ordinary updates may only set status=in_progress; use approve_objective_implementation for the explicit objective completion decision. This operation never approves the parent control — objectives are leaves and issues live at the control level.

Update one step's status and/or outcome summary. Status transitions are guarded: pending -> in_progress | skipped; in_progress -> completed | skipped; terminal states are sticky. Skipping a step requires a non-empty outcome_summary explaining why — the plan cannot complete without it. Workflow-required phases cannot be skipped and require an outcome summary. A selected recipe step cannot be skipped or completed without its exact start_recipe/end_recipe receipt. Completing the single-control evidence-expectation mapping step requires a structured evidence_mapping record with declared keys, bindings, intentionally unbound evidence, and the post-link coverage read-back. Campaign child completion verifies that record against a fresh authoritative get_control_context response. Refused if the plan itself is completed or cancelled.

Replace a custom definition using its expected revision; may require reset_authoring.

Replace an org policy's generated narrative sections. An approved policy is locked — call reopen_policy first (this returns a 422 policy_locked error otherwise). Read the current sections first with get_policy_narrative, then pass the full ordered list of sections back; each is an object with section_id, title, and content.

Bind resolver collections to recommended source kinds and persist the preflight artifact. Each kind maps to a COLLECTION of resolvers (each tells a distinct piece of the evidence story). Replaces a kind's collection wholesale. Resolver types are open: workspace_path, cli_tool, command, manual/attested, mcp, connected_api, pretorin_feature, or any custom type with a probe.

Update a risk. This is the mitigation surface — set/edit treatment, treatment_plan, and treatment_due_date through this tool (there is no separate /mitigate endpoint). Any subset of fields can be updated.

Replace the scope narrative sections for a system+framework. A completed scope is locked — call reopen_scope first (this returns a 422 scope_locked error otherwise). Pass the full ordered list of sections; each is an object with at least title and content.

Update vendor fields (name, description, provider_type, authorization_level, owner_user_id, inherent_risk).

Update a vendor contact. Requires the server-side `vendor.pii` scope (or an admin token). Only provided fields are updated.

Update a vendor contract. Requires the server-side `vendor.pii` scope (or an admin token). Only provided fields are updated. status and is_expired are server-derived and cannot be set.

Upload a file as evidence to the platform (system-scoped, requires WRITE access)

Upload a vendor evidence document (SOC 2 report, CRM, FedRAMP package, etc). Provide the file_path on the local filesystem.

Verify completed treatment and CLOSE a canonical Issue. This is the only way to close one. Requires lifecycle_status == verification_pending, which completing an approved plan produces; Issues sourced from an RFI or finding, or carrying an ai_review_finding_key, can reach it without a completed plan. The generic issue PATCH cannot close an Issue and rejects the attempt.

Probe resolver bindings in the preflight artifact and persist the results. Without source_kind, probes the full profile and refreshes its global verification timestamp. With source_kind, probes only that kind and deliberately leaves profile-wide freshness unchanged. Probes run locally on the CLI host (e.g. `gh auth status`, `az account show`, workspace path checks); the response reports verification_scope explicitly.

Void a canonical Issue that was never valid or no longer applies. TERMINAL and IRREVERSIBLE: the Issue becomes an immutable POA&M record that cannot be modified, reopened, or closed. Accepted from any non-voided state INCLUDING closed, so voiding a verified Issue destroys the audit distinction between remediated and never-valid. Requires explicit force=true confirmation; prefer verify_issue for work that was actually done.