Developers · Integration
Compatibility reference
Raw event names, historical state enums, and compatibility endpoints. These identifiers appear in webhook payloads, API responses, and memory files. They are documented here for reference — they are not the recommended integration surface.
session_completed, proof_created, and the approve-plan flow. The identifiers on this page are compatibility surface — they will remain stable but are not the primary developer story.Overview
Zero's internal model uses execution state names (OPEN, INVESTIGATING, IMPLEMENTING, VERIFYING, RESOLVED) and event names (case_state_changed, case_updated) inherited from the original Case model. These appear in raw API responses and webhook payloads.
For most integrations, you do not need to watch state transitions. Instead:
- Listen for
session_completedto know when a run finishes - Listen for
proof_createdto know when evidence is attached - Use
GET /cases?state=RESOLVEDonly for historical queries, not as a live trigger
Event names
| event_type | What it means | Recommended alternative |
|---|---|---|
case_state_changed | Internal execution state changed. Payload includes old_state and new_state. | Use session_completed or proof_created for work-done signals. |
case_updated | Work item fields updated (title, description). | No alternative needed — this is already a Work-level event. |
agent_completed | Agent run finishes (plan mode or work mode). Fires after each mode. | Prefer session_completed for end-of-session signals. |
State enums
Work item execution states. These appear in API responses (GET /cases) and case_state_changed payloads.
| State | Meaning |
|---|---|
OPEN | Work defined. No session started yet. |
INVESTIGATING | Planning session in progress. Agent forming hypothesis. |
IMPLEMENTING | Work mode: approved plan executing. |
VERIFYING | Execution complete. Proof gate evaluated. |
BLOCKED | Operator decision required. Execution paused. |
RESOLVED | Verified proof attached. Work closed. |
NON_ISSUE | Work item triaged as not actionable (duplicate, intended behavior, etc.). |
State transitions are driven by session events and operator approvals, not by direct API calls. PUT /cases/:id/state exists as a compatibility endpoint but is not the recommended path.
Legacy endpoints
| Method | Path | Notes |
|---|---|---|
PUT | /cases/:id/state | Direct state transition. Compatibility path — bypasses session execution and proof gate. Use for scripting or migration only. Prefer session-based flow. |