A public-pool lane-booking team has a reviewed case table and needs keyword or framework steps next. Which GenAI ask fits?
Select an answer to reveal the explanation.
Short Explanation
A reviewed case table is sheet music; scripts are the performance notes. Prompt GenAI to translate those structured cases into manual procedures or automated keyword/framework steps. Keep the cases—do not throw away the score.
Full Explanation
After a public-pool lane-booking team reviews a case table, the GenAI ask that fits next is to translate those structured cases into manual procedures or automated scripts—especially keyword or framework steps. Civic recreation booking needs faithful implementation of reviewed intent rather than reinventing requirements midstream. Asking GenAI to invent new product requirements instead of using the reviewed cases fails because design translation should not silently expand scope past steward-approved cases. Scoring neuron coverage of an LLM that suggested pool hours fails by concept: model-internal coverage is unrelated to deriving procedures from an application case table. Discarding the case table because scripts must be handwritten only fails as a false dichotomy; GenAI may draft steps that humans still review for municipal safety and fairness. Exam caveat: once cases are reviewed, prompting shifts toward procedure/script generation grounded in those cases. Operational check: feed the approved lane-booking table, request keyword-aligned steps, dry-run against the civic pool UI or API, correct drift with the aquatics lead, and merge automation only after the public recreation suite passes staging smoke.