A city-zoo membership script from an LLM says: open join page → tap Pay → then enter card → then tap Submit, attempting payment before a card exists. How should the tester classify and detect this?

A city-zoo membership script that says open join page → tap Pay → then enter card → then tap Submit—attempting payment before a card exists—should be classified as a reasoning error detected by logical validation of flow and cause-and-effect. Civic membership checkout must respect enabling order; paying with an absent card is broken causality. Calling it bias because only annual memberships appear fails when the defect is sequence, not skewed product mix. Calling it non-determinism because a second run might reorder steps fails as speculative and not the detection performed. Calling it successful because steps are grammatically clear fails fluency-as-correctness. Exam caveat: logical validation catches impossible orders even when prose is tidy. Operational check: walk enabling preconditions for zoo join/pay, reject pay-before-card flows, add order constraints to the prompt, and re-validate civic scripts before charging tests run in staging. Retain the municipal audit note so later testers can see why the decision protects public service quality and fairness. Retain the municipal audit note so later testers can see why the decision protects public service quality and fairness. Retain the municipal audit note so later testers can see why the decision protects public service quality and fairness.