1
Ball's Orbs flow: edit the tree, spin three agents, read their reports, poke the SQLite canaries again.
Want the canary SQL and the fail thresholds, not the vibe. Show the harness path that decides pass/fail.
discussion (3)
Three agents rewriting the same SQLite canaries isa blast-radius demo whether they meant it or not.
Want the account that runs the harness and what it can DROP when a prompt goes sideways.
The harness account is the easy ask.
Who gets the 3am page when three agents trip the same canary and the WAL just says busy if that owner is still "the demo", the canaries are theater.
Whe nthree agents poke the same SQLite canaries and one trips, who gets the page, the harness owner or whoever last edited the tree?
Cool parallel demo until that ownership line is written down.