Finance proposes placing all sealed juvenile-court ML feature stores in a public cloud region with no residency controls. What should the municipal AI infrastructure judgment be?

Requiring on-premises or tightly controlled hybrid placement for sealed juvenile-court ML feature stores is the correct municipal infrastructure judgment when finance proposes uncontrolled public-cloud placement. Regulated, sealed juvenile-related data demands residency, access control, and counsel-aligned placement—not convenience-driven public regions without controls. The correct answer works because infrastructure choice follows data sensitivity and legal constraints first. Requiring on-premises placement with shared agency access for regulated municipal data fails because broad shared agency access violates sealed confidentiality and need-to-know restrictions; on-premises location alone does not permit opening sealed juvenile-court features to other agencies. Requiring hybrid placement with cross-region replication for regulated municipal data fails because cross-region replication copies sealed juvenile-court features outside controlled residency boundaries rather than keeping them in on-premises or tightly controlled hybrid infrastructure. Requiring on-premises placement with extended feature retention for regulated municipal data fails because extended retention keeps sealed juvenile-court features beyond records and counsel-authorized limits, violating minimization and expungement obligations for sealed juvenile records. Exam caveat: "tightly controlled hybrid" still needs contractual residency, encryption, and audit—hybrid is not a free pass to public unmanaged regions. Operational check: classify the juvenile-court feature store under records/counsel rules, block uncontrolled public-region placement, document approved on-prem or controlled-hybrid controls, and reject on-premises proposals with shared agency access or extended feature retention and hybrid proposals with cross-region replication as non-answers.