A junior Team Coach on the school-district student-information ART asks what a prompt is when using the district's AI assistant. What is the most accurate explanation?
Select an answer to reveal the explanation.
Short Explanation
A prompt is just what you type and attach to steer the assistant—the job, the background, the limits. It is not a PI Objective, a legal hold, or a cheat code. Better instructions, better draft.
Full Explanation
A prompt is the instructions and context you provide that shape the model’s output. On the school-district student-information ART, that is the accurate explanation for a junior Team Coach learning the district’s AI assistant. It is not a SAFe PI Objective the model must implement without teams, not a legal records-retention hold that archives every student transcript in the model, and not a password that unlocks hidden SAFe exam answers. Confusing prompts with objectives, legal holds, or cheat codes mis-trains coaches and creates compliance risk around student data. Exam caveat: prompts can include examples and constraints, but they do not grant authority to bypass FERPA-aware district policy or team ownership of work. Operational check: have the Team Coach write a short prompt that states role, SIS ART context, and desired output; run it on an approved tool with nonsensitive sample text; and critique whether the instructions shaped the result as intended. Keep the civic mission visible when applying the technique so resident-facing outcomes stay the measure of success. In municipal ART practice, capture the rationale in facilitation notes so future coaches inherit the same standard. Re-validate after the next PI cadence event that the same control still fits current civic constraints.