Terminology: Translate the implementation
Terminology: Translate the implementation
Aligning terms upfront makes every deep-dive page easier.
Quick mapping
| Term | One-line meaning | Entry points |
|---|---|---|
| Gateway | The control-plane process (connect/auth/dispatch/broadcast/audit) | Protocol / Health |
| WS (WebSocket) | Long-lived control channel: connect first, then subscribe/call | Protocol |
| method | A request action name (e.g. chat.send) | TypeBox |
| event | Server-pushed notifications (streaming, approvals, logs, …) | Control UI |
| sessionKey | Stable key that defines “which conversation this belongs to” | Sessions / Session tool |
| runId | ID for a single execution run (trace logs/events) | Logging |
| lane / queue | Ordering + concurrency: one key serial, multiple keys parallel | Queue + lanes |
| scope | Permission boundary for methods/events | Authentication |
| tool policy | Pipeline that narrows the tool surface | Tools |
| approval | Human gate for risky actions | approvals / Exec approvals |
| fallback | Try alternate provider/model on retryable failures | Model failover |
Four sentences to remember
sessionKeydecides “which conversation”.lane + queuedecides “ordering and concurrency”.scope + approvaldecides “whether a risky action is allowed”.runIddecides “how you trace a run end-to-end”.