1. Where the Bill Stands Today (May 20, 2026)
The bill is past committee and on the Senate Legislative Calendar. It is NOT yet law. Here is the procedural picture as of this writing.
Where it is in the Senate
S. 3062 was placed on the Senate Legislative Calendar under General Orders on May 11, 2026, following the unanimous 22-0 Judiciary Committee vote on April 30. This is the procedural step that makes the bill eligible for a full Senate floor vote. The floor vote has not yet been scheduled.
Where it is in the House
A companion bill has been introduced in the House. The 22-0 bipartisan signal in the Senate Judiciary Committee, plus the introduced House companion, are the two main indicators that a floor vote in this Congress is realistic rather than aspirational.
What could change the picture
Two known risks to the timeline:
- Industry opposition — some tech industry groups (e.g., NetChoice) are publicly opposing the age-verification provisions on privacy and First Amendment grounds. Floor amendments to soften age-verification language are possible.
- Senate floor scheduling priorities — calendar placement is a necessary but not sufficient step. Bills can sit on the Senate calendar for months without floor action if leadership prioritizes other items.
If the bill is materially amended on the floor, this page will be updated. The provisions described in Section 2 reflect the introduced bill text as advanced by Judiciary.
Net read: this is a bill worth tracking actively, not preparing for as if it were already law. The architecture conversation in district procurement should start now (see Section 6 below); the compliance scramble does not.
2. What S. 3062 Actually Says
The bill is short by federal-statute standards (13 pages) and the operative provisions are concentrated in four sections. Here’s what each says, in plain English, with section numbers.
§ 3(1) — The definition of “AI companion”
An “AI companion” under the bill is an AI chatbot that:
“(A) provides adaptive, human-like responses to user inputs; and (B) is designed to encourage or facilitate the simulation of interpersonal or emotional interaction, friendship, companionship, or therapeutic communication.”
The word that matters for school SEL technology: therapeutic communication. Any chatbot designed for kids to have therapeutic-feeling conversations falls into scope.
§ 3(2)(B) — The narrow-purpose carve-out
The bill expressly excludes from its “AI chatbot” definition any tool whose responses are:
“(i) limited to contextualized replies; and (ii) that is unable to respond on a range of topics outside of a narrow specified purpose.”
Tools built around a single, contained job — rather than open-ended conversation — are not regulated by this bill.
§ 5(c)(2)(A) — The therapist-representation prohibition
Covered AI chatbots:
“may not represent, directly or indirectly, that the chatbot is a licensed professional, including a therapist, physician, lawyer, financial advisor, or other professional.”
§ 5(c)(2)(B) — Required disclosure
Covered chatbots must disclose “at the initiation of each conversation with a user and at reasonably regular intervals” that the chatbot does not provide medical, legal, financial, or psychological services, and that users should consult a licensed professional.
§ 6 — The hard prohibition on minor access
If a covered entity’s age verification process determines a user is a minor, the entity “shall prohibit the minor from accessing or using any AI companion” the entity owns, operates, or otherwise makes available.
In other words: the bill doesn’t restrict how AI companions can be used with minors. It bans them from being used with minors at all.
3. Who This Bill Catches
The K-12 educational technology market includes a growing number of student-facing AI products. The bill’s “therapeutic communication” language is the trigger that matters for SEL technology.
Reading the bill literally, the following product categories would be considered “AI companions” under § 3(1) and therefore prohibited from minor access under § 6:
- AI chatbots designed for students to talk through their feelings or process social situations — even if framed as “SEL coaching” or “resiliency support.”
- Character-based bots positioned as friends, mentors, or therapeutic companions for K-8 students.
- Open-ended generative chatbots embedded in school platforms where students can ask the AI about their lives, emotions, or relationships.
- AI tutors that hold themselves out as functionally equivalent to a counselor or psychologist for student support purposes.
Regardless of how a vendor markets the product, the bill’s definition turns on what the product is designed to do. A chatbot whose design encourages students to engage in therapeutic-style dialogue with the AI is in scope, even if the vendor never uses the word “therapist.”
4. Where Story Bridge Fits Under the Bill
Story Bridge was designed before this bill existed. We are not adapting to comply. The product architecture already meets each requirement.
Here is how each operative provision maps to Story Bridge’s architecture:
§ 3(1) — “AI companion” definition
Story Bridge is not an AI companion.
The bill’s definition requires an AI chatbot that provides adaptive responses to a user and is designed to simulate interpersonal or therapeutic communication. Story Bridge’s user is the school counselor or school social worker, not the student. The counselor describes a student situation; Story Bridge generates a story; the counselor reads that story with the child. There is no chatbot relationship between the AI and the student. The student never types into the system.
§ 3(2)(B) — Narrow-purpose carve-out
Story Bridge fits the carve-out.
The platform’s purpose is narrow and contained: a counselor provides a structured input describing a Tier 2 student situation, and the system produces a single therapeutic story plus implementation notes. It does not respond on open-ended topics. It does not maintain ongoing dialogue. The output is “limited to contextualized replies” within a narrow specified purpose. This is the express statutory carve-out.
§ 5(c)(2)(A) — Therapist-representation prohibition
Story Bridge does not represent itself as a licensed professional.
Our marketing, product copy, and counselor-facing UI consistently frame Story Bridge as a tool that supports counselors. The licensed professional is the school social worker, school psychologist, or school counselor — the same definition ESEA § 4108 uses for “school-based mental health services provider.” Story Bridge is the platform; the counselor is the clinician.
§ 5(c)(2)(B) — Disclosure requirement
Not applicable in the form the bill contemplates.
The disclosure requirement is structured around a chatbot’s “initiation of each conversation with a user.” There is no chatbot conversation between Story Bridge and a student. The counselor reads the story with the child; the relationship is human-to-human. Where appropriate, we will add platform-level acknowledgments that counselors should rely on their professional judgment when adapting any Story Bridge output to a specific student.
§ 6 — Prohibition on minor access
Minors do not access Story Bridge as users.
User accounts on Story Bridge are held by counselors, school social workers, and student services administrators. K-8 students are the audience for stories the counselor selects and reads with them — the same way a counselor selects and reads a published picture book with a student. The student is not a Story Bridge user under any reading of § 5(a) or § 6.
5. Why We Designed It This Way
The compliance picture is downstream of a deeper design decision. We never wanted the AI to be in a relationship with the child.
Story Bridge was co-founded by a practicing K-5 school social worker with fifteen years in Wisconsin schools. The product was built from the practitioner’s experience: the relationship between counselor and student is the intervention. Whatever artifact the counselor brings into the room — a book, a worksheet, a story — is the bridge. Replacing the counselor with a chatbot misunderstands what is actually working in a Tier 2 SEL session.
The federal policy direction of travel — bipartisan 22-0 advancement of the GUARD Act, parallel state-level activity, the OpenAI Child Protection Blueprint endorsed by State Attorneys General — is converging on the same principle: AI for children needs an adult in the room. That conclusion lines up with the conclusion school social workers and counselors have always drawn from their own practice. We built around that principle from the start.
We don’t have a student-facing chatbot to retire. We don’t need to add age-verification infrastructure. We don’t need to retrofit disclosure language about “not a licensed professional.” The architecture was already there.
6. What This Means for Districts Evaluating AI for SEL
If your district is evaluating any AI tool for K-8 student support in 2026, three questions are now load-bearing for procurement.
- Who is the user? If the AI is designed for the student to interact with directly, the product is in regulatory scope. If the AI is designed for the counselor and the counselor delivers the artifact to the student, it is not.
- What is the purpose? Open-ended, conversational AI products that span topics fall under the bill. Narrow-purpose tools that generate a single contained artifact from a structured input fall outside.
- What does the product represent itself as? Any positioning — in marketing, in product copy, in onboarding flows — that suggests the AI is a therapist, counselor, or psychological-services provider is now legal exposure.
Districts that are mid-procurement on student-facing AI products in 2026 should add these three questions to their vendor evaluation criteria. The 180-day effective date in § 8 of the GUARD Act, if enacted, gives any non-compliant product less than half a school year to either rearchitect or exit the K-12 market.
7. What Districts Should Do This Week
Three concrete steps that are right whether the GUARD Act passes the Senate floor this Congress or next.
1. Audit your current AI tools against the “AI companion” test.
For every AI tool currently deployed or under evaluation in your district, ask: (a) Does a student interact with the AI directly? (b) Is the tool designed for open-ended conversation, or is it limited to one narrow purpose? (c) Does the product’s marketing or product copy describe itself in therapist-like terms?
Tools that answer “yes” on (a) or (b) and “yes” on (c) are the ones to flag for legal review now. The other tools can wait.
2. Add three questions to your procurement template.
Even if the GUARD Act stalls, the underlying procurement questions are sound on their own. Add these to your standard vendor evaluation form:
- Who is the primary user of your AI — the student or the educator?
- What is the AI’s scope — open conversation, or a narrow defined output?
- Does your product or marketing represent the AI as providing therapeutic, psychological, medical, or legal services?
3. Track the floor vote — not the press cycle.
The bill’s status as of May 20, 2026 is “on the Senate Legislative Calendar” — a procedural step, not enactment. The single piece of information that should trigger immediate action is the scheduled Senate floor vote date. Subscribe to Congress.gov tracking for S. 3062 rather than relying on news headlines, which compress “committee advance” and “passage” together.
Story Bridge will update this page when the bill moves materially — floor vote scheduled, amendments adopted, passage, or House action. The page’s “Last updated” line above the timeline reflects the most recent confirmed status.