Evidence is not an access grant
A linked record retains its source context. Opening it still depends on the source’s permissions. The demo includes a restricted evidence example with no confidential payload.
Connected context. Clear boundaries.
Trust starts with being precise about what is demonstrated, what is intended and what still needs confirmation.
Implementation and school access differ
Code and tests can establish a capability exists. They do not establish deployment, a pilot agreement or permission to offer it to a school. No school availability is asserted by this preview.
A task is not an impact measure
Completing follow-through records delivery. A professional judgement, recommendation closure or educational impact review requires a separate human decision.
Each domain keeps its responsibility
Curriculum & assessment planning owns curriculum design; Gradebook & reporting owns results; Student records owns learner identity. Calendar and Home / Control Centre may present source information without taking it over.
A prepared resource is not safety approval
Intended operational tools do not replace a person’s qualifications, specialist safety decisions or statutory checks. No operational product demonstration is available here.
Public assurances require separate evidence
Hosting region, data residency, certifications, framework licences, service levels, legal terms, customer references and real integrations need approved evidence before public claims are made.
This page explains the review prototype and product principles. The website-only Privacy Notice and Website terms are drafts for owner review. They do not establish security certification, approved school-product agreements or public activation.
See the current evidence and direction