30/100

Emerging evidence

Published recordHealthGeneral

AI and Teen Identity Formation

Truvace record
TRV-2026-2552raw data (JSON)
Version
v2Revised
First published
Evidence type
Commentary, opinion, or narrative review
Sources
1 sourcePeer-reviewed
sha256
ec41afe04a13…check it

Identity exploration is a central developmental task of adolescence. As proposed by Erikson1 and subsequent research, adolescence is a critical period for answering fundamental questions: “Who am I? What do I believe? Who do I want to become?” Pediatricians witness this process during well-child visits as adolescents navigate shifting interests, peer dynamics, and family tensions. Increasingly, however, this exploration is taking place not with people but with artificial intelligence (AI).Generative AI (systems…

The problem

A Pediatrics commentary argues that teens who explore identity privately with agreeable AI chatbots may lose the reciprocal human feedback that healthy identity formation depends on.

What this doesn’t fix

The authors say empirical research on adolescent AI use for identity exploration remains limited, and their discussion assumes reasonably responsive caregiving, which is not universal.

Sources

1 on file
  1. Pediatricsdoi:10.1542/peds.2026-076609
    Peer-reviewed2026-08-25

Cite this record

v2

Truvace Impact Record TRV-2026-2552, v2: “AI and Teen Identity Formation.” Truvace, 2026-11-12. /record/TRV-2026-2552 (accessed on the day you copy it). sha256 ec41afe04a13175f…

Change history

2 versions

Every change made to this record since it was first published, and why.

  1. Revisedv2ec41afe04a13…

    Filed as context: this is an argument or a review without a measured outcome, so it is not counted as a problem. The record's text is unchanged.

  2. Publishedv1008c757fa10a…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2552 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.