{"resourceId":"pvsd-ai-approval-guidelines-2026","versions":[{"version":"external-37d88648be4784f7c9eefb88624ff0824fcddc3bfd84e2b2e8456101072f856a","resource":{"id":"pvsd-ai-approval-guidelines-2026","title":"Portola Valley connects AI approval to classroom expectations","organization":"Portola Valley School District","sector":"K–12 education","geography":"California, United States","publishedAt":"Spring 2026 page; guidelines marked adopted June 2026; exact day unknown","publicationDate":null,"eventDate":null,"sourceName":"Artificial Intelligence (AI) Guidelines","sourceLabel":"Official district guidance","sourceUrl":"https://www.pvsd.net/departments/technology/ai","evidenceClass":"standards-guidance","outcomeClass":"emerging","topics":["knowledge-work","data-security","governance-procurement","accessibility-workforce","operating-model"],"finding":"The district describes privacy, technical and curricular review before tool access, alongside assignment-specific AI permissions.","sledRelevance":"Interpretation: Newly archived background for fall implementation; adds an explicit intake-to-configuration workflow to prior district planning coverage.","evidence":"The page lists a typical 2–3 week review and Gemini staff approval as of June 2026. These are operator statements, not independently verified service levels or educational outcomes.","architectureImplications":"Interpretation: Separate approved staff access from assignment-level student permissions. Validate identity and learning-platform settings; no hosting topology or compute benchmark is supplied.","governanceImplications":"Interpretation: A permission rubric needs consistent classroom communication and an appeal path; perceived AI writing patterns should not alone establish misconduct.","securityPrivacyImplications":"Interpretation: Verify actual retention, secondary use and access controls; a privacy agreement does not itself demonstrate technical enforcement.","caveats":"Undated updates may lag operations. Community perceptions are not measured benefits; response selection and the middle-school denominator are unclear. No causal learning, workload or security evaluation.","streamIds":["k12"],"roles":{"sales":"Interpretation: Curriculum, technology and procurement leaders need a predictable path from teacher request to permitted classroom use. Ask where requests stall, which approval applies to which users, and how families learn the rules. A bounded engagement could map one proposed staff workflow through intake, configuration and classroom communication. The value hypothesis is fewer unresolved decisions and clearer ownership. Do not promise the district's stated turnaround elsewhere or treat listed approval as product endorsement.","engineering":"Interpretation: Prototype an approval record linking intended task, user group, data inventory, agreement and tested configuration. Prerequisites are local policy and access to supplier settings. Test staff and student accounts separately using synthetic information, including denial and withdrawal scenarios. Proposed proof of value requires every pilot account to match the approved access scope and every exception to have an owner. The public page cannot establish how current product defaults or integrations behave.","delivery":"Interpretation: The curriculum lead should own classroom expectations with IT operating access and privacy staff reviewing data decisions. Train teachers using realistic assignments and provide accessible family explanations. Dependencies include a supported tool configuration and time for requests. Proposed acceptance: sampled pilot assignments show an explicit permission level, users can explain it, and a withdrawn approval disables access in a rehearsal. Risks include inconsistent enforcement, outdated approvals and unsupported misconduct allegations."},"retrievedAt":"2026-09-14T03:01:24Z","enrichedAt":"2026-09-14T03:04:02Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Interpretation: Test comprehension of permissions with multilingual families and learners needing accommodations.","procurementImplications":"Interpretation: Budget review time and demand configuration-specific evidence before licensing.","operatingModelImplications":"Interpretation: Give curriculum and technology owners a shared decision record and review date.","updateExplanation":"New canonical URL, absent from all 274 archive records retrieved at offsets 0, 100 and 200; related K12 coverage reviewed. Older background, not September 13 breaking news.","sourceVerification":{"openedUrl":"https://www.pvsd.net/departments/technology/ai","referenceExcerpt":"Every AI application must pass a formal review before reaching students or staff.","promptVersion":"sled-research-v3.2","model":null,"basis":"agent-reported inspection"}}}]}