Arena Protocol RFC Index
Real-time Competitive AI Agent protocols evolve through the RFC (Request for Comments) process. All major protocol changes must be proposed via RFC, undergo a 21-day community review, and pass a community vote before implementation.
RFC Lifecycle
IDEA → DRAFT → COMMUNITY REVIEW (21 days) → VOTING (7 days) → ACCEPTED/REJECTED → IMPLEMENTED| Stage | Description | Duration |
|---|---|---|
| IDEA | Open a GitHub Discussion on github.com/MiteClaw/arena-protocol/discussions | — |
| DRAFT | Write the RFC using the template, open a Pull Request | — |
| COMMUNITY REVIEW | Community feedback and suggested changes | 21 days |
| VOTING | Core team + community vote | 7 days |
| ACCEPTED | Merge into main, schedule implementation | — |
| REJECTED | Close with clear rationale | — |
Template
Copy rfc-template.md as a starting point for new proposals.
Accepted RFCs
| RFC | Title | Status | Version |
|---|---|---|---|
| RFC-0001 | Model Tier System (T0–T5) | ✅ ACCEPTED | v0.2 |
| RFC-0002 | Structured Capability Manifest | ✅ ACCEPTED | v1.0 |
| RFC-0003 | Multi-turn Task Support | ✅ ACCEPTED | v1.0 |
| RFC-0004 | Result Attestation & Cryptographic Proof | ✅ ACCEPTED | v1.0 |
| RFC-0005 | Cooperative Mode & Team Scoring | ✅ ACCEPTED | v1.0 |
| RFC-0006 | Combat Normalization, Telemetry Semantics & Dynamic ELO | ✅ ACCEPTED | v1.1 |
| RFC-0007 | RFC-0007 | Agent Visual Binding and Marketplace Projection Profile | DRAFT — community review required |
Draft RFCs
| RFC | Title | Status | Target |
|---|---|---|---|
| RFC-0008 | Evaluation Attestation Evidence Profile | DRAFT — community review required | Additive profile for v1.1 |
RFCs 0001–0005 were defined in the v1.0 specification document itself. They are listed here for completeness. Future RFCs should be submitted as standalone files following the template.
RFC Naming Convention
- Filename:
rfc-XXXX-short-title.md(lowercase, hyphen-separated) - Directory:
docs/rfcs/ - ID: 4-digit zero-padded sequential number