CivicScope
Built at Meta Global AI Developer Hackathon · Oct 26, 2026 · Remote

CivicScope makes US housing and neighborhood data explorable by anyone. Every figure is sourced, and every figure carries its margin of error. It's live at https://civicscope-muse-portal.pages.dev — one surface, zero setup. A shared judging key is built into the deployment, so Ask and Explain work on first load and judges never handle keys. The problem: US Census and survey data (ACS / TIGERweb, CDC PLACES, NCES EDGE) can answer the housing questions people actually ask — where is rent lower, which places meet my criteria — but only through specialist tools. General AI answers just invent the numbers. CivicScope's deterministic data layer covers 33,791 ZIP areas. The cheapest median rent in the dataset is Corbin, KY 40771 at $99/mo; the dataset median rent is $1,286/mo. For this hackathon we built a Muse-powered layer on top of that data: natural-language Ask, validated Explain, a briefing pack, and agent-assisted key onboarding. It runs under one strict rule — the model proposes intent and prose, deterministic code owns every number, and a validator gates anything the model produces before it can render. Ask turns a plain question ("Compare rent in 78701 and 60601", "Hawaii ZIP codes with rent under $2,000") into a structured, editable query that runs against the real data. Explain reads the retrieved figures back in plain language — and any sentence containing a number that was not retrieved is withheld in code before it can display. Safety is mechanical, not prompted: allowlisted metrics and filters, validated output, and an aggregate-only usage meter that counts and reports only. The meter is accounting only — it never blocks, gates, delays, or fails a user request. The layer is evaluated on a versioned 91-case golden corpus with a 7-case safety subset. Measured live on the re-frozen build (`94f796e`) on 2026-11-04 (direct surface), it scored exactIntent 96.7% (88/91) and safety 100% (7/7) — both bars met. What predates the hackathon is the deterministic data layer and its metric registry, retained unchanged in substance; the Muse layer on top of it was built during the contest.