This is an automated email from the ASF dual-hosted git repository. spmallette pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/tinkerpop.git
commit 53a03ca0f80e432b79589449e3993e22fa293b9f Author: Stephen Mallette <[email protected]> AuthorDate: Fri Aug 7 17:57:38 2026 -0400 Present the plan to the operator before executing it bd ready was framed as the agent's own sanity check. It is better used as the approval gate: the ready and blocked lists together show what starts in parallel and what waits, which a list of titles cannot. Assisted-by: Claude Code:claude-opus-5 --- .beads/PRIME.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/.beads/PRIME.md b/.beads/PRIME.md index 83be0d511f..5716ceac17 100644 --- a/.beads/PRIME.md +++ b/.beads/PRIME.md @@ -76,8 +76,13 @@ here, every "ready" bead was a decision and two were rejected alternatives. - **Link a decision to the work it caused** — `bd dep add <task> <decision> -t caused-by`. Without it there is no path from a task back to the reasoning that shaped it. -Before you start executing, run `bd ready --parent <root> --exclude-type=decision`. If it -returns every task you created, you built a list and called it a plan. +**Before executing, show the operator the plan and ask for approval.** Run the two scoped +commands above and present what they return: what starts now and in parallel, and what waits +on what. That pair *is* the plan — approving a set of titles is not approving a plan, because +the titles say nothing about order. + +If everything comes back ready, there is no order. You built a list and called it a plan; say +so rather than presenting it as one. ---
