Curb Answer Coach — which questions the talking yard sign fumbled
Sign in with a staff account to view the Answer Coach.
The Answer Coach pack isn’t applied yet — apply db/2026-07-31_0011_curb-coach-staged.sql, then reload.
Collection is dark. config.curb_feedback is {"enabled": false}, so no misses and no thumb votes are being recorded — the counts below are history only (or zeros on a fresh rail). The houses answer buyers exactly as they do today, and the fact editor below still works: fix a fumble now, and it’s live the moment the switch flips.
The curb rail itself is dark. config.curb is off — no house is answering, so nothing new can be fumbled.
Fumble ranking — last 28 days
A fumble is a miss (the house had no curated answer and fell back to bare listing data) or a buyer’s thumbs-down. Tap a listing to see which topics it fumbles — then teach it the answer.
No fumbles recorded in this window — either the sign is doing great, or collection hasn’t started yet.
—
Fumbled topics
Bars count miss + per topic; rides along on the right. Tap a topic to load it into the editor below.
Teach the house — curated fact editor
preview confirm apply, like the Deadlines panelCurated facts override the MLS feed word-for-word (curb_topics()): set the key to the fumbled topic’s name and the house speaks your line next scan. A blank value removes the key. Nothing writes until you apply a previewed change.
—
Aggregate topics only. Every count on this page is a topic-name tally from pure_curb_events (five columns: id, slug, kind, topic, ts) — no buyer identity, contact, or question text exists anywhere on this rail. The facts you edit here are the operator’s own script for the house.
Pure MLS Tech · Acquisto Real Estate · Answer Coach over mcp_curb_coach_status / mcp_curb_fact_set (previewapply, audited) · dark behind config.curb_feedback · * = capped: misses count per TOPIC while questions count once, so one fumbled multi-topic question can out-count its ask ·