HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
BraveAnn011
ai-halo-valuation-bias
Python2026–2026
BraveAnn011 / ai-halo-valuation-bias

ai-halo-valuation-bias

Context halo in VLM valuation of an identical low-cost necklace across six models (1,164 sessions). Paper: arXiv:2610.34591

2Distinct people
3Mentions
0Explicit recommenders
4GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Context halo in VLM valuation of an identical low-cost necklace across six models (1,164 sessions). Paper: arXiv:2610.34591

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by day3 dated mentions

Observed mentions: 2026-07-28 13:07:40 UTC to 2026-08-18 19:39:23 UTC.

0122026-07-28 00:00:00 UTC to 2026-07-29 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsJul 282026-07-29 00:00:00 UTC to 2026-07-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-30 00:00:00 UTC to 2026-07-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-31 00:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-01 00:00:00 UTC to 2026-08-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-02 00:00:00 UTC to 2026-08-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-03 00:00:00 UTC to 2026-08-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-04 00:00:00 UTC to 2026-08-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-05 00:00:00 UTC to 2026-08-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-06 00:00:00 UTC to 2026-08-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-07 00:00:00 UTC to 2026-08-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 72026-08-08 00:00:00 UTC to 2026-08-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-09 00:00:00 UTC to 2026-08-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-10 00:00:00 UTC to 2026-08-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-11 00:00:00 UTC to 2026-08-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-12 00:00:00 UTC to 2026-08-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-13 00:00:00 UTC to 2026-08-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-14 00:00:00 UTC to 2026-08-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-15 00:00:00 UTC to 2026-08-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-16 00:00:00 UTC to 2026-08-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-17 00:00:00 UTC to 2026-08-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-18 00:00:00 UTC to 2026-08-19 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 18

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jul 282026-07-28 00:00:00 UTC2026-07-29 00:00:00 UTC211
Jul 292026-07-29 00:00:00 UTC2026-07-30 00:00:00 UTC000
Jul 302026-07-30 00:00:00 UTC2026-07-31 00:00:00 UTC000
Jul 312026-07-31 00:00:00 UTC2026-08-01 00:00:00 UTC000
Aug 12026-08-01 00:00:00 UTC2026-08-02 00:00:00 UTC000
Aug 22026-08-02 00:00:00 UTC2026-08-03 00:00:00 UTC000
Aug 32026-08-03 00:00:00 UTC2026-08-04 00:00:00 UTC000
Aug 42026-08-04 00:00:00 UTC2026-08-05 00:00:00 UTC000
Aug 52026-08-05 00:00:00 UTC2026-08-06 00:00:00 UTC000
Aug 62026-08-06 00:00:00 UTC2026-08-07 00:00:00 UTC000
Aug 72026-08-07 00:00:00 UTC2026-08-08 00:00:00 UTC000
Aug 82026-08-08 00:00:00 UTC2026-08-09 00:00:00 UTC000
Aug 92026-08-09 00:00:00 UTC2026-08-10 00:00:00 UTC000
Aug 102026-08-10 00:00:00 UTC2026-08-11 00:00:00 UTC000
Aug 112026-08-11 00:00:00 UTC2026-08-12 00:00:00 UTC000
Aug 122026-08-12 00:00:00 UTC2026-08-13 00:00:00 UTC000
Aug 132026-08-13 00:00:00 UTC2026-08-14 00:00:00 UTC000
Aug 142026-08-14 00:00:00 UTC2026-08-15 00:00:00 UTC000
Aug 152026-08-15 00:00:00 UTC2026-08-16 00:00:00 UTC000
Aug 162026-08-16 00:00:00 UTC2026-08-17 00:00:00 UTC000
Aug 172026-08-17 00:00:00 UTC2026-08-18 00:00:00 UTC000
Aug 182026-08-18 00:00:00 UTC2026-08-19 00:00:00 UTC101

What Hacker News says

3 sources
I posted a GitHub repo recently :https://github.com/BraveAnn011/ai-halo-valuation-bias It started with a simple question, and I thought it was done. But now I think it is not that easy. What made the model change its answer??? Yes, I can easily answer: AI is affected by biased cues. The more I look at this experiment, the less interested I am in the necklace itself. The part I can't explain is this: AI overpriced itself even for Stimuli #4 (necklace itself without Human, testing default setting) Back to my simple answer: Yes, I can answer easily AI is affected by biased cues. --> why did AI use Information You Never Intended It to use? That is where I think the interesting research question starts. There is already a fairly large literature on LLMs showing context-sensitive judgment: anchoring, framing effects, user-belief influence/sycop
Read the rest
hancy, etc. But most anchoring experiments give the model an explicit anchor—usually a number, prior answer, or “expert” opinion. In my experiment, there was no explicit price anchor. Instead, the context was something like: same necklace + formal setting same necklace + casual/recycling-yard setting The model was free to decide what information mattered. So I'm curious about the technical interpretation: What representation is changing when the object stays constant but the model's valuation changes? How does AI decide which information to use or not?
In [dead]

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.