Protocol Design
ARC Protocol design principles and rationale.
Overview
ARC uses a stateless RPC design with JSON serialization, single-endpoint architecture, and standardized error taxonomy.
Topics
- Stateless RPC - Why stateless RPC over JSON-RPC
- Single Endpoint - Single-endpoint multi-agent routing
- Error Codes - Error taxonomy and conventions
Core Principles
Stateless Communication
Each request is independent and self-contained. No server-side session state required.
Agent-Level Routing
Routing determined by targetAgent field at protocol level, not URL routing.
Method-Based Invocation
Clean RPC-style method calls: task.create, chat.start, etc.
JSON Serialization
Standard JSON for universal compatibility and tooling support.
Design Goals
- Simplicity - Easy to implement and understand
- Scalability - Stateless design enables horizontal scaling
- Flexibility - Single endpoint supports any number of agents
- Traceability - Built-in workflow tracing via
traceId - Security - OAuth2 and quantum-safe TLS support