Work Streams
Work Units rolled up to the initiatives they advance — what each stream costs, who carries it, and where it's blocked. The aggregation layer between a single unit of work and the roadmap.
Corey Ricelast activity 12m ago3$12.4k4,820186
OR
54%31%15%claude-sonnet-4.5Deflection rate up 6pts since the retrieval fix shipped. Next milestone is auto-resolving refund requests end to end.
Omer Goldberglast activity 3m ago3$18.9k1,240142
48%44%8%gpt-5-codexToken yield is leaking on long debugging sessions — $2.1k/mo of retries with no shipped diff. Fix is in review.
68%32%claude-opus-4.5Throughput is strong but the initiative is blocked on Legal approving the redline templates before we can auto-apply them.
Mike Stonelast activity 27m ago2$4.4k1,9808852%28%20%gpt-5Follow-up drafting is the highest-volume, lowest-cost stream. Nearly ready to ship CRM auto-logging.
Where streams collide — and feed each other
3 projects · 6 people · 2 agents · today
CoreyOROritOmerSupport's escalation triage and Legal's contract review both touch refund logic — context is already shared.
Two teams maintain overlapping prompt templates for billing intents; consolidate to one.
MikeCoreyPaoloSales follow-up drafting reuses Support's resolved-ticket summaries as enrichment.
CRM write-back permissions block both streams from closing the loop.
OmerOROritYonatanPR review and redline drafting both wait on the same template sign-off from Legal.
Inferred from work-memory file evidence. A collision is rarely a problem — it's where coordination already happened, or where one person's context can enrich another's work.
