Technical overview

Local-first learning with controlled role boundaries.

This page contains the technical depth kept away from the main visitor journey: data separation, offline behaviour, handoffs, install boundaries and production-readiness requirements.

Role separation

All ten role environments use distinct routes, controls and permission boundaries, including separate Pupil and Pupil Take-Home Apps, separate SEND App and SEND Dashboard, leadership dashboards, school control, operations and ParentLink.

Offline-first operation

Core lessons, support flows and local records can remain available without a constant network connection.

Controlled handoffs

Pending information can move through approved sync, QR or file-based workflows with audit records.

Current demonstration architecture

  • Static, backend-ready public demonstration
  • Service-worker caching and offline fallback
  • LocalStorage and IndexedDB demonstrations
  • Role-specific installable App manifests
  • Local lesson checking and predefined VexSpark™ support

Production requirements

  • Secure authentication and role-based access control
  • Encryption, audit logs and secure backups
  • School-specific DPIA and data-processing agreements
  • Penetration testing and vulnerability management
  • Incident response, retention and deletion controls
Boundary: the public build uses fictional demonstration information. A production deployment would require approved infrastructure, contracts, policies, safeguarding procedures and independent security testing.