Skip to content
KHAMSEEN

Integrations

Channels & interconnections

Adapters normalize chat, mail, and HTTP into kernel events. Human gates and QA apply on every surface — no shortcut around the graph.

Humans and systems meet the OS through adapters — Slack, WhatsApp, email, webhooks, MCP, and your own APIs. Same lifecycle; different surfaces.

SLACKworkspaceWHATSAPPBusiness APIEMAILSMTP / inboundWEBHOOKSHTTPGITHUBVCSLINEARissuesMCP / TOOLSagent runtimeCALENDARscheduleCONTROL PLANEGATEWAY

Selected channel

Slack

Ingress

slash · mention · thread reply

Egress

run updates · approval cards · alerts

Adapters normalize external surfaces into kernel events. Human gates and QA stages apply regardless of channel — chat is not a shortcut around the graph.

Approve from chat

  1. Run reaches HUMAN_APPROVAL
  2. WhatsApp delivers signed prompt to Human Authority
  3. Approve → kernel advances → Slack notifies #ops

Ticket-driven delegate

  1. Linear issue moves to DELEGATE
  2. Chief of Staff mounts sub-module graph
  3. Evidence links posted back to issue + GitHub PR

Webhook boundary

  1. External system emits webhook (verified)
  2. Mapped to REQUEST → PLAN — never bypasses QA
  3. Outbound webhook fires only after DONE or explicit gate