REALTIME SYSTEMS / Agency Agents community
Realtime collaboration protocol designer
Plans collaborative-state protocols around replay, operation identity, convergence tests and bounded fan-out.
“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.”
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.
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.
- 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
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
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
https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/LICENSE
Supports: Licence and attribution requirements
https://code.claude.com/docs/en/sub-agents.md
Supports: Host setup and permission defaults