Channel Contract v0
Scope
Defines the canonical channel contract for AIOS top-level channels in v0:ssh_remotedialog
Terminology
- Top-level channels: only
ssh_remoteanddialog. - Remote mode:
ide_primaryorterminal_fallbackunderssh_remote. - Target: concrete endpoint/tool/channel target in
dialog(e.g. codex/wechat/telegram).
Normative Spec
Channel Set
AIOS v0 MUST expose only two top-level channels:ssh_remotedialog
ssh_remote MUST include remote_mode and only allow:
ide_primaryterminal_fallback
Dialog Event Set
dialog event types are fixed in v0:
messagetool_callstatuserror
Envelope (minimum)
All channel messages/events MUST include:channel_typesession_idstream_idseqtimestampcorrelation_idtargetevent_typepayload
workspace_idagent_idmessage_iddedup_keyresume_cursorstatus_codeerror_coderetry_count
Routing Identity Rule
- Stable routing key MUST be
workspace_id + agent_id. session_idis transport/session state only.
Data Boundary Rule
dialogand terminal content underssh_remoteare forward-only.- Platform persistence is metadata-only.
Examples
Error & Recovery
- Invalid
channel_typeorremote_mode: reject. - Missing required envelope fields: reject.
- Reconnect semantics for
dialogMUST support at-least-once + receiver idempotency. ide_primaryfailures MAY downgrade toterminal_fallbackwith explicit reason code.
Security & Audit
- All channel events MUST be traceable via
correlation_id. - No transcript persistence in platform storage.
- Gateway remains sole routing/policy authority.
Status
Current status:draft
Source discussions:
docs/maintainers/conversation-records/agent-platform/2026-03-24-channel-contract-v0-draft.mddocs/maintainers/conversation-records/agent-platform/2026-03-24-p0-freeze-result-accepted.md
Changelog
- 2026-03-24: Initial skeleton created.
- 2026-03-24: Added normative channel set, envelope, routing, and forward-only constraints.