Decisions
The choices made, who made them, and why.
The Decisions stream captures the choices made, who made them, and the rationale, so a decision is never lost, never anonymous, and never un-auditable.
What it captures
A Decision is a durable record with an owner: what was decided, by which person or Runner, at what time, under which policy, and why. Approving a loan against a soft exception, filing a SAR, setting a Runner's autonomy slider, overriding an Ask gate, each of these is a Decision, and each names a responsible person rather than "the system" or "Compliance." A requirement without a name is a department talking; a Decision without an owner is the same problem one layer down.
Why it matters
Decisions are where accountability and the Compounding Loop meet. For the loop, past choices become priors: the next similar case sees how the last one was handled and why. For the operator, it ends the archaeology of reconstructing who decided what from email and memory.
In the exam
Every consequential action in Runline passes an Allow / Ask / Block gate, and every gate outcome is a Decision on the record, append-only, timestamped, and tied to the key and the actor. "Who approved this, and on what basis" is a query, not a scramble. Human oversight stops being a policy claim and becomes a queryable stream.