Skip to content

Ops question definitions

Checklist for creating or fixing an in-game question definition from the ops agent. The domain guides are the same ones Cursor uses. This page names the ops tools.

Read the listener system and authoring question definitions before drafting. Use league event state for the target league only.

Checklist

  1. Name the league and the prop. What event asks it, what proves yes, and what proves no.
  2. List existing names for that league with GET /api/question-definitions?league=.
  3. Confirm payload shapes with search_recording on a real internal match id. Do not invent field paths.
  4. Clone the closest existing row's shape: group, no-path, and correction window. POST /api/question-definitions/{id}/clone goes through propose_writes.
  5. Draft triggers, extract, choices, weights, and points. Read question definitions for field roles.
  6. If the prop needs a running count or a first-this-phase flag, confirm a published match_state key in the league event-state guide. If it is not listed, stop. Do not invent a key and do not edit listener code.
  7. Smoke-test the conditions against a recording hit from search_recording.
  8. Save with propose_writes:
  9. create: POST /api/question-definitions
  10. replace: PUT /api/question-definitions/{id}
  11. archive: POST /api/question-definitions/{id}/archive

Archiving means the in-game question will not be asked again. Questions already sent keep their old wording.

A definition change does not rewrite questions that were already issued.

What this page does not do

Do not run aws, do not open a database shell, and do not write SQL to save a definition. The admin API is the save path, and Slack Approve runs it.