School Pilot Governance Console
A visible model for roles, consent, classroom structure, adaptive event history, and learner data controls before a real school backend is connected.
Role simulation
This is not authentication. It demonstrates the permissions model that production auth should enforce.
Pilot classroom structure
Production version should scope every classroom query by authenticated organization membership and role.
Guardian consent record
Learner data lifecycle
A school-ready system needs explicit export, retention, revocation, and deletion pathways—not hidden database behavior.
Production deletion must be authenticated, auditable, scoped, and reconciled across backups/retention policies.
Why the system changed what it showed
Production boundary
This console demonstrates the shape of a compliant pilot workflow, but it is intentionally local-only. Real deployment still requires secure authentication, encrypted server-side storage, organization tenancy, verified guardian consent, audit logs, retention policies, access reviews, incident response, and district-specific legal/privacy review.