You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've spent the last week firefighting AI-spend incidents (token bleed from paused repos still spending, repeat-spend on unchanged PRs, silent misrouting to a billed provider instead of the free local one). Every one of those was only caught by hand-querying audit_events live in production. We have no durable, always-on way to see — and show the community — how the review engine is actually performing over time.
This epic is about turning gittensory's own operational behavior into three honest, trackable, public metrics: how fast we review, how accurate our decisions are, and how efficiently we avoid redundant work. Not a benchmark of the underlying LLMs (that's not something we're building), and not raw GPU hardware health (the host is rented infrastructure, not our product) — this is about the engine's own competence.
#4367 (open, assigned) already covers GPU exporter + Grafana + a new gittensory_ai_provider_request_duration_seconds histogram for raw AI-provider call latency. That's internal ops observability; this epic's speed sub-issue is a different, public, end-to-end metric (webhook received → comment posted) and should reuse/reference that histogram where useful rather than duplicate it.
#110 (closed) shipped reviewVelocityPerDay — a queue-throughput/PR-resolution-rate trend, not a per-review latency measurement. Different metric, cited for context only.
#4261/#2352 track the miner's own self-review calibration (a different subsystem, packages/gittensory-engine/src/phase7-calibration-loop.ts) — not the maintainer-facing review engine this epic is about.
Three durable, historical, publicly-visible metrics — review speed, review accuracy, and resource efficiency — each backed by a real rollup table (not a live-computed snapshot), each shown on the public stats page/homepage with a trend, and each documented honestly enough that the methodology itself could be published.
Motivation
We've spent the last week firefighting AI-spend incidents (token bleed from paused repos still spending, repeat-spend on unchanged PRs, silent misrouting to a billed provider instead of the free local one). Every one of those was only caught by hand-querying
audit_eventslive in production. We have no durable, always-on way to see — and show the community — how the review engine is actually performing over time.This epic is about turning gittensory's own operational behavior into three honest, trackable, public metrics: how fast we review, how accurate our decisions are, and how efficiently we avoid redundant work. Not a benchmark of the underlying LLMs (that's not something we're building), and not raw GPU hardware health (the host is rented infrastructure, not our product) — this is about the engine's own competence.
Non-goals (explicit)
What already exists (don't rebuild)
computeGateEval(src/review/parity.ts:88-169) joins every gate decision to its realizedpr_outcome, reversal-discounted viarecordReversalSignals(src/review/outcomes-wire.ts:402-471), already live on the homepage as "Decision accuracy %" (feat(stats): public proof-of-power — lifetime PRs-handled + accuracy counter on homepage hero #1059, feat(review): persist every AI review for accuracy-over-time tracking #1567, both shipped). This epic's accuracy sub-issue extends this into a tracked-over-time trend — it does not rebuild the underlying computation.#4367(open, assigned) already covers GPU exporter + Grafana + a newgittensory_ai_provider_request_duration_secondshistogram for raw AI-provider call latency. That's internal ops observability; this epic's speed sub-issue is a different, public, end-to-end metric (webhook received → comment posted) and should reuse/reference that histogram where useful rather than duplicate it.#110(closed) shippedreviewVelocityPerDay— a queue-throughput/PR-resolution-rate trend, not a per-review latency measurement. Different metric, cited for context only.#4261/#2352track the miner's own self-review calibration (a different subsystem,packages/gittensory-engine/src/phase7-calibration-loop.ts) — not the maintainer-facing review engine this epic is about.Sub-issues (priority order)
computeGateEval/pr_outcomeinfrastructure.Expected outcome
Three durable, historical, publicly-visible metrics — review speed, review accuracy, and resource efficiency — each backed by a real rollup table (not a live-computed snapshot), each shown on the public stats page/homepage with a trend, and each documented honestly enough that the methodology itself could be published.
Effort
Epic — 3 independently shippable sub-issues.