KOkobaltlabs
internal

Debug Requirement

Changed on

One requirement, as the thing to be judged rather than a row in a ranking.

Three questions in one response, because answering them separately is what makes a reader guess: what does this rule say now, where in the standard did it come from, and what has it actually done to real collateral.

get/internal/evals/rollout-consistency/sweeps/{sweep_id}/requirements/{requirement_id}

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}/requirements/{requirement_id}
  • Auth
    none declared

Path parameters

sweep_idstring uuid required
requirement_idstring uuid required

Response

Successful Response

requirement_idstring uuid required
revision_idstring uuid required
revision_numberinteger required
state'active' | 'disabled' | 'archived' | 'superseded' | 'proposed' required

Whether a requirement is in the working library, and if not, why not.

All of them are recorded as revisions, so every one is reversible and readable.

ARCHIVED and SUPERSEDED are deliberately distinct: ARCHIVED is a person deciding this obligation does not apply to them, SUPERSEDED is a newer decomposition of the same guideline taking over. A regeneration must never overwrite the first with the second — that would erase a human decision.

requirement_textstring required
judging_guidancestring nullable required
trigger_termsstring[] required
collateral_typesstring[] nullable required
marketing_team_idsstring[] nullable required
flagged_on_truncatedboolean
drift_truncatedboolean

Changes