Skip to content

fix(skill): sold comps — never price-cap the sold search, read the card, Zestimate optional - #1

Merged
therohitdas merged 1 commit into
mainfrom
fix/sold-comps-no-price-cap
Sep 7, 2026
Merged

fix(skill): sold comps — never price-cap the sold search, read the card, Zestimate optional#1
therohitdas merged 1 commit into
mainfrom
fix/sold-comps-no-price-cap

Conversation

@therohitdas

Copy link
Copy Markdown
Collaborator

Fixes the collapsed comp pool: the agent applied the buyer price cap to the SOLD search and leaned on the Zestimate in low-coverage markets (Phoenix ~22%, Austin ~42%). Doc-only; no valuation-math change.

…rd, Zestimate optional

The scanner's comp pool was collapsing to 1-3 records because the agent applied
the buyer's price cap to the SOLD search (filtering out sold homes above the
buyer's budget — the very evidence that establishes area value) and leaned on the
Zestimate in low-coverage markets (Phoenix ~22%, Austin ~42%).

- New "Sold comparisons" section makes two rules unmissable: never apply the
  buyer's price cap to the sold search (area + bedroom band only), and read the
  closed price / sale date / living area straight off the SOLD card
  (unformattedPrice + dateSold + livingArea) — no per-comp detail lookup needed.
- Zestimate reframed as an optional cap, not a gate; its absence is expected.
- Step 2 corrected: only active homes need a detail fetch; sold comps do not.

No behavior change to the valuation math (scanning.md already treats the Zestimate
as an optional cap); this fixes how the agent gathers the sold-comp pool.

Co-Authored-By: CRHQ <noreply@crhq.ai>
@therohitdas
therohitdas merged commit ba1acfe into main Sep 7, 2026
2 checks passed
@therohitdas
therohitdas deleted the fix/sold-comps-no-price-cap branch September 7, 2026 13:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants