INTYLLECTUAL · ACTION LAB

See the need.
Act. Review. Adjust.

A teacher-led support cycle, not just a list of students near a cut score.

STUDENT SUPPORT IN ACTION · v17
100% fictional demonstration. No real student or district data was used. No live AI or school connection. Changes reset on refresh.
Illustrative Grade 7 · Mathematics

Who needs what next?

Fictional fixture snapshot: November 14, 2026 · 6 fictional learners

Governance by design · proposed production model

Connected evidence. Controlled access.

This public demo uses fictional records only. Viewpoint buttons illustrate different experiences; they do not authenticate users or enforce permissions. No SIS, assessment, IEP or 504 system is connected. Do not enter real student information or upload student documents.

Who would have access?

Proposed access combines verified identity, district/school assignment, student relationship, record sensitivity and permitted action. A job title alone does not grant access. View, contribute, edit, approve and export are separate permissions.

  • Teachers: assigned learners’ relevant learning evidence and instructional supports; contribute observations and delivery records.
  • Case managers and designated specialists: authorized RTI/MTSS, IEP or Section 504 workflows for assigned cases; maintain plan versions and review history.
  • School leadership: school-level patterns and authorized student follow-up.
  • District leadership: aggregate patterns first; individual drill-down only where responsibilities and authorization justify it. Small-group reporting needs disclosure controls.
  • Students and caregivers: their authorized goals, supports, progress and participation pathways. Verify student/guardian relationships and applicable records-access rights; a simplified portal must not replace those rights.
  • Technical administrators and vendors: no blanket educational-record access by default; any operational access must be specifically authorized, limited and auditable.

FERPA requires reasonable methods to limit school-official access to records in which they have a legitimate educational interest. U.S. Department of Education guidance ↗

Parent records-access and participation safeguards also apply to relevant special-education and Section 504 records. IDEA records access ↗ · Section 504 guidance ↗

How could systems bring the evidence together?

Potential connections—not installed integrations. A district would approve each source, purpose, field mapping and access scope before any data transfer. Availability depends on the provider’s supported API or export, licensing and district authorization.

  1. SIS: enrollment, school/grade, schedules, attendance and verified student/guardian relationships; discipline only where supported and explicitly approved.
  2. Assessment and learning platforms: dated results, assessment versions, standards and assignment evidence. Scores from different tests must not be treated as interchangeable.
  3. Intervention/MTSS systems: goals, intervention history, planned versus delivered sessions, progress checks and accountable staff.
  4. Special-education and 504 systems: separately authorized plan status, relevant accommodations, services, goals and review dates. Sensitive documents stay in their approved source system where feasible, with controlled links.
  5. School improvement plans: priorities, strategies, milestones, owners and evidence of implementation.

Proposed data flow: approved source → restricted read-only import → identity matching and validation → authorized dashboard views → human review. Begin with read-only connections; any write-back requires separate design and approval.

Keep source identifiers, effective dates, last successful sync, missing records and corrections visible. Quarantine ambiguous matches rather than merging students by name. A stale or failed connection must not silently replace the last verified record or display missing data as zero.

What security and governance would real use require?
  • District-approved agreements, purposes, data minimization, retention/deletion rules and incident-response responsibilities.
  • Server-enforced access for records, search, exports and document downloads; tenant separation and prompt access removal when assignments change.
  • Approved identity controls, secure transport and storage, protected credentials, and auditable access, changes and exports. These production controls are not demonstrated by the public role toggle.
  • Versioned documents with draft/final status, accountable reviewers and clear correction history.
  • No automatic eligibility, placement or disciplinary decisions. Human teams retain decision authority.
  • No student records sent to an AI provider without separately approved purpose, contracts, data-use terms and security review. No model runs in this demo.

Current boundary: this is a public fictional prototype, not a claim of FERPA compliance, security certification, production readiness or an operating district integration.