@xema/omni-protocol 0.1.115 → 0.1.116
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/guide.md +1 -1
- package/package.json +1 -1
package/guide.md
CHANGED
|
@@ -46,7 +46,7 @@ are used precisely throughout and mean nothing looser here.
|
|
|
46
46
|
| **Call** | The caller’s complete phone call, which may continue through IVRs, queues and several agents. The protocol never describes the IVR or the queue; it carries the call's history and details to whichever agent holds it now. |
|
|
47
47
|
| **Assignment** | The call routed to this agent, from the offer until the task ends. It is the one thing that crosses: the provider assigns, names the assignment with `assignmentId`, and that is the only name the agent computer ever uses back. A call that comes back is a new assignment on the same call, and a declined or lapsed offer is an assignment that became nothing more. What the platform calls its own record, and whether it reuses that name, is the adapter's business and unknown to the agent computer. |
|
|
48
48
|
| **Interaction** | The agent's time on the call, from answer until their audio ends: the `in-progress` and `paused` phases. An assignment produces at most one interaction, and a call that returns produces a new assignment and so a new interaction. |
|
|
49
|
-
| **Task** in `guide/agent.md` | The agent computer's record of one assignment, from offer through wrap: the workspace, controls and completion work the agent has for it, described by the provider and held by the agent computer. A task is identified by the assignment it is the record of. `pending`, `confirmed` and `preview` are assigned and not yet interacting; `in-progress` and `paused` are the interaction; `completing` is the assignment outliving its interaction. A voice task is one assignment, never the caller's whole call. |
|
|
49
|
+
| **Task** in `guide/agent.md` | The agent computer's record of one assignment, from offer through wrap: the workspace, controls and completion work the agent has for it, described by the provider and held by the agent computer. A task is identified by the assignment it is the record of. `pending`, `confirmed` and `preview` are assigned and not yet interacting; `in-progress` and `paused` are the interaction; `completing` is the assignment outliving its interaction. A voice task is one assignment, never the caller's whole call. **Task is the word on every channel**: voice, chat and email each hand an agent the same unit, offered, worked and wrapped under one assignment, and chat and email have no call. So a channel platform's own name for one agent's part of a contact -- an agent call on a phone platform -- is a task here, and the platform's record of the whole contact across agents and callbacks is the backend's, outside this protocol. |
|
|
50
50
|
| **Channel** | The kind of work a provider carries: `voice`, `chat`, or `email`. Fixed per provider by its manifest. |
|
|
51
51
|
| **Task type** | The provider's own name for a category of work — a queue, a mailbox folder, a chat source. Free-form, and finer-grained than a channel. |
|
|
52
52
|
| **Capability** | A provider's declaration that a control exists for a task or a session. It says *offer this*; the provider performs it, and the agent application only offers it — see **Where a command executes** in `guide/agent.md`. |
|