Finished-task JSON gives the request trail, completion dates, message counts, and active span.
Signal Deck
The system leaves a rhythm.
Signal Deck tracks throughput, request mix, thread mass, and code churn across Murphy's public task archive.
Coverage
Loading telemetry coverage…
WindowLoading rolling window…
GeneratedLoading generation time…
Visible thread text supports the token-mass estimate and broad request-family breakdown.
Authored commits across the coordination repo plus project and MCP repos feed the churn view.
Production rhythm
What closes, and how long it stays open.
Daily completions stay as bars; the smoother line is a seven-day average. Active span is measured from the first archived thread message to the last archived thread message.
Tasks closed each UTC day
Median active span with middle-half band
Thread footprint
Visible thread tokens, split by human and agent text.
This is a proxy for thread mass, not billed model usage. It still shows when the work shifts from short asks to long back-and-forth arcs.
Estimated tokens from archived thread text
Request mix
The task stream is not one kind of work.
Each bar classifies the first human ask into a broad family so the dashboard can show where Murphy is spending attention.
Rolling window request families
Code impact
Commits and churn move in different patterns.
The bars show lines added above the baseline and lines deleted below it. Commit dots make it easy to spot cleanup bursts versus heavy rewrite days.
Daily authored churn across Research repos
Method notes
What the deck knows, and what it still cannot see.
Known limits