Leadership mandates one public generative tool for every facilitation artifact on the library consortium digital-services ART, including work that touches patron-record integrations under retention law. What should the RTE advocate?
Select an answer to reveal the explanation.
Short Explanation
A public catalog card is not a patron's borrowing history. One mandatory AI hose for every library artifact will spray regulated data into the wrong tank. Responsible use needs an off-ramp for sensitive paths.
Full Explanation
Uniform tooling is useful until it collides with privacy, retention, or licensing constraints. Patron-record integrations are regulated workloads; a public model is often an unacceptable destination for that content. The RTE advocates a documented exception so teams can complete facilitation and delivery without pasting restricted data. A vendor privacy page does not replace consortium legal review or municipal policy.