Executive Summary

Supervision around the black box is not supervision over the black box.

A teacher may set conditions before a student interacts with the system and may review outputs afterward. But that does not mean the teacher supervises what occurs during content formation.

For risk managers and insurers, the governance problem can be stated in familiar operational terms. A student-facing generative AI deployment must preserve enough explainability, predictability, traceability, and repeatability for institutional accountability to function. The institution does not need to predict every output in advance, but it must define the authorized boundary of use, trace what occurred from records it can retrieve, explain how responsibility was assigned, and apply a repeatable correction process when a harm, concern, or boundary deviation is identified.

The IAF identifies governance failure modes that may arise when generative AI systems are made available to students through school-issued devices, district accounts, approved platforms, embedded features, or other school-controlled access pathways.

1

The Supervision Gap

Institutional authority does not extend to the content formation phase where outputs are generated. Schools control input conditions and may review outputs after delivery. They do not control what occurs between them.

2

AUP Insufficiency

Acceptable use policies assume that student inputs are independently generated and attributable to the student. Generative systems can suggest, complete, frame, or influence those inputs across stateful multi-turn interactions.

3

The Conformance Gap

A student may be bound by school policy while the system is not bound by any comparable mechanism requiring its behavior to remain within school policy, instructional purpose, or age-appropriate instructional value.

4

The Parental Supervisory Gap

Parents may hold authority over the child, but they typically do not hold authority over the system. Content supervision requires access, logs, controls, and the ability to preview, restrict, or constrain outputs. Most parents are not given those tools.

5

The Reporting Boundary

Reporting a harmful or nonconforming output does not, by itself, correct the system. Correctability requires a binding pathway that routes the condition to an entity with authority to act and verifies correction before comparable student exposure continues.

6

Accountability Stack Failure

Policies, logging, supervision, and insurance are not independent controls. They form a sequence in which each element enables the next. Where any element is absent, the sequence does not produce partial governance. It produces the appearance of governance without its functional conditions.

7

The Reconstruction Gap

Logs are not the same as reconstruction. If a record is sufficient for reconstruction, it shows the full interaction sequence, including student prompts, system outputs, system suggestions, auto-completions, and where relevant, retained context, access conditions, and supervision context, such as whether the interaction occurred at home, at school, or under teacher observation. Where the institution cannot reconstruct those conditions from records it can retrieve, attribution cannot be demonstrated, and accountability, conformance review, and correction are undermined in turn.

8

In Loco Parentis Inversion

The doctrine of in loco parentis presupposes the unity of custody, authority, and accountability. Generative AI deployments sever that unity: schools retain custody and accountability, but authority over content formation resides with a vendor that bears no corresponding custodial obligation. A doctrine premised on that unity cannot function as intended where the unity has been severed.

9

The Ungoverned Advisor Condition

A conversational generative system that is continuously available to a minor, across topics, at advisory depth, may occupy a role closer to an advisor than a bounded digital tool. Existing digital-tool governance frameworks were not designed for that condition.

The IAF establishes five operational conditions for accountable deployment.

Condition 1

Attribution

Can the institution determine who or what originated the relevant input or output?

Condition 2

Reconstructability

Can the institution know what occurred from records it can independently retrieve?

Condition 3

Accountability

Has a named entity accepted responsibility, and does that entity hold authority commensurate with that responsibility?

Condition 4

Conformance

Can the institution determine whether actual use remains within the boundary it authorized?

Condition 5

Correctability

Can an identified harm, concern, or nonconforming condition be bound to verified correction?

These conditions are not a checklist. They are an interdependent sequence. Four out of five does not produce partial governance. It produces the appearance of governance with a structural gap that becomes material when a harm, concern, or contested interaction requires the missing condition.

Threshold question

Can the institution determine, on an ongoing basis and independent of whether any student harm or concern has been reported, whether the deployment is operating within school policy and age-appropriate instructional value?

This is the Conformance State.

Specific interaction

Only once the Conformance State is established does the test turn to a specific interaction:

  • What happened?
  • Who was responsible?
  • Why did it happen?
  • How will recurrence be prevented?
A governance framework that cannot establish a determinable Conformance State and answer the four event-specific questions from records the institution independently holds has not established governance adequate to the deployment it authorized. It has assumed governance.

Downward

Institution to Student

What the institution owes the student directly.

Upward

Institution to Vendor

What the institution must secure from vendors before deployment, including logging, correction, responsibility alignment, change control, and enforceable commitments.

Lateral

Institution to Insurer

What the institution must confirm with insurers, including whether coverage has been evaluated for the specific student-facing generative AI use case.

Inward

Institution to Its Own Governance Infrastructure

Whether the institution has built the internal infrastructure needed to detect, reconstruct, classify, route, and correct concerns from records and mechanisms it can actually use.

If any direction is missing, the accountability chain is incomplete.

Every district deploying generative AI systems with students faces the same structural choice: not between using AI and not using AI, but between governing the deployment adequately and assuming it is governed.

A governed deployment

Carries real immediate costs: procurement review, vendor negotiation, logging infrastructure, coverage confirmation, population-level monitoring, conformance review, and correction pathways.

A legacy posture

Carries lower immediate friction but may leave the institution with unconfirmed and potentially retained exposure where vendor responsibility is disclaimed, insurer review has not occurred, and the governance infrastructure required to respond to a claim or contested interaction has not been established.

The IAF applies to generative AI systems with conversational capability that interact directly with students, regardless of product labeling, deployment pathway, or whether use occurs on school premises. It applies based on how the system behaves in the student environment, not on whether the vendor or district labels it as a chatbot, tutor, search assistant, productivity tool, embedded feature, or instructional platform.

It does not apply to teacher-facing tools that operate under direct adult supervision without independently interacting with students.

The IAF does not argue that generative AI should or should not be used in schools. It establishes what governing such systems would require if they are used.