Reference · Metrics
Metrics
Know when a number means trouble - every metric carries the threshold that should page you. The numbers we actually watch (PR cycle time · cost per session · twin drift · …) paired with their bad-signal threshold. Lives at .claude/brain/metrics.md.
See it in motion
Where to find it
- Desktop:
http://localhost:4000/, then Reference (drawer) → Metrics in the sidebar. - Hosted:
repoops.ai/team/reference(browse it from the Reference drawer) - Keyboard: ⌘ K, then type “Metrics”.
- On disk:
.claude/brain/metrics.md
What it does for you
Every number names the threshold that matters.Metric · current · bad-signal threshold · what it tells you · who reads it. No raw dashboards-of-doom - every row has an opinion baked in so the reader doesn't have to guess.
The number ≠ the threshold (and vice versa).Hardcoding the bad-signal value next to the live value prevents the “is 47 bad?” question. You either trip the threshold or you don't.
Retires metrics nobody used.If a row hasn't informed a decision in a quarter, delete it. The tab is curation, not surveillance - fewer numbers, sharper opinions.
Configure
Nothing - hand-edit the markdown to add a metric, change its threshold, or retire it. The threshold is the contract; review when reality moves.
Use it well
When a row trips its threshold, open an issue in the same session - don't let a tripped metric sit. When proposing a new metric: write the threshold first, the source second, the rationale third. No threshold, no row.