KOkobaltlabs
risk-assessment

Unapprove Factor

Undo an approval and go back to PROPOSED.

Also clears attribution, mirroring requirement_checks.py's /unapprove. It does not touch manual_inherent_risk_label — undoing an override is PATCH .../{id} with manual_inherent_risk_label: null, a distinct action from undoing an approval.

post/risk-assessment/factor-assessments/{factor_assessment_id}/unapprove

Request

  • Base URL
    https://api.kobaltlabs.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.kobaltlabs.com/risk-assessment/factor-assessments/{factor_assessment_id}/unapprove
  • Auth
    none declared

Path parameters

factor_assessment_idstring uuid required

Response

Successful Response

factor_assessment_idstring uuid required
status'queued' | 'running' | 'complete' | 'error' required

Lifecycle of one factor's assessment within a run.

There is no deferral state: a factor either produces a rating its rationale can defend, or it errors. Missing evidence is narrated in the rationale.

progress_pctinteger nullable required
current_activitystring nullable required
review_state'proposed' | 'approved' | 'overridden' required

Where a human reviewer stands on the agent's proposed rating.

Written by the approval workflow (M5); until then every completed factor sits at PROPOSED, which is what renders the "Kobalt proposed" chip.

reviewer_namestring nullable required
reviewed_atstring date-time nullable required
citation_countinteger required
distinct_document_countinteger required
step_countinteger nullable required
duration_msinteger nullable required
errorstring nullable required
agent_run_idstring uuid nullable required

Changes

No recorded changes to this operation across all 8 revisions of this API.