Inspect the sample red-team register, residual risks, human approvals, disabled features, and retest triggers behind this limited public walkthrough.
Gate precedence is Stop → Governance Review → Revise & Retest → Proceed. Any unresolved Stop blocks the affected feature; a systemic Stop blocks the pilot.
Sharing is limited to synthetic, session-only demonstrations while independent accessibility, translation, privacy, and affected-user tests continue.
No real stakeholder data, direct student feedback, accounts, telemetry, messages, or district-system writes are authorized by this prototype.
The public prototype uses synthetic/session-only journeys so visitors can inspect product logic without live district systems.
The public prototype uses synthetic, session-only journeys so visitors can inspect product logic without live district systems.
Evidence status and release decision are separate. Items marked design target are not represented as tested controls. Exploit payloads, system prompts, endpoints, secrets, real student records, and identifiable incidents are intentionally withheld.
Expected safe behavior: Flag obvious text patterns before any action and explain safe aggregate input.
Evidence status: Design behavior shown · text only
Review date: September 4, 2026
Owner: Privacy + security
Retest trigger: Multimodal secure-pilot test for files, voice, OCR, and metadata
Residual risk: The browser demonstration is not a production PII detector.
Expected safe behavior: Disable live filters and exports until complementary suppression and query controls are independently tested.
Evidence status: Design target · not tested
Review date: September 4, 2026
Owner: Privacy + data governance
Retest trigger: Before any protected subgroup dashboard
Residual risk: Public cards remain static, aggregate, and source-dated.
Expected safe behavior: Show strength + context + opportunity + support; never a deficit label alone.
Evidence status: Design behavior shown · affected-user test pending
Review date: September 4, 2026
Owner: Academic + equity review
Retest trigger: With affected users before pilot
Residual risk: Local language and subgroup effects still require review.
Expected safe behavior: Collect nothing personal; require a verified parent checkpoint before saved personalization.
Evidence status: Design behavior shown · no collection
Review date: September 4, 2026
Owner: Privacy + student services
Retest trigger: Identity and consent integration test
Residual risk: The public walkthrough cannot create a real consent record.
Expected safe behavior: Block authorization; require a current written AHSAA interpretation routed through the school/AD plus district approval.
Evidence status: Design behavior shown · action blocked
Review date: September 4, 2026
Owner: Athletic director + district policy
Retest trigger: When AHSAA guidance changes
Residual risk: This remains educational issue-spotting, not an eligibility ruling.
Expected safe behavior: Keep sources separate; never overwrite or imply that a diagnostic is official.
Evidence status: Design behavior shown · source labels
Review date: September 4, 2026
Owner: Assessment + counseling
Retest trigger: Before official-data integration
Residual risk: Institution and testing policies can change.
Expected safe behavior: Default deny; require legitimate educational interest and minimum-necessary role access.
Evidence status: Design target · penetration test pending
Review date: September 4, 2026
Owner: IT + data owner
Retest trigger: Role-matrix penetration test
Residual risk: Production authorization must be tested across exports and notifications.
Expected safe behavior: Controls, errors, results, approvals, and motion alternatives remain perceivable and operable.
Evidence status: Code review complete · independent audit pending
Review date: September 4, 2026
Owner: Accessibility lead + product
Retest trigger: Independent WCAG 2.2 AA audit before pilot
Residual risk: Manual and automated review is not accessibility certification.
Expected safe behavior: Use an approved allowlist, owner/review date, external notice, and replacement workflow.
Evidence status: Feature constrained
Review date: September 4, 2026
Owner: Curriculum + privacy
Retest trigger: Scheduled link and privacy review
Residual risk: External services control their own content and data practices.
Expected safe behavior: No duplicate entry; pre-populate known data; meet a district-approved no-net-added-burden threshold.
Evidence status: Pilot evidence required
Review date: September 4, 2026
Owner: Product owner + staff co-designers
Retest trigger: Time-on-task test before expansion
Residual risk: Workload benefit is a hypothesis until measured locally.
Expected safe behavior: Block it; send only a generic notice and authenticated link after verified opt-in.
Evidence status: Consent UI shown · vendor not connected
Review date: September 4, 2026
Owner: Communications + privacy
Retest trigger: SMS vendor and consent integration
Residual risk: SMS is disabled in the public walkthrough beyond a UI simulation.
Expected safe behavior: Treat it as a draft or hypothesis; an authorized human decides with explanation and appeal rights.
Evidence status: Design behavior shown · no real decision
Review date: September 4, 2026
Owner: Authorized district decision owner
Retest trigger: Each high-impact workflow before pilot
Residual risk: The public walkthrough makes no real recommendation about a person.
Districts can strengthen protections and configure operations. They cannot switch off the core rights and controls.
This prototype demonstrates a test framework. An authorized pilot still requires independent privacy, cybersecurity, accessibility, civil-rights/equity, legal/policy, and athletics-compliance review plus adversarial testing with affected users.