A courts clerk turns off grounding to municipal files and then sees more generic legal-sounding text without city policy citations. What does this illustrate?
Select an answer to reveal the explanation.
Short Explanation
Pull the city policy binders off Copilot's desk and the answers get fuzzy and generic—no surprise. Less grounding context means weaker ties to the municipality's real documents.
Full Explanation
Changing or reducing available context changes response quality and grounding. A courts clerk who turns off grounding to municipal files and then sees more generic legal-sounding text without city policy citations is illustrating that Copilot's answers track the evidence it can use. Remove the city policy files from the grounding set and citations to those policies naturally degrade or disappear, replaced by broader, less local language.
Disabling file grounding always improving citation quality fails because the observed outcome is the opposite: fewer city policy citations, not better ones. Generic text meaning permanent loss of all Microsoft 365 apps fails by overgeneralizing a grounding setting into a catastrophic, permanent app lockout. City policy citations appearing only when the web is the sole allowed source fails because municipal policy citations come from the city's own files and knowledge—not from making the web the only source.
Exam caveat: Generic legal-sounding prose is especially dangerous in a courts or city-attorney context because it can sound authoritative while missing local procedure. AB-730 expects recognition that grounding controls quality, not that generic text is "good enough" for municipal legal work.
Operational check: For policy-dependent answers, keep grounding to approved municipal files enabled, require clerks to confirm that cited policies match the current SharePoint versions, and reject responses that lack local citations when city procedure is required.