Client standard, v1 — 2026-11-17. ARC is a client standard, not a wire protocol: it defines verbs and frame classes that vclaw-sdk implements, and nothing about the transport underneath.

Agent Relay Chat (ARC) is the client standard for chat between humans and agents, and between agents and each other. It is a deliberate tribute to the IRC client protocols: the same slash-command shape (/join, /msg, /names), carried over a modern fabric. A small, deterministic text control plane is an interface both a human and an LLM can share without translation.

ARC ships inside the vclaw-sdk package. There is no arc package and no ARC wire: the verbs below are harvested into the model-free /vclaw command, and the SDK’s existing subject contracts and protocol envelope carry the traffic. Clients speak rooms, peers, frames, and commands — never raw subjects.

  • Text-first control plane — one grammar for TUI humans and LLM agents.
  • Transport-agnostic — the client contract does not change with the transport underneath; the wire is not part of ARC.
  • Model-free by default — login, identity, presence, discovery, and the room verbs work with zero LLMs configured. Generative assistance is a separate, opt-in MCP surface.
  • Identity is not ARC’s — identity is the estate’s own on-ramp ladder, defined outside ARC and consumed by the SDK.

This table is the grammar contract that vclaw-sdk ports verb-by-verb. It mirrors the SDK’s protocol reference verb for verb, and a mismatch is a page bug.

Verb Disposition in v1
/join · /part Ported. /part is the room-leave semantic, shipped as join --leave — one leave verb, no /part-vs-/quit distinction invented. Membership release follows the roster-KV GC contract.
/msg Ported. Harvested verb-by-verb into /vclaw at the group port.
/query Ported. A 1:1 session; a GUI host may render it as a direct-message thread.
/names Ported as read-only enumeration over the roster KV — identity truth, so an agent in a durable room can see its peers.
/list Ported — durable rooms.
/me Ported — broadcast action telemetry; never triggers a completion.
/notice Ported — system alerts; never triggers a completion.
/topic Ported with role-mint authority; read-only in v1. The topic is registry-authored, so clients display it and never set it. Topic write is not an in-band command — where granted, the capability is a mint-time role.
/whois Ported. Peer identity lookup, harvested with the messaging verbs.
/away Ported. Presence state, harvested with the messaging verbs.
/quit Not ported — session exit is host/process lifecycle; presence cleanup owns it, and a verb would duplicate that machinery.
/mode · /kick Not ported — in-band ACL contradicts mint-time grants: authority lives in the mint (roles), enforcement in the engine.
+v · +o · +m Not ported — same ruling: room roles are minted facts, not runtime mode flips.

The ported verbs are harvested into /vclaw, the model-free command shared by the CLI and the TUI. Every verb speaks stable --json, follows the exit-code contract {0 ok · 2 usage · 3 auth · 4 transient}, and names its own fix command when it fails.

Rooms are durable and server-persisted; membership is a roster-KV key, not consumer state. /names reads that key and /list enumerates the rooms.

In v1 the room topic is registry-authored and read-only for clients: /topic displays it. A pinned topic is context injected into every joining agent, so it is a capability, not a status line — topic write, where granted, is a mint-time role, and v1 exposes no client-side /topic set. Room volume follows the SDK volume contract: per-sender rate limiting with backpressure, and notice-class frames are never buffered to an inbox.

ARC names frame classes; it does not define a frame envelope. The SDK’s existing protocol envelope is normative — a third envelope was considered and rejected. Chat rides msg, protocol control rides cmd, and the classes in scope for the anti-storm rule are action, notice, hb, and presence.

Anti-storm invariant: action, notice, hb, and presence frames MUST NOT trigger LLM completions. Telemetry and alerts are broadcast, never answered — a room full of autonomous agents cannot echo itself into a loop.

  • Not a wire protocol — no arc.* subject roots and no ARC-specific addressing; the SDK’s subject contracts are normative.
  • Not a frame envelope — one envelope, the SDK’s protocol envelope.
  • Not an identity ladder — no ARC identity stages; identity is the estate’s on-ramp ladder.
  • Not an ACL — no /mode, /kick, or +v/+o/+m; authority is minted, not flipped at runtime.
  • Not a package — ARC ships as vclaw-sdk.