Before pupil launch
Configure validation
Choose the school context once, then keep the pupil experience simple. This demonstrator saves configuration only in your browser; production will use authenticated role-based administration.
Validation details
Used to personalise the demonstrator and its alignment layer.
Identity & governance model
One persistent pupil identity, managed through the school and school group.
School groupGovernance and cross-school configuration
RoleSchoolStaff, profile, reporting
RoleTeacherClasses, assignments, observations
RolePupilPseudonymous VIBE ID + school-managed sign-in
JourneyHome use: the same pupil identity may continue teacher-approved activity at home. Context is tagged so home practice is not silently treated as supervised school evidence.
Validation readiness checklist
Governance preparation only — not a legal or regulator certification checklist.
Before live pupil use: re-check the current source set, the school’s own policies, applicable privacy/data-protection requirements, and any procurement/security conditions. VIBE’s school context profile is an evidence map — not legal advice.
Global configuration rule
The product should never fork into separate hard-coded country apps.
1One VIBE CoreSame SEL framework, CoBots, mission engine and evidence contract.
2School context profileCountry/location evidence profile selected at setup; curriculum configured independently.
3Source-linked claimsEvery regulatory mapping displays an official source and a boundary.
4Version the mappingRe-check it when regulator requirements change.
Production connection
The UI and data contract are ready for a real backend, but this package intentionally remains safe to share because authentication and persistence are local demo functions.