Skip to content
Maia OS

Protocol

@maiaos/protocol owns versioned schemas and the Maia-owned parse facade. It is not an application client, node handler, or transport. Product clients consume these contracts through @maiaos/sdk. This page classifies families by status. Exact fields live in the Protocol README.

Source-implemented candidate — callable current evidence

The current schema surface includes these source-implemented contracts. They are not implemented under the release-gated AGENTS meaning:

  • generic request, response, and event envelope metadata
  • structured response errors and bounded capability descriptors
  • versioned file-first configuration documents
  • private desktop-local lifecycle messages, including node.status and node.shutdown
  • project, repository, workspace, checkout, keyed receipt.get, and bounded no-payload receipt.list contracts
  • session create, list, show, and event-page contracts

N1 framing is four-byte big-endian length plus strict UTF-8 JSON, one request and response per connection, a 1 MiB payload cap, and a five-second incomplete frame deadline.

Source-implemented candidate — blocked

These schemas exist and remain blocked. They are not enabled:

  • schema-v6 turn.send / turn.show and bounded turn projection
  • schema-v7 / v9 terminal availability and the 13 active live-terminal methods (schema v10 is the node's index-only receipt-list migration; it does not rewrite this terminal contract)
  • maia.orchestration/v1 local Run, inbox, Question, and settle contracts
  • ordinary-read harness.installed.list
  • Client-only context.show Invocation-context projection

Observer attach, controller renew, restart, delete, and reconcile schemas exist only for the wider contract and remain unavailable or inert at the node boundary.

Planned

Not present as enabled protocol product behavior:

  • approvals and structured Session attachments
  • Session/Run/Dispatch Invocation attachments
  • ADR-015 Public operation catalog descriptors/digest and Notebook lifecycle, controller, cell, variable, checkpoint, handoff, result, and error schemas
  • remote transport schemas
  • worker, sandbox, Gate, watch/wait, and device-capability contracts

MCP, ACP, A2A, and CloudEvents remain separate compatibility boundaries. They are not aliases for Maia commands.

Unsupported

No current protocol family is implemented under the release-gated AGENTS meaning. Windows process-tree ownership stays platform_unsupported until that host is proven.

Next action

Use the Protocol README and continue to the SDK and CLI notes. Architecture ownership lives in services/README.md. The accepted catalog and Notebook schemas are specified in Portable notebooks but are not exported today.