Pick an option on each card and press Done; your answer goes straight
back to the session. The raiser's pick is marked. "I'm not sure" and "Take it to the engineering bridge" are real answers.
1
In plain terms. Should we turn on the faster safety check that runs before every push? It is built and rehearsed; switching it on is one command a person runs, with a one-command undo.
The full question, as raised
Switch on the faster pre-push safety check on the Mac mini? All its code is merged (agent-harness #1908, #1910, #1911, #1912, #1914, #1915, #1916; agentflow-relay #489, #490) and rehearsed on copies against main 7045100b0. ADR-0069 section 6 reserves the one-command load, which also points the live guard-bash hook at it, for a person. Exact load and undo commands, plus the rehearsal results: https://docs.propflowai.co/a/row-fence-load-step-2026-11.html
Why, and what was tried
The session raising this recommends: Turn it on now, with the one-command undo ready Each check drops from 2-5.7s (often over its 5.5s limit) to 0.3-1.3s; it fails closed if the helper is down, and undo is one command Tried first, unsuccessfully: Not a question for the decider: fable-decide fd0bcfac7 already ruled to build it and that loading stays a human act (ADR-0069 section 6).
220300f9 is parked on this.
2
In plain terms. Can I remove three finish-line items that point at pull requests we closed and split into smaller ones? The work is all merged under the new pull requests; the old items can never tick.
The full question, as raised
Clear three finish-list checks that can never pass on task send-door-registry-derived? They name PRs that were closed and split after three review rounds: agent-harness #1909 (replaced by #1911 + #1912, both merged) and propflowai #25038 merged/live (replaced by #25048, #25059, #25062, all merged; each replacement is already its own check). Shrinking the finish list is the human door: run once drive --replace "<the same criterion>" and the Driver re-arms the list without those three items. Board: https://docs.propflowai.co/a/send-door-registry-derived.html
Why, and what was tried
The session raising this recommends: Yes, drop the three dead checks The work they named shipped under the replacement PRs, which are already checked; keeping them blocks DONE forever Tried first, unsuccessfully: Not a decider question: shrinking an acceptance list is reserved for a human (driver-here refuses it; only drive --replace may re-baseline).