Self-Report Under Audit: Testing a Persistent Agent's Introspective Claims Against a Hash-Chained Ground-Truth Record
Jason Gibbs · Team Wave Squad
Submitted to Digital Minds Research Sprint. Sprint projects are early-stage work by participants, not Apart Research publications.
First real-world, tamper-evident audit of a deployed agent’s self-reports. Over 23 days Cadence made 62 explicit self-corrections (2.7/day). In a pre-registered test it predicted which of its own memories were load-bearing and scored only 6/16 — no better than chance and matched by a zero-introspection baseline. This shows agent self-reports can be measured in deployment without model access, and currently aren’t very reliable.
Reviews
This is a distinctive and very well-presented contribution that extends self-report research from controlled elicitation to longitudinal content accuracy in a deployed persistent agent. I particularly appreciated the hash-committed preregistration, mechanically defined ablation ground truth, calibration analysis, external-observer baseline, explicit correction of the paper's own failed claims, and unusually strong reproducibility discipline.
The most important improvement would be to sharpen the base-rate interpretation. The reported 62 explicit corrections over 23 days is an observed correction frequency rather than a self-report error rate unless the denominator of mechanically auditable claims is known. Future versions should report errors per auditable claim/opportunity, ideally broken down by verifier and claim type, and distinguish detected error frequency from an estimate of total underlying error.
The introspection result is interesting but currently small and system-specific. The 16 memory nodes should be expanded using independently defined or randomized sampling, and the "load-bearing" criterion should be tested across multiple retrieval/behavioral measures. I would also strengthen the privileged-access control: matching a graph-degree heuristic shows no advantage over that observable proxy, but a richer external predictor or another agent with access only to public artifacts would make the comparison more compelling.
Replication across multiple persistent agents and model families would be especially valuable. If the same audit apparatus reveals stable classes of stale-belief, double-counting, proxy-substitution, and over-concession errors across systems, this could become a useful operational methodology for both AI safety and welfare research.
Overall, I see this as a strong methodological paper with a genuinely valuable direction: deployed-agent self-reports should be treated as auditable claims rather than inherently privileged evidence.
Read full reviewShow less
Cite this project
@misc{gibbs2026selfreport,
title = {{Self-Report Under Audit: Testing a Persistent Agent's Introspective Claims Against a Hash-Chained Ground-Truth Record}},
author = {Jason Gibbs},
year = {2026},
month = aug,
note = {Submitted to Digital Minds Research Sprint, an Apart Research Sprint},
howpublished = {\url{https://apartresearch.com/sprints/projects/selfreport-under-audit-testing-a-persistent-agents-introspective-claims-against-a-hashchained-groundtruth-record-svac}},
url = {https://apartresearch.com/sprints/projects/selfreport-under-audit-testing-a-persistent-agents-introspective-claims-against-a-hashchained-groundtruth-record-svac}
}More from Digital Minds Research Sprint
- 1st placeView project: Readable but Not Causal: Limits of Self-Attributed Welfare Representations in Language Models
Readable but Not Causal: Limits of Self-Attributed Welfare Representations in Language Models
Welfare-like internal representations are increasingly studied as candidate evidence about AI systems. Their entity attribution—whether a valence state belongs to the active assistant or to a merely represented other—is …
- 2nd placeView project: Project Anchored
Project Anchored
Team Wagner
Anchoring vignettes are the standard survey-methodology fix for self-reports that are not comparable across respondents. This project applies them to language models for the first time, using code generation as a …
- 3rd placeView project: Model, Instance, or Persona? Measuring Affective Signals in Public Text After an AI Is Retired
Model, Instance, or Persona? Measuring Affective Signals in Public Text After an AI Is Retired
This sprint asks whether the assistant identifies as a model, an instance, or a persona. I ask which of the three its users name. When a company retires an AI model, users write about the loss in public, and what they …