Edit a suite under optimistic revision control

Every accepted edit appends a NEW immutable revision instead of mutating content, so a run that pinned an earlier revision keeps reading exactly what it executed. The request must carry the revision the edit is based on; a stale write returns 409 with the revision that beat it and never overwrites. Scenario personas may carry bounded interruption and intent-change rules that drive an adaptive caller, and each scenario may carry up to five semantic rubrics; a rubric is a separate evaluator call on every attempt, which is why that ceiling is low.

patch/v1/agents/{agent_id}/simulation-suites/{suite_id}

Request

  • Base URL: https://api.skysay.ai
  • URL: https://api.skysay.ai/v1/agents/{agent_id}/simulation-suites/{suite_id}
  • Auth: none declared

Path parameters

agent_idstring required
suite_idstring required

Request body

baseline_run_idstring

A finished run of THIS suite that later runs are compared against. Send an empty string to clear it. A run belonging to another suite, one that is still going, or one that recorded no attempts is refused with 400 -- each would make the comparison meaningless.

default_snapshot_source'draft' | 'published'
descriptionstring
namestring
policyobject
revisioninteger required

The revision this edit is based on.

status'active' | 'archived'

Response

Suite at its new revision

Changes

No recorded changes to this operation across all 1 revision of this API.