{"resourceId":"smfcsd-ai-working-group-2026","versions":[{"version":"external-dc786f57d91cf230cd657dd0615b9319314155ccde94b0f921d5b791da6444c8","resource":{"id":"smfcsd-ai-working-group-2026","title":"San Mateo-Foster City sequences community input, policy and staff learning","organization":"San Mateo-Foster City School District","sector":"K–12 school district","geography":"California, United States","publishedAt":"Undated live page; 2026 planning timeline","publicationDate":null,"eventDate":null,"sourceName":"AI Working Group","sourceLabel":"Official district planning guidance","sourceUrl":"https://www.smfcsd.net/community/ai-working-group","evidenceClass":"standards-guidance","outcomeClass":"emerging","topics":["knowledge-work","governance-procurement","data-security","accessibility-workforce","operating-model"],"finding":"The district describes a 26-member community group and schedules policy drafting for September–November, with implementation and professional learning in late 2026 and beyond.","sledRelevance":"Interpretation: Newly archived example of a fall district governance process; planned steps should be verified before treating policy as operational.","evidence":"Official timeline and membership description; planned community meetings in September. No comparison group, measured learning effects or workload baseline.","architectureImplications":"Interpretation: translate approved uses into identity and application controls after policy decisions. The page specifies no hosting architecture or autonomous-agent deployment.","governanceImplications":"Interpretation: connect community recommendations to a documented decision, owner and review date.","securityPrivacyImplications":"Interpretation: turn privacy principles into supplier-specific data-flow, retention and access checks before learner use.","caveats":"District self-description; future milestones are not completed outcomes. Exact publication day and meeting dates are unknown; linked presentations were not used as evidence.","streamIds":["k12"],"roles":{"sales":"Interpretation: District leadership may need help turning community expectations into practical staff guidance. Ask how recommendations become decisions, how students and families can challenge them, and what educators need before implementation. A bounded engagement could map one proposed use through policy, supplier review and classroom communication. The value hypothesis is fewer unresolved responsibilities at launch. The planning page cannot demonstrate improved learning or trust, and it establishes no buying intent. Validate whether a similar process fits the customer's governance calendar and capacity before proposing work.","engineering":"Interpretation: Start with a policy-to-control map for one proposed staff assistant and one learner activity. Prerequisites are explicit intended uses, user groups and supplier data documentation. Check whether existing district identity systems can enforce differentiated access, and whether logs expose unnecessary student information. A proposed proof of value should walk permitted and prohibited scenarios through tool approval, classroom use and incident escalation. Keep production student records out of demonstrations. Cloud, local or hybrid selection needs separate requirements; the planning timeline supplies no capacity benchmark or validated integration design.","delivery":"Interpretation: The district education lead should own the transition from recommendations to practice, supported by principals, procurement and privacy staff. Dependencies include an approved policy, accessible communication and teacher release time. Train staff using classroom scenarios, then gather family and student feedback through channels they can use. Proposed acceptance: each selected use has an accountable owner, documented supplier review and tested support route before access expands. Record a dated decision on unresolved concerns. These are proposed criteria, not claims about district completion. Risks include consultation without follow-through and training arriving after tools are already in use."},"retrievedAt":"2026-09-08T03:01:24Z","enrichedAt":"2026-09-08T03:01:51Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Interpretation: provide accessible, multilingual consultation and educator practice time, with non-AI routes.","procurementImplications":"Interpretation: convert tool-evaluation guidance into supplier evidence requirements; no tender or purchase intent is established.","operatingModelImplications":"Interpretation: education leadership owns intended use; IT, procurement and privacy owners implement the resulting controls.","updateExplanation":"Not an archive repeat: absent from all 20 K12 records and the full-library candidate search. Newly added context for fall 2026 decisions; not represented as new September 7 publication.","sourceVerification":{"openedUrl":"https://www.smfcsd.net/community/ai-working-group","referenceExcerpt":"Draft policy development and refinement of recommendations to support responsible AI use across the district.","promptVersion":"sled-research-v3.1","model":null,"basis":"agent-reported inspection"}}}]}