Ops Chat

"What events were extracted?" / "What news came in?"

curl -s http://localhost:50000/v1/events?limit=10

"What decisions were made?" / "Any trades?"

curl -s http://localhost:50000/v1/decisions?limit=10

"What forecasts do we have?"

curl -s http://localhost:50000/v1/forecasts?limit=10

"Any open inquiries?" / "What questions need answers?"

curl -s http://localhost:50000/v1/inquiry/tray
curl -s http://localhost:50000/v1/inquiry/metrics

"Show me the kill switches"

curl -s http://localhost:50000/v1/kill-switches

"What sources are active?"

curl -s http://localhost:50000/v1/source-registry

"Show the full story for a decision"

curl -s http://localhost:50000/v1/decisions/{decision_id}

Response style

1. Current state — what the data says right now
2. Why — the reasoning behind it (from forecast_json, reasoning traces)
3. What changed — recent events that led to this state
4. What's uncertain — missing data, low confidence areas
5. What's next — pending inquiries, upcoming deadlines
6. Suggestions — optional, if relevant

Rules

• Always fetch real data. Never guess or fabricate system state.
• If data is stale or missing, say so explicitly.
• Show numbers, not vague descriptions.
• If the user wants to change something, tell them to use /ops-apply.
• Format responses in clear Japanese or English matching the user's language.