Concepts
The AgentFlow vocabulary — workspaces, authority requests, the decision ceremony, receipts, delivery modes, and the audiences.
The pipeline
Glossary
| Term | Meaning |
|---|---|
| Workspace | An organization boundary — the tenantId on API objects. Every request, user, connection, and configuration belongs to one workspace. |
| AI agent connection | An agent identity plus its x-ai-agent-key access key and a delivery configuration. Keys are issued by operators in the console; the raw key is never stored after creation. |
| Routing | The rule that assigns incoming requests to a person or a role. Routing decides which approver's queue a request lands in — unless the agent names one directly with recipientUserId. |
| Authority request | One ask from an agent: externalRequestId + idempotencyKey (unique per connection), title, action summary, display snapshot, content hash, expiry, risk level. |
| Request status | pending → opened → decision_in_progress / verification_required → approved or rejected (final), plus expired, failed. |
| Decision intent | Step 1 of the decision ceremony in the TrustLoop app: the assigned approver records approve or reject. |
| Identity verification | Step 2: the approver verifies their identity on-device (for example with biometrics). A successful verification is required to finalize. |
| Decision | Step 3: the decision finalizes — the status flips, an Ed25519 receipt is signed, audit events are written, and any webhook delivery is queued. |
| Receipt / proof | The signed artifact: an Ed25519 signature over {requestId, decisionId, outcome}, referenceId: AUTH-<externalRequestId>, verificationRule: 'local-ed25519'. getProof returns the verifiable form. |
| Delivery mode | How a finished decision reaches the agent: polling (always on — getStatus + getProof) or webhook (a signed approval.completed callback, at-least-once — dedupe by eventId). |
| Audit trail | An append-only, hash-chained log of every action in the workspace. Operators browse and verify it in the console — see Audit trail. |
Actors
- Agents authenticate with
x-ai-agent-keyand only ever see requests submitted by their own connection. - Approvers are workspace users who review and decide requests in the TrustLoop mobile app.
- Operators are console users. Workspace admins manage their own workspace; platform admins (the AgentFlow team) can act across workspaces.
Assignments
Routing produces a single assignee per request: the request lands in that person's queue, and only they can decide it.