OPERATIONS
Cadence
Surfaces coordination debt before it becomes ops pain.
Backlog velocity, knowledge drift, tool overlap, integration gaps, meeting density, focus-time fragmentation.
Why Cadence exists
Ops is the work that happens between the work. Sprint planning, knowledge-base hygiene, tool-stack rationalization. Cadence watches the operational pulse and surfaces drift before it becomes pain.
Routines
What Cadence does every cycle.
Backlog velocity
Net throughput (acted - new), staleness %. Flags backlog growing 2x faster than acted-on.
Knowledge drift (Phase 2)
Doc freshness, last-edited recency, orphan pages. Requires Notion.
Tool overlap
Two tools doing the same job means context switches. Flags overlap even when both look individually healthy.
Integration gaps
Missing connections the agents need. Capped at 1 nudge per integration per 30 days.
Meeting density (Phase 2)
Meeting load + focus-block ratio. Requires Google/Microsoft Calendar.
DATA SOURCES
- →Eidros opportunities + findings tables
- →connections table
- →mirror_events (meeting density, focus-time)
- →Linear / Notion / Calendar (Phase 2)
MODEL USE
MODELS.classify (Haiku) for triage · MODELS.generate (Sonnet) for synthesis findings
WHAT IT EMITS
- →Backlog health findings
- →Tool overlap + integration-gap findings
- →Knowledge drift findings (Phase 2)
The rest of the team