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¶
- Name the league and the prop. What event asks it, what proves yes, and what proves no.
- List existing names for that league with
GET /api/question-definitions?league=. - Confirm payload shapes with
search_recordingon a real internal match id. Do not invent field paths. - Clone the closest existing row's shape: group, no-path, and correction
window.
POST /api/question-definitions/{id}/clonegoes throughpropose_writes. - Draft triggers, extract, choices, weights, and points. Read question definitions for field roles.
- If the prop needs a running count or a first-this-phase flag, confirm a
published
match_statekey in the league event-state guide. If it is not listed, stop. Do not invent a key and do not edit listener code. - Smoke-test the conditions against a recording hit from
search_recording. - Save with
propose_writes: - create:
POST /api/question-definitions - replace:
PUT /api/question-definitions/{id} - 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.