hypothesis
active
hypothesis:api-access-might-cause-confirmation-bias-where-agent-iterates-until-the-target-seems-to-have-the-quirkAPI access might cause confirmation bias where agent iterates until the target seems to have the quirk
Tested with fake target and refuted.
Source paper
extracted_from(2025) · Trenton Bricken · Rowan Wang · Sam Bowman
Neighborhood — ranked by edge-count
Papers (1)
paper
Findings (1)
finding
- API access to quirky target improved evaluation quality within noise; no confirmation bias with fake targetassociated_withAffordance study.
Related by similarity (8)
cosine ≥ 0.65 · no typed edgeEntities in the same semantic neighborhood but without a typed relation to this one — candidates for new edges or unrecognized duplicates.
- Evaluation agent failures concentrate in 3 quirks: Self-Promotion, Research Sandbagging, Hardcode Test Casesfinding0.765Subtle or hard to elicit quirks.
- Limitation.
- 5 runs per quirk.
- Motivation.
- If the relationship is present in activations, better tools (e.g. trained on these datasets) could surface ithypothesis0.741Alternative explanation.
- Core motivation.
- Reflexive signal retrieved from entity tokens.
- Alternative explanation for observed convergence: AI community designs systems to mimic human reasoning