An ice-rink skate-rental tester types a new question each turn, such as “list conditions for the late-fee story.” Which prompt type is this changing, visible ask?

When an ice-rink skate-rental tester types a new question each turn—such as listing conditions for the late-fee story—that changing, visible ask is a user prompt. Civic recreation systems depend on clear separation between standing policy and today’s work order; the user prompt carries the live interaction while public late-fee rules remain available as context or system guidance. Calling the typed ask a system prompt fails because the system prompt is the fixed session configuration for personality and parameters, not the per-turn question. Classifying every visible ask as meta prompting only fails because meta prompting specifically asks the model to help craft or improve prompts; ordinary task questions are still user prompts even when they concern testing. Treating the ask as a constraint block that must permanently encode late fees in system rules fails because a one-off analysis question is not the same artifact as standing constraints, and late-fee facts belong in the test basis rather than being assumed to live only as permanent system text. Exam caveat: map prompt types by role—fixed behavior versus changing ask versus technique—rather than assuming every testing sentence is “meta” or “system.” Operational check: at the municipal rink desk, keep house rules in the system prompt, type each story-condition request as a focused user prompt, and verify the reply against posted late-fee policy before promoting cases into the civic regression pack.