# Event Schema Index

- `interaction.created.json`
- `interaction.assigned.json`
- `interaction.escalated.json`
- `interaction.closed.json`
- `agent.state.changed.json`
- `call.recording.ready.json`
- `call.connected.json`
- `call.transferred.json`
- `ivr.completed.json`

Each file is a JSON Schema (draft 2020-12) and can be used as a validation contract between services.

Track 8 introduces a canonical transport envelope for bus-delivered events:

- `docs/architecture/event-envelope.json`

Payload-specific schemas under `contracts/events` remain the authoritative contracts for the
domain payload inside that envelope.

Track 4 now provides the concrete schema file for the recording import placeholder:

- `docs/architecture/call.recording.ready.json`

Track 5 adds the concrete schema for IVR completion:

- `docs/architecture/ivr.completed.json`

Track 9 adds the dialplan-to-platform `UserEvent` contract reference:

- `docs/architecture/asterisk-user-events.md`

Track 11 adds additive voice lifecycle event types produced by call-control flow:

- `call.connected` (operator connected to customer)
- `call.transferred` (blind transfer requested by operator/admin)