KOkobaltlabs
internal

Set Review

Mark a worklist row as reviewed, or clear the mark.

First writer wins: a concurrent mark for the same row returns the existing one rather than overwriting who reviewed it. Clearing deletes the row — this is staff bookkeeping, not a customer record, so there is nothing to retain.

post/internal/evals/rollout-consistency/sweeps/{sweep_id}/reviews

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/internal/evals/rollout-consistency/sweeps/{sweep_id}/reviews
  • Auth
    none declared

Path parameters

sweep_idstring uuid required

Request body

subject_kind'rule_drift' | 'low_signal' | 'regression' | 'item' required

What a collaborative review mark is attached to on one sweep.

Four kinds, kept apart because a requirement can show up on both the drift worklist and the low-signal list, and a mark on one is not a mark on the other. The id is the row the dashboard already uses as the key: requirement_id for the two rule lists, regression_id for a baseline risk, item_id for a piece of collateral.

subject_idstring uuid required
reviewedboolean required

Response

Successful Response

review_idstring uuid required
sweep_idstring uuid required
subject_kind'rule_drift' | 'low_signal' | 'regression' | 'item' required

What a collaborative review mark is attached to on one sweep.

Four kinds, kept apart because a requirement can show up on both the drift worklist and the low-signal list, and a mark on one is not a mark on the other. The id is the row the dashboard already uses as the key: requirement_id for the two rule lists, regression_id for a baseline risk, item_id for a piece of collateral.

subject_idstring uuid required
reviewed_by_user_idstring uuid nullable required
reviewed_by_emailstring required
reviewed_by_namestring required
reviewed_atstring date-time required

Changes

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