Risk Approvals

Risk inherits the control-plane Dual Control API (/v1/approvals). This page lists Risk-specific actions, who may approve, and what the model is allowed to do while a request is pending.

Gated Risk actions

Ordinary inference (triage: true, briefs, maps) is not gated. Publishing those outputs out of Eridian is.

Propose from a report

POST /v1/approvals
Authorization: Bearer eridian_sk_...

{
  "project_id": "prj_risk_001",
  "action": "risk.report.approve",
  "resource": "rpt_0912",
  "payload": { "format": "pdf" },
  "justification": "Eval evr_risk_12 citation_coverage=1.0 pii_leak=0."
}

The proposer cannot approve. Approver needs governance:manage or risk:approve (alias on Enterprise). Same SSO principal is rejected.

While status: pending, GET /v1/risk/reports/rpt_0912/content from a production integration key returns 403 dual_control_required with param equal to the apr_ id.

High-risk tools

If a template may call an outbound tool (block a CIF, release a held payment), mark it:

{
  "template_id": "tpl_fc_tools_v1",
  "tools": [
    { "name": "customer_block", "high_risk": true }
  ]
}

The inference call then returns 403 dual_control_required instead of executing the tool. After approve, retry with the same Idempotency-Key. See Inference.

Timeouts

Pending Risk approvals expire in 24 hours by default (1 to 72). Expiry does not close the case. It leaves the report in draft.

Audit

Events: approval.approved, approval.rejected, risk.report.approved, risk.case.closed. These appear in Audit Log and in examiner Evidence Export.

Segregation

409 segregation_of_duties if assignee and reviewer are the same on high-severity cases, or if the approver is the analyst who drafted the report. Fix membership, do not disable the gate.

See Dual Control for the generic propose/approve contract.