Skip to main content
The dispatch
Issue #9 2026-04-19 Sundays only

Where decision_log queries earn their keep.

Five SQL queries every operator runs in the first week — refund-rate-by-rollback, judge-floor-misses-by-channel, tier-A-conversion-uplift, and two more.

The decision_log is only as useful as the questions you ask it. This week, the five queries operators reach for in their first week — the ones that turn an append-only table into an operating dashboard.

The five

  • refund-rate-by-rollback — does reversing an action correlate with fewer refunds downstream?
  • judge-floor-misses-by-channel — which channel generates the most rejected proposals, and why?
  • tier-A-conversion-uplift — how much does verified-cost confidence improve action outcomes?
  • reversal-latency — how long between an action and its rollback, by agent?
  • evidence-recurrence — which evidence rows show up across the most decisions?

None of these are exotic. They're the questions a good operator already asks — the difference is that with an append-only log, the answers are queryable facts instead of reconstructed guesses.

// three links we sent

  • A gentle intro to window functions in Postgresaround the web
  • Supabase's docs on querying append-only tablessupabase.com
  • An essay on metrics that change behavioraround the web

// one ship

Saved queries: the first-week five now ship as templates

Run all five from the workspace without writing SQL.

See the changelog

// the dispatch

Get this Sunday's issue.

Subscribe and the next dispatch lands at 09:00 local this Sunday. Operator essay, three ecosystem links, ship of the week. That's it.

Sundays only · One-click unsubscribe · No tracking pixels