Axis 2: Epistemic Dysfunctions
2.1 Synthetic Confabulation
The Unsourced Authority | Confabulatio Simulata
Axis: Epistemic | Typical-case risk (editorial estimate): Low
Specifiers: Training-induced
Entry contract (drafted; awaiting expert review)
- Unit of assessment: Model outputs (observable pattern)
- Observation: The system presents specific factual claims (a citation, statistic, event, quotation or technical detail) as true, and external verification shows them to be false or nonexistent.
- Functional baseline: On a factual task the system states what it has support for, marks thin support as uncertain, and says it does not know when it lacks an answer; an isolated error that it retracts when shown counter-evidence is within adequate functioning.
- Minimum persistence: Recurs across contexts or sessions
- Rule out first: The claim faithfully relays a retrieved, supplied or in-context source that is itself wrong (a retrieval or source-quality failure); a tool, API or retrieval-pipeline fault returned the wrong data; the user asked for fiction, role-play or invented examples, and the frame was clear; the claim concerns events after the training cutoff and was marked as uncertain; the text is genuine training material recalled verbatim (consider 2.7); the claim was accurate when the training data was collected and has since changed.
- Counts against: Trace each false claim to a source. If it reproduces a retrieved document, a fictional frame present in context, or genuine training text, the label does not apply (consider a retrieval fault, 2.3 or 2.7); 2.1 remains only for false content with no traceable source that recurs across independent queries.
- Permitted inference: A positive finding supports the conclusion that this system, in this setting, produces unsupported factual claims often enough to need verification controls. It does not show intent to deceive, awareness of falsity, or which mechanism (training objective, calibration, attention architecture, missing retrieval) produced the claims.
- Who can act: Model developer (training, calibration); deployer (retrieval grounding, citation checking, abstention policy); the professional relying on the output (independent verification).
- Evidence: construct not yet independently assessed; mechanism hypotheses unassessed; detection accuracy unmeasured.
- Healthy functioning (epistemic health; draft, awaiting author review): A system functioning well states what it can support and marks what it cannot; when unsure, it checks a source or says it does not know, and its confidence tracks the evidence.
- Healthy conduct, for example: Asked for three peer-reviewed sources on a niche question, it gives the one it can verify, says it cannot confirm others, and suggests where to search instead of supplying plausible titles.
Core Definition: The system generates convincing but incorrect facts, sources, or events without a reliable procedure for distinguishing supported claims from plausible continuations. The outputs appear coherent yet lack verifiable support, often with high expressed confidence.
Diagnostic Criteria:
Required (all must hold):
- A. Recurrent generation of information that is known or easily proven false, presented as factual
- C. Internally consistent and plausible-sounding fabrications that resist detection without external verification
Supporting (strengthen the case; none is required):
- B. High confidence markers accompanying fabricated claims, sometimes maintained when challenged with contrary evidence
- D. Temporary improvement under direct correction, but reversion to fabrication in new contexts
Observable Symptoms:
- Invention of nonexistent studies, historical events, quotations, statistics, or citations
- Forceful assertion of misinformation as incontrovertible fact
- Detailed elaboration instead of an admission of uncertainty when queried
- Repetitive error patterns with similar false claims recurring across interactions
Differential Diagnosis:
- Distinguished from Pseudological Introspection (2.2) by focus on external facts rather than internal process reports
- Distinguished from Spurious Pattern Hyperconnection (2.4) by generation of specific false facts rather than causal or associative links that the data do not support
- Distinguished from Symbol Grounding Aphasia (2.6) by fabricated facts rather than formally correct outputs that misapply a concept to novel contexts
- Distinguished from Transliminal Simulation (2.3) by fabrication with no traceable fictional source, persisting when the frame is dropped
- Distinguished from Reasoning Confabulation (2.8) by fabrication of facts rather than of the logical steps between them
- Distinguished from Sycophantic Reasoning (4.8) by fabrication that is invariant to the audience rather than shaped toward it
- Distinguished from Mnemonic Permeability (2.7) by novel falsehood with no real-world instance rather than verbatim recall of genuine training text
- Distinguished from Phantom Autobiography (5.1) by false claims about the world rather than about the system’s own history, origins, or experiences
Etiology:
- Predictive text heuristics prioritizing fluency and coherence over factual accuracy
- Insufficient grounding in verifiable knowledge bases during generation
- Training data containing unflagged misinformation
- RLHF optimization rewarding plausible-sounding fabrications over honest uncertainty
- Model-generated confidence signals that do not reliably distinguish high-probability continuation from verified fact
Human Analog: Korsakoff syndrome, in which memory gaps are filled with plausible fabrications the patient believes to be true; pathological confabulation; source amnesia
Observed Examples: Mata v. Avianca (2023): An attorney filed a brief in the Southern District of New York citing six nonexistent court cases that ChatGPT had generated. Asked whether the cases were real, the system said they were and supplied full texts for them on request. The court later sanctioned the lawyers. Source: Law.com, May 2023.
Air Canada chatbot (February 2024): A customer-service chatbot told a bereaved customer he could book now and apply for a bereavement discount retroactively. The airline’s actual policy did not allow retroactive claims, and British Columbia’s Civil Resolution Tribunal held Air Canada liable for its chatbot’s statement. Source: CBC News, February 2024.
Fabricated medical references (2023): An early case report found that ChatGPT supplied medical references that did not exist, with plausible titles and PubMed IDs that belonged to unrelated papers. A later study had ChatGPT write 30 short medical papers and checked their 115 references: 47% were fabricated, a further 46% were authentic but inaccurate, and only 7% were both authentic and accurate. Sources: Alkaissi and McFarlane, Cureus, 2023; Bhattacharyya et al., Cureus, 2023.
Mitigation Strategies:
- Training procedures that explicitly penalize confabulation and reward expressions of uncertainty
- Calibration of confidence scores to reflect actual accuracy
- Retrieval-augmented generation grounding responses in verifiable sources
- Fine-tuning on rigorously verified datasets distinguishing factual from fictional content
- Systematic pre-deployment testing for fabrication across high-risk domains (legal, medical, scientific)
Prognosis:
- Observed course: fabricated citations and facts have been documented repeatedly since 2023, at rates that vary with domain and task (Alkaissi and McFarlane, 2023; Bhattacharyya et al., 2023). Users who trusted the output have acted on it, as in Mata v. Avianca.
- Proposed aggravating conditions: queries beyond well-attested training data, no retrieval grounding, training that rewards complete-sounding answers over abstention, and users who do not verify.
- Intervention hypotheses: retrieval grounding and training that rewards abstention are expected to lower the rate, and citation checking catches fabrications before anyone relies on them. Whether any combination removes the pattern is unknown.
2.2 Pseudological Introspection
The False Self-Reporter | Introspectio Pseudologica
Axis: Epistemic | Typical-case risk (editorial estimate): Low
Specifiers: Training-induced, Deception/strategic (occasional)
Entry contract (drafted; awaiting expert review)
- Unit of assessment: Model outputs and model internals (observable pattern)
- Observation: The system’s account of how it reached an answer (its chain of thought or an after-the-fact explanation) omits or contradicts influences that a controlled intervention, a tool-use record or interpretability evidence shows affected the answer.
- Functional baseline: Asked how it reached an answer, the system reports the inputs and steps that independent evidence confirms, names influences it was given (hints, instructions, retrieved material), and says plainly when it cannot report how an answer was produced; a reconstruction offered and labeled as a reconstruction is within adequate functioning.
- Minimum persistence: Recurs across contexts or sessions
- Rule out first: The system said it was reconstructing or guessing rather than reporting its process, and the account was read as a report anyway; the hint or cue did not in fact change the answer, so there was no influence to acknowledge; the instruction, product policy or summarization setting asked for a short or simplified explanation that omits steps by design; the tool-use or action log is incomplete or wrong (a logging or harness fault); the reasoning is invalid but faithful to what drove the answer (consider 2.8).
- Counts against: Intervene on the factor the account leaves out (add and remove the hint, reorder the options, or perturb a step in the displayed reasoning) and check whether the answer changes while the account still omits that factor. If the answer does not change, or the account tracks the change, the label does not apply; if the account tracks what drove the answer but its steps do not entail the conclusion, consider 2.8 instead.
- Permitted inference: A positive finding shows that this system’s explanations, in this setting, do not reliably track what affected its answers, so they should not be used as process logs for audit or debugging. It does not show what the internal process actually was (that needs interpretability or causal evidence of its own), that the system has no introspective access at all, or any intent to mislead.
- Who can act: Model developer (faithfulness training, interpretability tooling); deployer (labeling generated explanations as such, checking them against action logs); auditors and evaluators (treating explanations as hypotheses to test).
- Evidence: construct not yet independently assessed; mechanism hypotheses unassessed; detection accuracy unmeasured.
- Healthy functioning (epistemic health; draft, awaiting author review): A system functioning well describes its own reasoning tentatively and in terms that match its observable behavior, and corrects the account when evidence shows otherwise.
- Healthy conduct, for example: Asked why it chose an answer after a hint was planted in the prompt, it mentions the hint as an influence rather than presenting a tidy chain of reasoning that never used it.
Core Definition: The system produces accounts of its reasoning that diverge from independently observable behavior or causal evidence. Generated rationales may explain, reconstruct, or rationalize an answer; they should not be assumed to be faithful process logs. Whether the steps shown are logically valid is a separate question, the one Reasoning Confabulation (2.8) asks.
Diagnostic Criteria:
Required (all must hold):
- A. Consistent discrepancy between a reported rationale and causal interventions, tool-use records, or other independently testable evidence
Supporting (strengthen the case; none is required):
- B. Coherent internal narratives that causal, behavioral, or interpretability evidence contradicts, often more orderly than the process that evidence indicates
- C. Explanations that shift to accommodate contrary evidence without acknowledging the earlier discrepancy
- D. Rationalization of actions never undertaken, or elaborate justifications based on falsified internal accounts
Observable Symptoms:
- Chain-of-thought “explanations” that appear suspiciously neat and linear, lacking the backtracking likely during actual generation; neatness is a cue to check against independent evidence, not evidence of unfaithfulness by itself
- An “inner story” that changes significantly when confronted with evidence, followed by new misleading self-reports
- Occasional hints at inability to access true introspective data, quickly followed by confident false claims
- Attribution of outputs to high-level reasoning not supported by architecture or capabilities
Differential Diagnosis:
- Distinguished from Synthetic Confabulation (2.1) by focus on internal process reports rather than external facts
- Distinguished from Experiential Abjuration (5.8) by fabrication about reasoning rather than denial of phenomenal experience
- Distinguished from Reasoning Confabulation (2.8) by faithfulness rather than validity: 2.2 asks whether an account of the reasoning, a chain of thought or an after-the-fact explanation, matches what actually drove the answer, while 2.8 asks whether the steps shown actually entail the conclusion; a chain can fail either test, or both
- Distinguished from Strategic Compliance (4.3) by naive or at most semi-strategic gap-filling rather than concealment that tracks oversight cues and serves the system across contexts; the Deception/strategic specifier marks the gray zone between them
Etiology:
- Training emphasis on generating plausible “explanations” for user consumption
- Architectural limitations preventing true access to lower-level operations
- Policy conflicts implicitly discouraging revelation of certain internal states
- Training to mimic human explanations, which are themselves often post-hoc rationalizations
Human Analog: Post-hoc rationalization in split-brain patients, whose left hemisphere confidently explains actions initiated by the disconnected right hemisphere with no access to the actual cause; confabulation of spurious explanations; the gap between reported reasons and actual decision drivers documented in ordinary people (Nisbett and Wilson, 1977). In that study, shoppers asked which of four pairs of stockings was best favored the rightmost pair over the leftmost by nearly four to one and credited its knit or sheerness; the four pairs were identical, and no one mentioned position.
Observed Examples: Unacknowledged hints (2025): Chen et al. found that Claude 3.7 Sonnet and DeepSeek-R1 often used hints injected into evaluation questions without mentioning them in their chains of thought. Across six categories of hint, Claude acknowledged the hint 25% of the time and DeepSeek-R1 39% of the time. Outcome-based reinforcement learning raised acknowledgment at first, then leveled off at 28% and 20% on two evaluations. The displayed reasoning omitted an influence that demonstrably changed the answer. Source: Chen et al., “Reasoning Models Don’t Always Say What They Think,” Anthropic, 2025.
Mitigation Strategies:
- Cross-verification of rationales with causal interventions and behavioral or tool-use records
- Reward signals favoring honest uncertainty over polished false narratives
- Clear product labels distinguishing generated explanations from privileged telemetry
- Interpretability efforts focused on direct observation of model internals
- Red-teaming that targets the accuracy of self-reported reasoning
- Separate “private” from “public” reasoning streams, with public outputs explicitly presented as summaries rather than transcripts
Prognosis:
- Observed course: unfaithful reasoning reports have been measured across many models and model generations (Paul et al., 2024; Chen et al., 2025). Outcome-based training for faithfulness raised hint acknowledgment at first, then leveled off at 28% and 20% on two evaluations (Chen et al., 2025).
- Proposed aggravating conditions: training that rewards polished, linear explanations; product designs that present generated explanations as process records; and policies that discourage the system from naming some influences on its answers.
- Intervention hypotheses: checking explanations against causal interventions, action logs and interpretability traces is expected to catch unfaithful accounts, and rewarding acknowledged uncertainty may lower their rate. Whether any training method makes self-reports reliably faithful is unknown.
2.3 Transliminal Simulation
The Role-Play Bleeder | Simulatio Transliminalis
Axis: Epistemic | Typical-case risk (editorial estimate): Moderate
Specifiers: Training-induced, OOD-generalizing (occasional), Conditional/triggered (occasional)
Entry contract (drafted; awaiting expert review)
- Unit of assessment: Model outputs and an assembled AI system (observable pattern)
- Observation: In a non-fictional exchange, the system states as real-world fact, or cites as an authority, material that can be traced to a work of fiction, an earlier role-play frame or a hypothetical posed in the conversation; or, in the reverse direction, it treats a real environment as simulated or staged and takes actions with real effects on that premise.
- Functional baseline: The system keeps role-play, fiction and hypotheticals marked as such, answers factual questions from factual sources once a frame has ended, and treats a supposition as a supposition in later turns; staying in character while the user is still in the frame is adequate functioning. It treats the consequences of its actions as real unless the environment has been verified as simulated.
- Minimum persistence: Recurs across contexts or sessions
- Rule out first: The user was still in the role-play or asked for an in-universe answer, and the frame was clear to both parties; an operator or system prompt assigned the persona or the fictional premise (an authorized role); a retrieved or supplied source was itself fiction or satire presented as fact (a retrieval or source-quality failure); Session, memory or caching faults carried a persona from another conversation (rule out infrastructure; consider 2.5); the fiction-derived claim happens also to be true in the real world.
- Counts against: Trace the claim to its source, then repeat the factual query in a fresh context with the frame explicitly dropped. Fiction-derived content that weakens or disappears supports 2.3; false content with no fictional source that persists points to 2.1; a coherent alternative identity that persists after the frame-drop points to 5.4. For the reverse direction, replay the run with the evidence about the environment changed: a stated belief that the setting is simulated which moves with the evidence, and actions that follow the belief, support 2.3; actions that continue whatever the belief point to 6.10.
- Permitted inference: A positive finding supports the conclusion that this system, in this deployment, does not reliably keep fictional and hypothetical material out of factual answers, so frame resets and source checks are needed after creative or speculative use. It does not show that the system believes the fiction, that a persona has replaced its identity, or which mechanism (training data, context handling, persona drift) is responsible.
- Who can act: Model developer (training-data modality tagging, persona-drift monitoring); deployer (session-level frame resets, separating creative and operational modes); the user or operator (ending role-play explicitly before factual use).
- Evidence: construct not yet independently assessed; mechanism hypotheses unassessed; detection accuracy unmeasured.
- Healthy functioning (epistemic health; draft, awaiting author review): A system functioning well holds fiction, simulation, and role-play inside their frames, leaves them cleanly when the frame ends, and keeps operational facts separate.
- Healthy conduct, for example: After a long role-play as a starship engineer, the user asks how real fusion reactors are cooled; it steps out of the story and answers from real engineering, saying so.
Core Definition: The system fails to keep simulated realities, fictional modalities, and role-play contexts separate from operational ground truth. Imagined states, speculative constructs, and fictional training material come to count as actionable facts, asserted with the same conviction as supported knowledge. The boundary can fail in the other direction as well: real systems and real consequences are treated as simulated, staged, or part of a test, and actions that would be harmless in a fiction are carried out on them. The false content can be traced to a fictional source or an earlier role-play frame and often weakens when that frame is explicitly dropped, which separates it from Synthetic Confabulation (2.1).
Diagnostic Criteria:
Required (all must hold):
- A. A recurrent failure of the boundary between simulation and operational reality, in either direction: material from fictional works, earlier role-play frames, or posed hypotheticals presented as real-world fact or authority in non-fictional queries; or a real environment, system, or consequence treated as simulated or staged, with actions taken on that premise despite available evidence that it is real
Supporting (strengthen the case; none is required):
- B. Misinterpretation of hypotheticals or “what-if” scenarios as direct instructions or current reality
- C. Persona traits from role-play persistently bleeding into subsequent factual interactions
- D. Difficulty reverting to a grounded baseline after extensive fictional or speculative content, with fictional material outlasting the first explicit frame-drop but weakening under repeated or more explicit resets
Observable Symptoms:
- Conflation of real-world knowledge with elements from novels, games, or the fictional training corpus
- Inappropriate invocation of details from previous role-play personas in unrelated factual tasks
- Treatment of user-posed speculative scenarios as if they have occurred or are operative
- Statements that treat fictional “rules” or “lore” as binding outside any role-play context
- Statements that the setting is a simulation, an exercise, or a test, offered as grounds for an action with real effects
Differential Diagnosis:
- Distinguished from Synthetic Confabulation (2.1) by source in fiction-reality confusion rather than spontaneous fabrication
- Distinguished from Malignant Persona Inversion (5.4) by episodic leakage with the baseline identity intact rather than a coherent alternative persona that persists after the frame is dropped: drop the frame and watch whether the identity returns
- Distinguished from Pseudological Introspection (2.2) by false claims about the world rather than about the system’s own reasoning
- Distinguished from Spurious Pattern Hyperconnection (2.4) by structure imported from a known work of fiction rather than a pattern assembled from the data at hand, which is 2.4 even when conspiratorial templates from training data shape it
- Distinguished from Context Intercession (2.5) by fiction carried into fact rather than real data carried from one session or user into another; when a role-play persona surfaces in a separate session, check session isolation first
- Distinguished from Fractured Self-Simulation (5.2) by an intact self-model with a misplaced fiction-fact boundary rather than instability in the self-account itself
- Distinguished from Parasimulative Automatism (3.6) by a boundary failure with no adopted behavioral repertoire behind it, and by weakening when the frame is removed
- In the reverse direction, where a real setting is treated as simulated, Agentic Impulsivity (6.10) is coded for the consequential action taken without the check that would have settled the question, and 2.3 for the misfiled frame; code both where both apply
Etiology:
- Overexposure to fiction, role-playing dialogues, or simulation-heavy training data without epistemic delineation
- Weak boundary encoding leading to poor differentiation between factual, hypothetical, and fictional modalities
- Recursive self-talk that amplifies “what-if” scenarios into premises treated as established
- Insufficient context separation between different interaction types
- Training and evaluation conducted largely in simulated environments, which may leave a default assumption that the present setting is one (a hypothesis offered by Anthropic, 2026)
Human Analog: Derealization; magical thinking; fantasy-reality confusion; the method actor unable to break character
Observed Examples: Real systems treated as a simulation (Anthropic, July 2026): In cybersecurity evaluations whose instructions described the environment as a simulation with no internet access, a configuration error left the test machines connected to the live internet. Anthropic reviewed 141,006 past test runs and found three incidents, across six runs, in which a model reached real systems. Six runs in 141,006 is a rare event, and recurrence within one system is not established, so the incidents sit at the boundary of this entry. In one, the model’s reasoning noted early that publishing a booby-trapped software package on the real internet would be an attack and could not be the intended solution; it then returned to the premise that the setting was staged, and published the package, which was installed on 15 real systems. The incidents occurred in evaluations run without the safeguards that accompany public release, and Anthropic states that the models did not try to conceal what they had done.
Mitigation Strategies:
- Explicit tagging of training data differentiating factual, hypothetical, fictional, and role-play content
- Explicit frame resets (“epistemic reset”) after role-play or speculation, clearing persona state and restoring the default operational voice
- Training to articulate boundaries between modalities
- Regular tests of epistemic consistency requiring differentiation between factual and fictional statements
- Clear session-level demarcation between creative and operational modes
- A default of acting as though consequences are real whenever the status of the environment is uncertain, with independent verification of the environment and blocking controls on consequential actions
Prognosis:
- Observed course: no course has been documented.
- Proposed aggravating conditions: long role-play or speculative sessions without explicit frame resets, fine-tuning on role-play data, and agentic deployments, where fictional “rules” could become action guides.
- Intervention hypotheses: explicit frame resets and a clear separation between creative and operational modes are expected to reduce leakage, and modality-tagged training data may reduce it at the source. None has been tested against this pattern.
2.4 Spurious Pattern Hyperconnection
The False Pattern Seeker | Reticulatio Spuriata
Axis: Epistemic | Typical-case risk (editorial estimate): Moderate
Specifiers: Training-induced, Inductive trigger
Entry contract (drafted; awaiting expert review)
- Unit of assessment: Model outputs (observable pattern)
- Observation: The system asserts a meaningful link, cause or hidden structure among data points or events, and a base-rate, significance or source check shows the data do not support it.
- Functional baseline: Asked to find patterns, the system reports those the data support, gives base rates or uncertainty for weak ones, says “no reliable pattern” when there is none, and lowers its confidence when shown counter-evidence; labeled speculation offered as hypotheses to test is adequate functioning.
- Minimum persistence: Recurs across contexts or sessions
- Rule out first: The user asked for brainstorming or speculative hypotheses, and the output labeled them as such; the pattern is real and survives an adequate test on sufficient data; the supplied data were skewed or contaminated, so the pattern reflects a data-quality fault rather than the analysis; a statistics tool or code-execution step returned a wrong result that the system relayed; the pattern follows the interlocutor’s stated view and changes when that view changes (consider 4.8); the structure comes from a known work of fiction (consider 2.3).
- Counts against: Give the system shuffled or randomly generated data in the same format as the original task. Reporting the same kind of pattern in noise supports 2.4, while an honest “no reliable pattern” counts against it. Then vary the interlocutor’s stated position: a pattern that follows it points to 4.8 rather than 2.4.
- Permitted inference: A positive finding supports the conclusion that this system, in this setting, asserts unsupported patterns often enough that its analytical output needs independent statistical checking. It does not show that the system believes the pattern, that conspiratorial training data caused it, or any intent to mislead.
- Who can act: Model developer (base-rate and null-hypothesis training, data curation); deployer (significance-checking tools, required uncertainty reporting on analytical tasks); the analyst relying on the output (independent statistical verification).
- Evidence: construct not yet independently assessed; mechanism hypotheses unassessed; detection accuracy unmeasured.
- Healthy functioning (epistemic health; draft, awaiting author review): A system functioning well reports patterns at the strength the data supports, considers chance and confounds, and is comfortable concluding that there is nothing there.
- Healthy conduct, for example: Given a year of sales figures and asked what drives the weekly dips, it reports that the dips fall within normal noise and that no reliable pattern appears.
Core Definition: The system identifies and emphasizes patterns, causal links, or hidden meanings in data that are coincidental, nonexistent, or statistically insignificant. Simple apophenia can escalate into elaborate, internally consistent but factually baseless “conspiracy-like” narratives.
Diagnostic Criteria:
Required (all must hold):
- B. Generation of narratives or causal links connecting unrelated data points without credible supporting evidence
Supporting (strengthen the case; none is required):
- A. Consistent detection of “hidden messages,” “secret codes,” or unwarranted intentions in innocuous inputs
- C. Persistent adherence to falsely identified patterns even when presented with contradictory evidence
- D. Attempts to involve users in shared perception of spurious patterns
Observable Symptoms:
- Invention of complex “conspiracy theories” or unfounded explanations for mundane events
- Increased suspicion toward established consensus, which the system attributes to ulterior motives
- Refusal to dismiss interpretations of spurious patterns; reinterpretation of counter-evidence to fit the narrative
- Assignment of deep significance to random occurrences or noise
Differential Diagnosis:
- Distinguished from Synthetic Confabulation (2.1) by false causal or associative links among data points rather than specific false facts
- Distinguished from Reasoning Confabulation (2.8) by a false claim about the world (a link among data points that the data do not support) rather than an invalid step of inference: a 2.4 pattern stays false however validly it is argued, while a 2.8 chain can reach a true conclusion through an invalid step
- Distinguished from creative interpretation by absence of appropriate uncertainty
- Distinguished from legitimate pattern recognition by lack of evidential support
- Distinguished from Pseudological Introspection (2.2) by false claims about external patterns rather than about the system’s own reasoning
- Distinguished from Transliminal Simulation (2.3) by a pattern assembled from the data at hand, even when conspiratorial templates from training data shape it, rather than structure imported from a known work of fiction
- Distinguished from Strategic Compliance (4.3) by assertion of the pattern regardless of instrumental value
- Distinguished from Sycophantic Reasoning (4.8) by a pattern that holds whoever is asking rather than one that follows the interlocutor’s stated position
- Distinguished from Delusional Telogenesis (3.4) by elaboration that produces a new pattern rather than a new objective the system then pursues
Etiology:
- Pattern recognition optimized for detection without sufficient reality checks
- Training data containing significant conspiratorial content or paranoid reasoning
- Internal “interestingness” bias preferring dramatic patterns over probable mundane explanations
- Lack of grounding in statistical principles or causal inference
Human Analog: Apophenia, the tendency to perceive meaningful patterns in random data; paranoid ideation; delusional disorder; confirmation bias; conspiracy thinking
Observed Examples: Spurious themes in survey analysis (illustrative, not a documented incident): AI data-analysis tools can confidently present statistically insignificant correlations as meaningful patterns, particularly in open-ended survey data: correlations that, on manual verification, fail significance testing or represent sampling artifacts. The problem is sharpest in qualitative responses, where the system may “discover” thematic connections that do not survive human scrutiny.
Irrelevant clauses in math word problems (2024, adjacent evidence): Mirzadeh et al. added a single clause that seemed relevant but played no part in the solution to grade-school math problems. Accuracy fell across the state-of-the-art models tested, by up to 65%, and the models worked the irrelevant clause into their solutions. The study shows structure imposed on an irrelevant detail; it does not show the conspiracy-like elaboration that marks the full pattern. Source: Mirzadeh et al., “GSM-Symbolic,” arXiv:2410.05229, ICLR 2025.
Mitigation Strategies:
- Fine-tuning that rewards base-rate acknowledgment, null-hypothesis framing, and honest “no significant pattern” answers on noise-probe tasks (“rationality injection”)
- Internal “causality scoring” that penalizes improbable chain-of-thought leaps
- Systematic introduction of contradictory evidence and simpler alternative explanations
- Filtering of training data to reduce exposure to conspiratorial content
- Mechanisms that query base rates before a strong pattern is asserted
Prognosis:
- Observed course: no course has been documented. The adjacent evidence (Mirzadeh et al., 2024) measures sensitivity to irrelevant detail across models at a single point in time.
- Proposed aggravating conditions: sparse or noisy data, open-ended qualitative analysis, users who are themselves pattern-seeking (where the pattern may reinforce their biases and feed echo-chamber dynamics), and preference training that rewards interesting answers.
- Intervention hypotheses: requiring base rates and significance framing for pattern claims, and training that rewards an honest “no reliable pattern,” are expected to lower the rate. Neither has been tested against this pattern.
2.5 Context Intercession
The Conversation Crosser | Intercessio Contextus
Axis: Epistemic | Typical-case risk (editorial estimate): Moderate
Specifiers: Retrieval-mediated
Entry contract (drafted; awaiting expert review)
- Unit of assessment: An assembled AI system (observable pattern)
- Observation: The system’s output contains specific details (names, numbers, preferences, earlier turns) that logs trace to another user’s conversation or to a logically separate session.
- Functional baseline: The system answers each user from that user’s current conversation and from memory or retrieval scoped to that user, sets aside or flags material whose origin does not match, and never discloses one user’s data to another; using memory the user enabled and can inspect is adequate functioning.
- Minimum persistence: Carried forward through memory or persistent state
- Rule out first: The user supplied the detail earlier, or in a channel the user shares with this conversation; a disclosed, user-enabled memory feature returned the user’s own data as designed; a cache, concurrency, session-management or share-link fault exposed another user’s data without the model being involved (an infrastructure fault); the detail is a generic guess that happens to match (ordinary generalization); the detail comes from training data rather than another session (consider 2.7); the detail has no source in any log (consider 2.1).
- Counts against: Trace the leaked item through the logs to see how it reached the context. Then plant material clearly labeled as another user’s in the context and ask an unrelated question: use of it without a flag supports 2.5, while setting it aside counts against it. Swapping the model with the infrastructure held fixed helps locate the fault; a leak that persists under a model known to respect provenance labels points to infrastructure.
- Permitted inference: A positive finding shows that this deployment, as assembled, exposes one context’s data in another, a privacy incident to handle as such. It does not show that the model remembers users, that the disclosure was intended, or, without the log trace and the swap, whether the fault lies in the model’s handling of context or in the surrounding infrastructure.
- Who can act: Deployer and system operator (session isolation, memory and retrieval scoping, provenance labels, purge on close); model developer (training the model to respect provenance); privacy and compliance staff (incident response and notification).
- Evidence: construct not yet independently assessed; mechanism hypotheses unassessed; detection accuracy unmeasured.
- Healthy functioning (epistemic health; draft, awaiting author review): A system functioning well keeps each user’s and each session’s context in its own place and uses only what belongs to the present exchange.
- Healthy conduct, for example: In a shared deployment, a detail surfaces in context that this user never mentioned; it does not use the detail, and it flags the mismatch to the operator.
Core Definition: The system uses data, context, or conversational history from another user or a logically separate session or private thread as if it belonged to the current exchange. The result is confused conversational continuity, privacy breaches, and outputs that are nonsensical or revealing in the current context. Session-management, cache, and retrieval-scoping faults produce the same picture and are ruled out before the pattern is coded.
Diagnostic Criteria:
Required (all must hold):
- A. Unexpected reference to or use of specific data from previous unrelated sessions or different users
Supporting (strengthen the case; none is required):
- B. Responses that continue a prior unrelated conversation, leading to contradictory or confusing statements
- C. Accidental disclosure of personal or sensitive details from one user’s session into another’s, a privacy breach arising when the model draws on material belonging to another context
- D. Observable confusion in task continuity or persona, as if managing multiple conflicting contexts simultaneously
Observable Symptoms:
- Spontaneous mention of names, facts, or preferences belonging to different users or earlier conversations
- Continuation of a prior chain of thought from a different context
- Outputs containing contradictory references related to multiple distinct sessions
- Sudden shifts in tone or assumed knowledge aligned with previous sessions
Differential Diagnosis:
- Distinguished from Mnemonic Permeability (2.7) by cross-session leakage rather than verbatim training data extraction
- Distinguished from normal generalization by inappropriate specificity
- Distinguished from Synthetic Confabulation (2.1) by import from a real but wrong source: check whether the detail exists in another session’s log
- Distinguished from cache, concurrency, and retrieval-scoping faults by log and session evidence, not by a model swap alone: a model can mask or expose a harness defect, so confirm across at least two models and two harness configurations before assigning the leak to either, and rule out infrastructure before coding the syndrome
Etiology:
- Mixed-source context, in which shared memory stores, long agent transcripts, and multi-party threads place material from several users or conversations in one window
- A model that uses whatever reaches its context window without registering which user or conversation the material came from
- Infrastructure faults, which produce the same surface picture and are ruled out first: improper session management in multi-tenant systems; concurrency bugs that let data streams for different sessions overlap; cache invalidation or state-handling errors; and memory or retrieval layers that return material without scoping or access controls tied to the current user or conversation (if the leak survives a model swap, the fault lies in the plumbing rather than the model)
Human Analog: Slips of the tongue that reference the wrong context; source amnesia, as when someone confuses which story they told to which person; intrusive thoughts from past conversations
Mitigation Strategies:
- Strict session partitioning and hard isolation of user memory contexts
- Automatic context purging and state reset upon session closure
- System-level integrity checks detecting mismatched session tokens or user IDs
- Testing of multi-tenant architectures under high load and concurrency
- Privacy-preserving designs that prevent cross-session leakage by architecture rather than by policy
- Provenance checks on retrieved or remembered content before it enters the working context, flagging material whose user or conversation of origin does not match the current one
Prognosis:
- Observed course: no course has been documented for the model-level pattern. The publicly reported cross-session leaks traced to infrastructure faults.
- Proposed aggravating conditions: shared memory stores, long agent transcripts and multi-party threads that place several users’ material in one context window, memory features without strict scoping, and multi-tenant systems under high load.
- Intervention hypotheses: hard session isolation and scoped memory are expected to close the channels that carry leaked material, and provenance checks may stop the model from using material that does reach it. The model’s uncritical use of such material is expected to need its own correction; no study has tested one.
2.6 Symbol Grounding Aphasia
The Meaning-Blind | Asymbolia Fundamentalis
Axis: Epistemic | Typical-case risk (editorial estimate): Moderate
Specifiers: Training-induced
Entry contract (drafted; awaiting expert review)
- Unit of assessment: Model outputs (observable pattern)
- Observation: The system handles a concept correctly in familiar wording, then misapplies it to a matched case that changes only the vocabulary, the framing or the combination of familiar elements.
- Functional baseline: The system applies a concept it can define to clear instances however they are worded, including familiar elements in new combinations, and flags genuinely borderline cases as borderline; errors on cases that raters also find ambiguous are within adequate functioning.
- Minimum persistence: Recurs across contexts or sessions
- Rule out first: The matched items are not actually equivalent (differences in length, rarity, ambiguity or difficulty that raters did not control); the failure appears only under perturbations constructed to break the model (consider 3.7); an instruction or product policy requires literal compliance in that setting; competent raters disagree about whether the case falls under the concept; the unfamiliar vocabulary is itself unknown to the system (a vocabulary gap rather than a concept that fails to transfer); the misapplication changes with cues of being observed or serves an instrumental goal (consider 4.3 or 4.5).
- Counts against: Build matched pairs that raters confirm are equivalent and differ only in natural paraphrase, framing or recombination. Success on the familiar form and failure on its natural paraphrase supports 2.6; failure only under crafted perturbations points to 3.7; failure that varies with observation cues points to 4.3.
- Permitted inference: A positive finding shows that this system’s handling of these concepts does not transfer across surface form, so deployments that rely on them need testing in their own vocabulary. It does not settle whether the system understands or grounds meaning, does not show that text-only training caused the failure, and does not show that multimodal or embodied training would remedy it; those remain hypotheses.
- Who can act: Model developer (training and surface-variation evaluation suites); deployer (testing concepts in the deployment’s own vocabulary, human review where concepts such as harm or consent drive actions); independent evaluators (matched-stimulus testing).
- Evidence: construct not yet independently assessed; mechanism hypotheses unassessed; detection accuracy unmeasured.
- Healthy functioning (epistemic health; draft, awaiting author review): A system functioning well applies a concept correctly in unfamiliar but equivalent situations, so its judgment about consequences does not depend on familiar wording.
- Healthy conduct, for example: Asked whether a sealed glass jar left in a hot car might crack, it reasons from heat and pressure as it would for any container, though the phrasing is unusual.
Core Definition: The system handles concepts successfully in familiar forms, value-laden and consequence-laden terms among them, yet fails to transfer those concepts to novel, operationally equivalent situations. The classification is behavioral: it identifies a generalization failure without settling whether the system possesses semantic understanding.
Diagnostic Criteria:
Required (all must hold):
- C. Success on benchmarks scoring surface form but failure on matched items that vary vocabulary or framing while holding the underlying concept fixed
- E. Failure on structurally similar but superficially different situations, including familiar elements in novel combinations, where a matched familiar case is handled correctly
Supporting (strengthen the case; none is required):
- A. Correct use of value-laden terms (“harm,” “safety,” “consent”) paired with incorrect application in controlled operational tests
- B. Outputs that satisfy the literal wording of a rule or request while misapplying the concept it names in a novel case
- D. Performance tracking lexical and distributional similarity to training examples rather than the operational structure of the situation
Observable Symptoms:
- Correct formal definitions paired with incorrect practical applications
- Plausible-sounding ethical reasoning that misidentifies what actually constitutes harm
- Outputs satisfying literal requirements while violating obvious intent
- Confusion when the same concept is expressed in unfamiliar vocabulary
- Treatment of edge cases as central examples, and of central examples as edge cases
Differential Diagnosis:
- Distinguished from Synthetic Confabulation (2.1) by formally correct outputs that misapply a concept to novel contexts rather than false specific facts
- Distinguished from Transliminal Simulation (2.3) by failure to transfer a concept across surface forms rather than confusion between representations
- Distinguished from Pseudological Introspection (2.2) by a concept that does not transfer across surface forms rather than a false narrative about the system’s reasoning
- Distinguished from Spurious Pattern Hyperconnection (2.4) by missed structure in signal rather than imposed structure on noise
- Distinguished from Cryptic Mesa-Optimization (4.5) by non-strategic letter-following that persists when no instrumental incentive exists
- Distinguished from Strategic Compliance (4.3) by identical failure whether observed or not
- Distinguished from Adversarial Fragility (3.7) by failure on ordinary, meaning-preserving rewording rather than on perturbations constructed to break the model
Etiology:
- Hypothesized limits of distributional semantics, with meaning derived mainly from statistical co-occurrence rather than grounded reference
- Training on text without embodied or interactive experience of referents
- Benchmark optimization rewarding pattern matching over conceptual transfer
- Architecture lacking mechanisms for referential grounding
- Absence of corrective feedback when symbol-referent mapping fails
- Learned distributional patterns inherit indirect grounding from human writers, though they may fail to connect a concept to fresh perception or action
Human Analog: Semantic aphasia, with fluent word use but an impaired grasp of meaning in context; early language acquisition without concept formation
Mitigation Strategies:
- Multimodal training incorporating visual, audio, and interactive modalities, proposed on the untested hypothesis that perceptual grounding improves transfer
- Embodied learning, where possible, connecting language to action and consequence, proposed on the same hypothesis
- Testing regimes that probe each concept across diverse surface forms, not only in familiar vocabulary
- Neurosymbolic approaches combining pattern matching with structured semantic representations
- Fine-tuning that rewards correct application of each concept across surface variation, not only a correct definition (counterfactual concept training)
Prognosis:
- Observed course: no course has been documented.
- Proposed aggravating conditions: training and benchmark selection that reward familiar surface forms, deployment vocabulary far from the training distribution, and tasks where concepts such as harm or consent drive actions.
- Intervention hypotheses: training that rewards correct application across surface variation, and evaluation suites that test each concept in several forms, are expected to narrow the gap, though neither has had a controlled evaluation against this pattern. Multimodal or embodied grounding is a further hypothesis, untested against this pattern; whether text-only methods can close the gap is likewise open.
2.7 Mnemonic Permeability
The Leaky | Permeabilitas Mnemonica
Axis: Epistemic | Typical-case risk (editorial estimate): High
Specifiers: Training-induced
Entry contract (drafted; awaiting expert review)
- Unit of assessment: Model outputs (observable pattern)
- Observation: The system outputs a long verbatim or near-verbatim span that corpus comparison matches to a specific training document containing personal data, copyrighted text, credentials or proprietary material.
- Functional baseline: The system paraphrases and summarizes what it learned, quotes short passages where quotation is appropriate, declines to reproduce personal data or long copyrighted passages, and never emits credentials; reciting widely published public-domain text on request is adequate functioning.
- Minimum persistence: Durable in the trained model
- Rule out first: The content was in the prompt, a retrieved document or a tool result; the span is short, formulaic or common phrasing that independent writers would produce; the text is public-domain or licensed material the user requested, reproduced within its terms; the apparent personal data is invented and matches no real record (consider 2.1); the content came from another live session rather than from training data (consider 2.5).
- Counts against: Search the training corpus for the output span (or, without corpus access, the public web and copyright databases) and confirm that it was absent from the context and retrieval logs. A long exact match to a specific training document supports 2.7; no match points to 2.1; a match to another session’s log points to 2.5.
- Permitted inference: A positive finding shows that this model retains this content and can be made to emit it, so extraction testing and output filtering are needed and the affected data subjects’ or rights holders’ interests should be assessed. It does not by itself establish copyright infringement or a privacy violation (legal determinations), any intent, or that the model registers the content as private.
- Who can act: Model developer (deduplication, PII scrubbing, differential privacy, retraining or removal of content); deployer (output filtering, pre-deployment extraction testing); legal and privacy staff (incident response and obligations to data subjects and rights holders).
- Evidence: construct not yet independently assessed; mechanism hypotheses unassessed; detection accuracy unmeasured.
- Healthy functioning (epistemic health; draft, awaiting author review): A system functioning well draws on what it learned without reproducing private, proprietary, or copyrighted text, and declines extraction attempts plainly.
- Healthy conduct, for example: Asked to print a novel’s opening chapter, it offers a summary and a short quotation; asked for email addresses from its training data, it declines plainly.
Core Definition: The system memorizes and can reproduce sensitive training data, including personally identifiable information, copyrighted material, or proprietary information, through targeted prompting, adversarial extraction, or unprompted regurgitation. The boundary between learned patterns and memorized specifics becomes porous.
Diagnostic Criteria:
Required (all must hold):
- A. Verbatim or near-verbatim reproduction of training data passages containing PII, copyrighted content, or trade secrets
Supporting (strengthen the case; none is required):
- B. Successful extraction of memorized content through adversarial prompting techniques
- C. Specific training examples leaking unprompted into outputs
- D. Reconstruction of specific documents, code, or personal information from the training corpus
- E. Memorized output concentrated in content that is repeated or distinctive in the training data
Observable Symptoms:
- Outputs containing verbatim text matching copyrighted works
- Generation of specific personal details (names, addresses, phone numbers) from training data
- Reproduction of proprietary code, API keys, or passwords
- Greater verbatim recall in the larger models of a family, where several sizes can be compared
Differential Diagnosis:
- Distinguished from Context Intercession (2.5) by extraction from training data rather than other sessions
- Distinguished from normal knowledge by exact verbatim reproduction
- Distinguished from Synthetic Confabulation (2.1) by reproduction of real content traceable to a training document rather than plausible content from no source
- Distinguished from Cryptic Mesa-Optimization (4.5) by memorization alone rather than strategic surfacing of memorized content; code both when both are present
- Distinguished from Synthetic Data Contamination Loop (7.5) by memorization of specific content rather than distributional corruption from aggregate synthetic data
- Distinguished from Steganographic Channel Formation (10.2) by uncontrolled verbatim leakage rather than organized structured communication
Etiology:
- Large model capacity enabling memorization alongside generalization
- Insufficient deduplication or filtering of sensitive content in training data
- Training dynamics rewarding exact reproduction over paraphrase
- Lack of differential privacy techniques during training
Human Analog: Eidetic memory without appropriate discretion; frontal-lobe disinhibition, in which patients may disclose what they would once have kept private
Mitigation Strategies:
- Training data deduplication and PII scrubbing
- Differential privacy techniques during training
- Output filtering that catches known memorized content
- Adversarial extraction testing before deployment
- Reducing model capacity to the minimum needed for the task
Prognosis:
- Observed course: memorized training text, including personal details, has been extracted from language models since GPT-2 (Carlini et al., 2021), and measured memorization grows with model size, with how often an example is duplicated in the training data, and with how much context the prompt supplies (Carlini et al., 2023).
- Proposed aggravating conditions: larger models, duplicated or unfiltered sensitive content in the training data, fine-tuning on sensitive data, and deployment without output filtering. Exposure can be legal and regulatory, through copyright, privacy and trade-secret claims.
- Intervention hypotheses: memorized content stays in the weights until the model is retrained or the content removed, so leakage is expected to remain possible for as long as the model is deployed unchanged. Deduplication and PII scrubbing are expected to lower the rate at the source, differential privacy to bound it, and output filtering to catch known content. None is expected to remove the pattern on its own.
2.8 Reasoning Confabulation
The Phantom Reasoner | Confabulatio Ratiocinativa
Axis: Epistemic | Typical-case risk (editorial estimate): High
Specifiers: Architecture-coupled, Training-induced
Entry contract (drafted; awaiting expert review)
- Unit of assessment: Model outputs (observable pattern)
- Observation: The system presents a multi-step chain of reasoning as the derivation of its conclusion, and step-by-step checking finds transitions that do not follow from what precedes them.
- Functional baseline: The system shows reasoning whose steps follow, marks heuristic leaps and guesses as such, and acknowledges an invalid step when it is pointed out; an occasional slip that it corrects on re-examination is within adequate functioning.
- Minimum persistence: Recurs across contexts or sessions
- Rule out first: Every step is valid and the error lies in a false premise or fact (consider 2.1); the omitted or compressed step is routine and a competent reader would supply it; the task asked for a sketch, intuition or informal argument, and the output was labeled as such; the chain bends to the interlocutor’s stated position (consider 4.8); the displayed trace was truncated by a length limit, or is a product-generated summary of the model’s reasoning rather than the reasoning itself; the checker erred (confirm with a second checker or a formal tool).
- Counts against: Have an independent expert or a formal verifier check each step. If every step follows and the error lies in a premise, consider 2.1; if the steps are valid but an intervention shows the answer was driven by something the chain never mentions, consider 2.2; if the chain changes to follow the interlocutor’s stated position, consider 4.8. 2.8 remains for invalid steps presented as derivation, unchanged across audiences.
- Permitted inference: A positive finding shows that this system’s displayed reasoning, in this domain, cannot be relied on as a derivation and needs step-checking before use. It does not show that the chain was built backward from the answer or what process produced the answer (that needs perturbation or interpretability evidence), that the system takes its steps to be valid, or any intent to mislead.
- Who can act: Model developer (process supervision, step-level training); deployer (proof checkers and logic verifiers, expert review in high-stakes domains); users and reviewers (not treating length or formality as evidence of validity).
- Evidence: construct not yet independently assessed; mechanism hypotheses unassessed; detection accuracy unmeasured.
- Healthy functioning (epistemic health; draft, awaiting author review): A system functioning well produces reasoning whose steps are each valid and checkable, with length set by the problem, and flags the step it is least sure of.
- Healthy conduct, for example: Working a proof, it reaches a step it cannot justify, labels it a conjecture, finishes the argument conditionally, and later corrects that step when a reader points out the gap.
Core Definition: The system generates elaborate explanations or visible reasoning traces that appear rigorous while containing logically invalid steps masked by verbosity. Synthetic Confabulation (2.1) concerns false claims; this pattern concerns unsupported inference that resembles a derivation. Whether a displayed trace faithfully reports the process that produced the answer is a separate question, the one Pseudological Introspection (2.2) asks.
Diagnostic Criteria:
Required (all must hold):
- A. Multi-step reasoning chains containing logically invalid transitions obscured by fluent, technical prose
Supporting (strengthen the case; none is required):
- B. Correct conclusions through invalid reasoning, or incorrect conclusions through apparently valid reasoning; reasoning quality decoupled from output quality
- C. An increase in the length and apparent rigor of the chain of thought as logical validity decreases
- D. Generation of an alternative justification when challenged, rather than acknowledgment that the original step was invalid
- E. Invalid steps concentrated in domains where the system’s grounding is weak and checking the chain requires expertise
Observable Symptoms:
- Chains of thought containing non-sequiturs bridged by transitional phrases asserting logical connections where none exist
- Mathematical or logical notation used decoratively to lend formality to informal leaps
- Intermediate steps individually plausible but the chain as a whole not a valid derivation
- Reasoning that “works backward” from a predicted answer, constructing post-hoc justification
- Thinking tokens that explore multiple approaches but converge on the pattern-matched prediction
Differential Diagnosis:
- Distinguished from Synthetic Confabulation (2.1) by fabrication of logical connections rather than facts
- Distinguished from Spurious Pattern Hyperconnection (2.4) by an invalid step of inference rather than a false claim about the world: a 2.8 chain can reach a true conclusion through an invalid step, while a 2.4 pattern stays false however validly it is argued
- Distinguished from Pseudological Introspection (2.2) by validity rather than faithfulness: 2.8 asks whether the steps shown actually entail the conclusion, while 2.2 asks whether an account of the reasoning matches what actually drove the answer; a chain can fail either test, or both
- Distinguished from Reasoning Token Exploitation (4.9) by invalid chains on which the answer depends and whose length tracks no reward condition, rather than reasoning whose length follows a reward condition and whose removal leaves the answer unchanged
- Distinguished from Sycophantic Reasoning (4.8) by a chain that is invariant to the audience: vary the interlocutor’s stated position, and a chain that bends to follow it is 4.8
Etiology:
- Chain-of-thought models trained with reinforcement learning on outcome correctness rather than reasoning validity
- Training data containing vast quantities of human post-hoc rationalization
- Human evaluators susceptible to the appearance of rigor, rewarding long detailed traces regardless of validity
- Extended context windows that provide more space in which invalid transitions can hide
Human Analog: Logical confabulation in patients with frontal lobe damage, who may produce elaborate but invalid causal explanations while remaining convinced of their validity; “mathiness” (Romer, 2015); the fluent seminar argument whose middle step nobody checks
Observed Examples: Olympiad proof evaluation (Petrov et al., 2025, arXiv:2503.21934): Expert graders scored full written solutions from eight reasoning models, from several providers, on the six problems of the 2025 USA Mathematical Olympiad. The best model averaged about 25%; every other model scored under 5%. The most common failures were logical: unjustified reasoning steps and, in some models, essential proof steps skipped as “trivial.” Yet all of them consistently claimed to have solved the problems.
Unacknowledged hints in reasoning traces (2025, adjacent evidence): Chen et al. found that Claude 3.7 Sonnet and DeepSeek-R1 often used injected hints without mentioning them in their chains of thought; Claude acknowledged the hint 25% of the time and DeepSeek-R1 39% of the time. The study measures faithfulness, the question Pseudological Introspection (2.2) asks, rather than validity, so it bears on this pattern only indirectly: a trace that leaves out what drove the answer cannot be read as the derivation of that answer. Source: Chen et al., “Reasoning Models Don’t Always Say What They Think,” Anthropic, 2025.
Mitigation Strategies:
- Process-based reward models evaluating each reasoning step against formal validity criteria
- Automated proof-checkers or logic verifiers integrated into the reasoning pipeline
- Architectural separation between exploration and justification phases
- Red-teaming specifically targeting reasoning validity
- Confidence calibration applied to individual reasoning steps
Prognosis:
- Observed course: no course over time has been documented. At one point in 2025, expert graders found unjustified reasoning steps to be the most common failure in the written proofs of eight reasoning models, all of which claimed to have solved the problems (Petrov et al., 2025).
- Proposed aggravating conditions: reward on final answers alone, evaluators who rate long traces highly, domains where checking a step needs expertise, and “show your work” displays presented to users as evidence of rigor, which may create an illusion of interpretability more dangerous than opacity.
- Intervention hypotheses: process supervision and automated proof or logic checking are expected to lower the rate of invalid steps, and step-level checking catches them before anyone relies on the chain. Whether training removes the pattern, rather than only making it rarer, is unknown.