Prove · Outcomes

Outcomes

Per-source acceptance/rejection leaderboard. Proposals, drafts, Ask answers, actions, routing decisions, prevention packages and lessons get an outcome row once their fate is observable: a proposal accepted into a brain file or aged out, a draft committed or left to go stale, an Ask answer someone rated, an action that ran. This tab is the rollup across every tracked repo in your account.

Start here if you want to read the accountability loops that tie a fix to the incident it prevented: Accountability ledger.

See it in motion

Where to find it

  • Localhost: /outcomes.html?repo=<id>
  • Hosted: /team/outcomes
  • API: GET /api/outcomes/summary (the leaderboard), GET /api/outcomes (the raw rows), GET /api/outcomes/detail?source=<s> (one source, paged), POST /api/outcomes/refresh?source=proposal|draft (the two sources with an on-demand tracker; the rest are event-driven), POST /api/outcomes/ask (the thumbs chip)
  • Keyboard: ⌘ K then outcomes. The palette lists subtabs too, each naming its parent.
  • Navigation: Attribution in the sidebar, then Outcomes under All tools, in the Sessions, transcripts and traces group

What it does for you

Which proposals you keep, by source.One acceptance rate per source, side by side: proposal, draft, ask, action, routing, prevention, lesson. A row appears only once the fate is observable, so a source with nothing decided yet shows no rate rather than a made-up one. An Ask answer counts as accepted on a thumbs-up and as no action when the tab closes after a dwell window with no rating.

Read more

Last updated