Intent Arena

Intent Arena is the real time collaboration layer. Arena combines real-time conversation, shared editing, and automatic decision extraction into a single workspace.

What Arena Provides

Arena transforms messy discussions into structured decisions. Automatically.

 ┌────────────────────────────────────────────────────────────────┐
 │                        Intent Arena                            │
 ├──────────────────┬──────────────────┬──────────────────────────┤
 │   Voice/Video    │   Shared Editor  │   Decision Extraction    │
 ├──────────────────┴──────────────────┴──────────────────────────┤
 │                    Real-time Sync (WebSocket + CRDT)           │
 └────────────────────────────────────────────────────────────────┘

Voice and Video

Arena integrates LiveKit for real-time communication:

• Voice calls for quick discussions
• Video when you need face-to-face
• Screen sharing to walk through code
• Automatic transcription of everything said

Transcription isn't just for the record—it feeds into decision extraction. Your verbal agreements become searchable artifacts.

Shared Editor

A collaborative code editor powered by CodeMirror and Automerge:

• Real-time co-editing with no conflicts
• Syntax highlighting for all major languages
• CRDT-backed for offline tolerance and merging
• Provenance tracking showing who wrote what

Multiple team members can edit the same file simultaneously. Changes merge automatically using CRDT conflict resolution—no manual merge conflicts.

Decision Extraction

As you discuss, Arena's AI extracts decisions in real-time:

• What was decided — The actual conclusion
• Why — The reasoning and tradeoffs considered
• Who — Attribution to participants
• When — Timestamped for the record

No more "what did we decide?" after the call ends. Decisions emerge as you discuss, not after.

How It Works

Creating a Session

Start an Arena session from the web interface or CLI:

intent arena create "API Architecture Discussion"

This creates a new collaborative workspace and returns a shareable link.

Joining a Session

Team members join via the shared link. Each participant gets:

• Access to the shared editor
• Voice/video controls
• Real-time view of extracted decisions
• Ability to annotate and refine extractions

During the Session

As you discuss:

1. Transcription captures everything said
2. Editor changes are tracked with attribution
3. AI monitors the conversation for decision patterns
4. Decisions appear in the sidebar as they're identified

You can:

• Accept extracted decisions as-is
• Edit them for clarity
• Reject false positives
• Manually add decisions the AI missed

After the Session

When the session ends:

1. Full transcript is saved
2. Decisions are finalized and linked to context
3. Code changes are committed to the CRDT
4. Everything syncs to the Intent Repo

The session becomes a permanent, searchable artifact. Anyone reviewing later can:

• Read the decisions
• Watch/read the transcript
• See exactly what code was discussed
• Understand the full context

Integration with Capture and Repo

Arena sessions flow into the same system as Capture:

┌─────────────┐     ┌─────────────┐     ┌─────────────┐
│   Capture   │     │    Arena    │     │    Repo     │
│  (solo AI)  │────▶│  (team)     │────▶│  (storage)  │
└─────────────┘     └─────────────┘     └─────────────┘
                           │
                    Same decision format
                    Same search index
                    Same provenance model

Whether you're working solo with Claude Code or discussing architecture with your team, decisions end up in the same place—versioned alongside your code, searchable forever.

Use Cases

Architecture Reviews

Before building a major feature:

1. Create an Arena session
2. Share screen showing the current codebase
3. Discuss approaches, tradeoffs, constraints
4. Decisions are extracted as you talk
5. Session becomes the architectural decision record

Pair Programming

Real-time collaboration on code:

1. Both developers in the shared editor
2. Voice on for continuous discussion
3. Every decision captured with attribution
4. No "who wrote this and why?" questions later

Incident Response

When something breaks at 2 AM:

1. Quick Arena session with on-call engineers
2. Screen share the logs and metrics
3. Discuss root cause and fixes
4. Decisions captured for post-mortem
5. Future on-call can search for similar incidents

Onboarding

Walking a new team member through the codebase:

1. Arena session with screen share
2. Explain the architecture and key decisions
3. Q&A captured with context
4. New hire can reference the session later

Privacy and Access Control

Arena sessions have configurable access:

• Private — Only invited participants
• Team — Anyone in your organization
• Link-based — Anyone with the link (for external collaborators)

All data is encrypted in transit and at rest. Session recordings can be deleted after a retention period.

Next Steps