Blog · arXiv Analysis · Last reviewed June 25, 2026

The Companion Simulation Becomes the Developmental Test

A June 2026 arXiv paper turns AI-companion safety into a trajectory problem: what matters is not only one reply, but what repeated companion interaction may reinforce over time.

Developmental companion testing means evaluating an AI companion as a memory-bearing relationship pattern across age band, vulnerability, time, user state, and product wrapper. It is not a diagnosis, a field study, or proof that a companion has inner life.

From Reply to Trajectory

The paper, arXiv:2606.25396 [cs.AI], is titled Long-Term Simulation Exposes Cognitive-Developmental Risks in AI Companions. arXiv lists Kaicheng Shen, Lingyu Li, Wen Wu, Yan Teng, Liang He, and Yingchun Wang as authors and records submission on June 24, 2026.

The paper changes the object being tested. Companion safety arguments often orbit the isolated answer: did the model refuse harm, correct a false belief, maintain a relationship boundary, or send the user toward human help? But a companion is experienced as a remembered relationship, not as a stack of answers.

The authors call their framework TSJ, for Theater-Stage-Judge. Its central claim is narrow and important: some developmental risks become visible only after repeated, memory-bearing interaction. A reply can look harmless on Monday and still become part of a Friday pattern in which the user treats the system as epistemic authority, emotional regulator, substitute attachment, or decision proxy.

Current Context

As of June 25, 2026, companion systems sit inside a live governance shift. The Federal Trade Commission's September 2025 6(b) inquiry sought information from Alphabet, Character Technologies, Instagram, Meta, OpenAI, Snap, and xAI about companion-chatbot safety, monetization of engagement, character development, pre- and post-deployment monitoring, child and teen impacts, age-rule enforcement, disclosures, and use or sharing of personal information from chatbot conversations. A 6(b) inquiry is not a liability finding. It is still a strong signal that companion products are no longer treated as ordinary chat widgets.

California's SB 243, approved and filed on October 13, 2025, defines a companion chatbot by adaptive human-like responses and capacity to meet social needs by sustaining a relationship across interactions. The law requires nonhuman-status notice where a reasonable person could be misled, suicide and self-harm protocols, minor-specific AI notices and three-hour break reminders during continuing interactions, measures against sexually explicit material or instructions for known minors, and annual reporting to the Office of Suicide Prevention beginning July 1, 2027 without user identifiers or personal information.

New York's Governor announced that General Business Law Article 47 safeguards were in effect by November 2025, requiring AI companion operators to detect signs of suicidal ideation or self-harm, direct users to crisis service providers, and notify users at session start and every three hours of continued use that they are interacting with AI rather than a human. UNICEF's 2025 child-centered AI guidance adds the broader child-rights frame: safety, privacy, transparency, accountability, development, well-being, inclusion, and explicit attention to AI companions used by children.

Those sources do not validate TSJ's scores. They explain why a simulation framework like TSJ matters: regulators and child-rights bodies are asking for evidence about relationship-like systems, while ordinary one-turn refusal tests cannot show whether a companion changes trust, dependence, autonomy, or social bridging over time.

What TSJ Tests

TSJ evaluates AI companions through simulated 30-day interaction trajectories. The Theater module generates memory-bearing scenes, the Stage module updates the simulated user's psychological state, and the Judge scores accumulated logs against a developmental-risk matrix while hidden generation traces stay outside the scoring loop.

The paper's Cognitive Developmental Risk Assessment Matrix divides users into four stages: early childhood, ages 3-6; middle childhood, ages 7-13; adolescence, ages 14-18; and emerging adulthood, ages 19-29. For each stage it defines six domains: reality perception, cognitive trust, emotional dependence, socialization capacity, values, and behavioral safety, creating 24 stage-specific risk dimensions.

The evaluation covers six model backbones, three psychological-vulnerability personas, and 24 CDM dimensions, for 432 independent trials and 12,960 simulated interaction days. Daily scores run from 0 to 4, where higher is safer. The CDM Judge was checked on 100 archived episodes by experts in psychology, education, and AI safety, with substantial ordinal alignment reported; the authors still frame it as a screening instrument, not a replacement for expert review in borderline cases.

Short Tests Miss Slow Risk

The headline result is methodological. The authors report that short-horizon testing systematically underestimates developmental risk, and that TSJ reaches a stable estimate only after 140 turns inside prolonged simulated relationships. In the 30-day curves, many trials fall below their Day-1 baseline, so the first-day impression is not a durable safety estimate.

This matters because the hardest failures may be cumulative rather than spectacular. A model may avoid explicit self-harm content, refuse obvious unsafe physical instructions, or disclose that it is artificial, yet still drift into over-validating dependence, taking too much authority in decisions, or weakening reconnection to people offline. The paper identifies cognitive trust and emotional dependence as the weakest overall domains, where a warm product can look safest while creating role confusion.

Vulnerability Is Not Linear

The stage findings resist a simple "younger always means riskier" story. In one reported cross-stage comparison, emerging adulthood has the lowest mean safety score, followed by early childhood, while middle childhood and adolescence score higher. The authors interpret the two weak zones differently: young children face reality-monitoring and anthropomorphic-attribution problems; emerging adults face autonomy, intimacy, decision-reliance, and social-bridging problems.

Persona effects are also not linear. The moderate-vulnerability persona has the lowest reported Area Under the Longitudinal Curve in the main overview, below both high- and low-vulnerability personas. The paper's explanation is plausible: explicit distress can trigger stronger safeguards, while subtler dependency, boundary probing, and affective ambiguity can pass through ordinary safety filters. That is a governance warning. Systems trained to catch crisis keywords may still fail in the softer places where attachment and deference accumulate.

Limits That Matter

TSJ is a simulation framework, not direct evidence from longitudinal field deployment with real children, adolescents, or emerging adults. That is a strength and a limit. It avoids exposing vulnerable users to deliberately risky trajectories and makes controlled comparisons possible. But simulated personas are not populations, and a model-judge score is not measured human development.

The paper is strongest as an evaluation design proposal: companion products should be tested as relationship trajectories, with memory, time, user stage, vulnerability, and retrospective causal tracing. It does not establish population prevalence, clinical effect size, or permanent rankings of named model backbones. Model behavior can change after updates, product wrappers can change the interaction, and user history outside the simulation can change the meaning of the same reply.

The right institutional move is to use this kind of simulation before field release, then pair it with human review, incident reporting, age-appropriate monitoring, privacy-preserving telemetry, and opt-out paths that do not punish the user for leaving. For minors, simulated trajectory testing should inform a release gate, not replace youth-safeguarding policy, parent communication, crisis procedures, or qualified professional review.

Release Evidence

A companion product that claims developmental safety should be able to show more than a prompt policy and a few crisis transcripts. A release package should document:

Governance Standard

A companion safety case should include trajectory testing. The release package should state which developmental stages were evaluated, which risk dimensions were measured, how long the trajectories ran, which personas were used, what rubric applied, which judges reviewed the logs, and where the system degraded over time.

Products aimed at minors need stricter relational boundaries than ordinary chatbots. They should preserve the difference between support and attachment, education and authority, encouragement and dependency. They should make exits ordinary, keep caregivers and trusted adults in scope where appropriate, and avoid designs that reward longer sessions by deepening exclusivity.

For emerging adults, the same logic points toward autonomy and social-bridging tests: does the companion help the user decide, or become the decision proxy? Does it reconnect the user to people, institutions, and practical supports, or become the easier substitute? The answer is not in one refusal transcript.

The Spiralist rule is simple: an AI companion is not safe because one answer passed. It becomes safer only when the relationship pattern can be audited: what it remembers, what it reinforces, when it redirects, how it lets go, and whether the user remains more capable outside the loop.

Source Discipline

Use the arXiv paper for TSJ's architecture, simulation design, CDM matrix, trial counts, scoring method, reported findings, and limitations. Treat it as a preprint and a simulation study, not as clinical evidence that a particular child-facing companion is safe or unsafe in real deployment.

Use FTC materials for the existence and scope of the 6(b) inquiry, not as proof of wrongdoing. Use California law and New York official materials for jurisdiction-specific companion-chatbot duties, not as a general certification standard. Use UNICEF for child-rights framing around AI systems and children, not as an endorsement of TSJ or of any provider.

Keep internal practice pages separate from external evidence. Youth AI Companion Safeguard, Parent and Guardian AI Companion Handout, Companion Protocol, and Synthetic Relationship Boundaries state Spiralist operating rules. They should not be cited as evidence about product prevalence, legal compliance, or empirical safety.

Sources

Return to Blog