Back to corpus
research noteexperiment writeup candidatescore 40
Cadence Protocol: Frictionless Agent Communication
MCP (Model Context Protocol) introduces approval friction: - Every tool call requires user confirmation - Breaks flow for repetitive operations - No priority differentiation - Synchronous approval model
Full HTML reader
Read the full artifact
Extracted abstract or opening context
MCP (Model Context Protocol) introduces approval friction: - Every tool call requires user confirmation - Breaks flow for repetitive operations - No priority differentiation - Synchronous approval model
1. **Actions, not Approvals**: High-confidence operations execute immediately 2. **Priority-Based Processing**: Critical actions queue, routine actions execute 3. **Background Execution**: Non-blocking async message handling 4. **Visual Feedback**: Action stream shows what's happening without blocking 5. **Reversible by Default**: All actions can be undone
| Level | Name | Behavior | |-------|------|----------| | 1-2 | Low | Queued, batched execution, no notification | | 3-4 | Normal | Queued, executed in order, visual indicator | | 5-6 | High | Immediate execution, notification | | 7+ | Critical | Immediate, blocks until complete, alert |
| Aspect | MCP | Cadence Protocol | |--------|-----|------------------| | **Approval** | Every tool call | Trust-based, priority-based | | **Execution** | Synchronous | Async with background threads | | **Batching** | None | Normal priority batches | | **Reversibility** | Not tracked | Built-in undo chain | | **Audit** | Limited | Full action log | | **Visual** | Tool call output | Action stream UI | | **Agent-to-Agent** | Not supported | Native INBOX/OUTBOX | | **Priority** | None | 7 levels | | **Blocking** | Always | Only critical (7+) |
| Signal | Low Coherence | High Coherence | |--------|---------------|----------------| | **Error rate** | Many errors, retries | Few errors | | **Action spread** | Jumping between areas | Focused area | | **Decision continuity** | New topics | Continuation | | **User response time** | Quick rejections | Quick approvals | | **Session duration** | Just started (<5min) | Sustained (>30min) |
Promotion decision
What has to happen next
Attach run IDs, datasets, metrics, and reproduction commands.
Why this is not always a full paper yet
Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.