Spend · Executive report

Executive report

The weekly or monthly rollup a leader asks for, assembled, never recomputed. Every number is the verbatim output of the same module its source tab reads. A number that differed from its source tab on the same window would be a defect, and a test asserts the equality.

Where to find it

  • Localhost: /exec-report.html?repo=<id> - a sub-tab of Telemetry (sidebar: Spend → Telemetry → Executive report)
  • API: GET /api/exec-report?cadence=weekly|monthly · GET /api/exec-report/artifact?name=<file>
  • Keyboard: ⌘ K then executive report

What is in the report

AI share of output.The tier-labeled share of merged work AI authored, straight from the AI share module: attested, co-authored, classified, and the explicit unattributed remainder.
Spend, and what it bought.Total spend, sessions, merged PRs attributed to agent sessions, and cost per merged PR, from the Spend-to-outcome join.
Prevented recurrences, in measured dollars.Dollars saved by prevented recurrences, priced from real per-session cost. Unpriced events stay counted, never estimated into a dollar figure.
Quality trend.Per-period quality bands over merged PRs, with the good share computed over graded PRs only. No graded PRs reads null, never a fabricated trend.

Cadence and delivery

  • Weekly and monthly. Both cadences ride the existing daily digest task: at most one stored artifact per cadence window, no separate cron, no separate mailer.
  • The digest carries it. The newest report's headline numbers (AI share, spend, prevented dollars, quality) append to the daily digest email, with a pointer to the full artifact.
  • Stored artifacts. Each report persists as a dated JSON artifact. The tab lists past reports; open any of them, download the viewed report as JSON, or print it.
  • First-run honesty. An empty install shows the schedule and what will fill in. Your first report generates the week you install; it never fabricates a number to look busy.

Read more