slash_response
slash_response is implemented by handleSlashResponse in src/api/handlers/slash/slash_response.osl.
Handles the slash response protocol operation through the resource-specific helper and storage layers.
Access
Section titled “Access”| Gate | Requirement |
|---|---|
| Authentication | Required by the central API gate. |
| Central permission | None. Resource, channel, ownership, or hierarchy checks may still apply in the handler/helpers. |
| Broadcast | Not marked global directly by this adapter. A helper may emit focused or server-wide updates. |
Request
Section titled “Request”Every request includes cmd: "slash_response" and may include an opaque listener correlation value.
| Field | Validation / meaning |
|---|---|
id |
schema.string() |
response |
schema.string().trim().minLen(1) |
author_id |
schema.string().optional() |
key_id |
schema.string().optional() |
signature |
schema.string().optional() |
Validator source
Section titled “Validator source”The handler and shared validation path use these OSL schema definitions before normalization:
*schema.Schema schemaSlashResponse = schema.object({ id: schema.string(), response: schema.string().trim().minLen(1), author_id: schema.string().optional(), key_id: schema.string().optional(), signature: schema.string().optional()})Processing path
Section titled “Processing path”handleCmdenforces authentication.dispatchCmdroutesslash_responsetohandleSlashResponse.- The adapter validates and normalizes input, then calls its domain collaborators.
- Durable mutations complete before the response or event is returned.
onMessageadds the request listener to direct responses and performs any marked broadcast.
Direct collaborators visible in the handler: slashPruneCalls, conn, messageContext, messageSigningData, typeof, slashReply, ephemeral, sendUser
Responses and events
Section titled “Responses and events”Response/event command names visible in this adapter: slash_response.
Validation and domain failures use:
{ "cmd": "error", "val": "<message>", "src": "slash_response", "listener": "<copied from request>"}