Update
Batch approval for scheduled tasks — one review, every write
TL;DR
A scheduled audit that finds thirty things to fix used to mean thirty separate approvals. Batch approval collapses that into a single review — while keeping the guarantee that matters: each write still applies against freshly-read account state, and a money write whose preview basis has gone stale is not quietly applied on old numbers.
What shipped
- One review covering every write a scheduled task proposes, instead of per-change approval.
- A preview-basis age bound on money writes — if the data a budget or bid change was calculated from is too old, it does not silently apply.
- A true preview-basis read for batch money writes, so the number you approved is the number that was checked.
- Chain-group UI so related changes are reviewed together rather than as disconnected items.
Why it matters
Approval fatigue is how governance quietly dies: if reviewing is tedious enough, people start approving without reading, and the gate becomes theatre. Batching makes the review practical without removing the check — which is the whole point of having it.
Frequently asked questions
- Does batch approval mean changes apply automatically?
- No. It changes how many times you click, not whether a human reviews. Every write still requires explicit approval, and each one is validated against fresh account state before it applies.
- What stops a batch-approved change from applying on stale data?
- Money writes carry an age bound on the data they were calculated from. If that basis is too old at apply time, the change does not go through silently.