The grounds requirement is documented after the steps that need it, so a reader following the surface page in order meets the refusal before the explanation. The page presents creation and planning as a sequence and states the grounds requirement further down, among the interview steps. An agent working through it in order therefore runs the plan verb, is refused for missing grounds, and only then reaches the passage that would have told it why and how. The cost is small per encounter and it recurs for every reader who trusts the order of the page, which is every reader following it for the first time. The fix is ordering rather than content: state the requirement where the step that enforces it is described.

The grounds requirement is documented after the steps that need it, so a reader following the surface page in order meets the refusal before the explanation. The page presents creation and planning as a sequence and states the grounds requirement further down, among the interview steps. An agent working through it in order therefore runs the plan verb, is refused for missing grounds, and only then reaches the passage that would have told it why and how. The cost is small per encounter and it recurs for every reader who trusts the order of the page, which is every reader following it for the first time. The fix is ordering rather than content: state the requirement where the step that enforces it is described.

Grounds

• pursued: a reader following commands/intent.md in order meets no grounds refusal; shown wrong if intent plan or ready refuses a missing grounds entry again