---
title: "Realtime collaboration protocol designer: review, role & definition · Undominated.ai"
canonical: https://undominated.ai/agents/agency-engineering-realtime-collaboration-engineer/
description: "Plans collaborative-state protocols around replay, operation identity, convergence tests and bounded fan-out."
---

# Realtime collaboration protocol designer: review, role & definition · Undominated.ai

> Plans collaborative-state protocols around replay, operation identity, convergence tests and bounded fan-out.

[← Explore all agents](/agents/)

REALTIME SYSTEMS / Agency Agents community

# Realtime collaboration protocol designer

Plans collaborative-state protocols around replay, operation identity, convergence tests and bounded fan-out.

 [Use this definition ↓](#setup)[Original source ↗](https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/engineering/engineering-realtime-collaboration-engineer.md)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 3 linked sources
 Publisher Agency Agents community
 Licence [MIT ↗](https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/LICENSE)
 Revision bd956db032d9
 [Read what was—and wasn’t—checked ↓](#review)

“Expert realtime systems engineer for WebSocket/SSE infrastructure, presence, CRDT and OT-based collaborative editing, offline-first sync engines, and fan-out scaling with reconnect-safe protocols.”

 [Agency Agents community · upstream description ↗](https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/engineering/engineering-realtime-collaboration-engineer.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - It separates ephemeral presence TTLs from durable document operations and explicitly rejects unbounded slow-consumer queues.
- The illustrative receiver ignores replayed sequence values and reconnects on gaps instead of advancing a discontinuous cursor.
- It requires a resume cursor before the happy-path connect, and it keeps presence on a TTL channel separate from the durable document log.
- Convergence claims are tied to hostile-network tests, not to a localhost demo.

### A good fit for

 - Provide document/state types, offline requirements, authorization boundaries, expected room sizes and current transport/storage.
- Receive a consistency contract, replay/presence architecture and adversarial-network/load-test scenarios.
- Designing reconnect, idempotent operations, and a per-type CRDT or last-writer-wins choice.
- Rejecting a plan that stores cursors in the same log as document operations.

### Weigh up before choosing

 - The snippets omit application-owned durable queue, operation application and authentication helpers; there is no complete sync engine here.
- Exactly-once effects require durable deduplication, crash recovery and tested concurrency; the example metrics are goals, not demonstrated guarantees.
- A single-writer room is an architectural choice, not a requirement for every CRDT; validate failover and snapshot/log consistency.
- Adapt the display name and color to supported Claude Code frontmatter in a working copy; original source bytes are preserved.
- Source-only listing: inspect the upstream context and referenced dependencies before adapting this definition.
- The file describes socket tests. It does not open a socket, run a latency harness, or choose a library version.
- No tools field is set, so the inherit-all host rule applies on install. The prompt does not revoke network tools.
- It does not guarantee convergence of an existing product. That would require the tests the file names.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - engineering/engineering-realtime-collaboration-engineer.md (complete definition)
- LICENSE (applicable redistribution terms)
- Host custom-agent documentation; repository installation guidance where applicable

### Our findings

 - It separates ephemeral presence TTLs from durable document operations and explicitly rejects unbounded slow-consumer queues.
- The illustrative receiver ignores replayed sequence values and reconnects on gaps instead of advancing a discontinuous cursor.
- The first rule is to design resume from the last acknowledged sequence before designing the initial connect.
- Presence expires and is not mixed with durable document operations. Backpressure is required so a slow client cannot grow server memory without bound.
- The test rule says to kill sockets and add latency. The file does not perform those tests.

### Not established by this review

 - No agent was installed or invoked. Host/model compatibility, task accuracy and runtime behaviour were not tested.
- The resource was not executed and its tools were not called.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Use the role in your project.

[Upstream setup instructions ↗](https://code.claude.com/docs/en/sub-agents.md)
 - Read the pinned definition and MIT licence; review the host permissions before use.
- Read the full definition as a role reference; create a host-valid .claude/agents/ working copy and bound tools to the agreed task.
- Provide document/state types, offline requirements, authorization boundaries, expected room sizes and current transport/storage.

### Before you start

 - A compatible agent host/model
- Project inputs and separately installed/authorized toolchains or services

### Compatibility

Claude Code

### Implementation

Markdown

### Host-mediated repository and tool access

 - No tool allowlist is declared; the orchestrating host must explicitly bound file, shell and network permissions.

### Cost model

The definition is reusable under its stated licence. Host/model usage, execution environments and connected services can incur separate charges.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Complete upstream definition at reviewed commit ↗](https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/engineering/engineering-realtime-collaboration-engineer.md) Checked 2026-10-14 https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/engineering/engineering-realtime-collaboration-engineer.md Supports: Workflow, inputs and outputs, Declared tools and constraints, Selection and limitations
- [Applicable upstream redistribution licence ↗](https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/LICENSE) Checked 2026-10-14 https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/LICENSE Supports: Licence and attribution requirements
- [Host custom-agent configuration ↗](https://code.claude.com/docs/en/sub-agents.md) Checked 2026-10-14 https://code.claude.com/docs/en/sub-agents.md Supports: Host setup and permission defaults

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Find reusable instructions](/skills/)
- [Inspect connections](/mcp-servers/)
- [Build a toolkit](/tools/)
- [Choose the model](/compare/)
