A public agency will ground an agent on citizen case files. Policy forbids using those files to tune a model. What must the build plan state?
Select an answer to reveal the explanation.
Short Explanation
You may look up the file, and you may not photocopy it into the clerk's memory. Your build plan has to say grounding on the citizen case files is allowed and tuning a model on those files is not. Keeping the files in-region does not make tuning acceptable.
Full Explanation
The agency's constraint separates two uses of the same files. Grounding lets the agent retrieve a case file at answer time. Tuning would change a model with those files, and policy forbids that. The build plan has to say grounding is allowed and tuning is not. Allowing tuning when the files stay in the same region confuses residency with purpose. A file can be stored in the right place and still be a forbidden training set under this policy. The plan should name the store, the allowed use, and the prohibited use where a reviewer can see all three. Turning off grounding as well as tuning forces the agent to answer with no case file, which throws away the use the agency did allow. Requiring tuning so the model memorizes each citizen file is the forbidden use stated as a prerequisite. Exam caveat: a later request for a custom model still has to satisfy this constraint. Stable labels do not override a ban on tuning with citizen data. Operational check: in the build plan, mark the case-file store as a grounding source, mark model tuning as prohibited for that store, and confirm the training pipeline has no path that reads it.