What Nexus can use
- Student academic work
- Assignment-linked reflection
- Educator-reviewed evidence
- LMS-approved workflow data
- Observable learning signals
Trust & Safety
Trust starts before the pilot begins
Nexus uses evidence from student coursework. Educators review what surfaced. Districts approve the scope, data boundaries, access, and expansion path before expansion.
UsesApproved coursework evidence
ShowsObservable learning signals
KeepsDecisions with educators
ReportsCareful pilot evidence summary
School-approved trust path
Coursework evidence
Educator judgment
District-approved scope
Human decision
Pilot Evidence Summary
Data boundaries
What Nexus uses, what it does not use, and what stays human
IXR helps schools review evidence from student coursework while keeping decisions with educators and data boundaries with the district.
What Nexus does not use
- Hidden mental-state claims
- Personality labels
- Discipline decisions
- Private messages outside the approved scope
- Evidence unrelated to the learning task
What stays human
- Educators review what surfaced
- Educators decide what happens next
- Districts approve the implementation scope
- Leaders review pilot patterns before expansion
- Nexus is careful not to overclaim from limited evidence
Trust signals
Built for school approval before expansion
Districts need clear boundaries before they expand any AI-supported learning system. IXR keeps implementation governed, evidence-based, and educator-guided.
FERPA
School-controlled data practices are reviewed with the district and aligned to school data expectations.
COPPA
Student-facing experiences are governed by the participating school or district.
CA-NDPA
IXR has an executed CA-NDPA agreement path through CITE Privacy Services.
District approval
Schools keep control of the implementation
Before a pilot begins, the district reviews the scope, users, LMS connection, access rules, privacy boundaries, and success questions.
Before the pilot
Districts approve scope, users, LMS connection, data boundaries, access rules, and success questions.
During the pilot
Educators use Nexus with approved coursework. Educators remain in control of support decisions.
After the pilot
The district reviews what surfaced, what educators used, and whether expansion is warranted.
Responsible AI boundaries
Clear limits create trust
Nexus is designed to support educator review, not replace professional judgment.
Not an AI detector
Nexus does not accuse students of cheating or reduce learning to a detection claim.
Not a grading engine
Nexus surfaces learning evidence for educator review. Educators and schools decide what happens next.
Not a diagnosis tool
Nexus does not profile students, diagnose students, or automate discipline decisions.
Start with a safe, focused pilot
Review the scope, data boundaries, users, support path, and Pilot Evidence Summary before expansion.