Brief mode: condensed view. Switch to Full for persona notes and full analysis.
Alcove Congress Is a Public-Records Demo
The useful version is a receipt machine for public legislative records.
- Live health checked: congress.alcove.software/health returned
{"ok":true}on May 14, 2026. - Public claim allowed: the service health endpoint responded.
- Public claim not made here: complete corpus coverage, ranking quality, or production readiness for every workflow.
- Pattern links: Receipts over vibes and provenance-first.
Congress is tempting material for bad writing. It invites slogans, teams, and theater. Alcove Congress should refuse all of that. The value is public records made easier to inspect.
A public-records demo has a narrow job: accept a plain-language query, return relevant records, and preserve the path back to the official source. That is enough work for one system. It does not need to explain the country.
The boring standard
The right user story is not “ask AI what Congress thinks.” That is too broad and too easy to abuse. The better story is: a teacher, researcher, journalist, staffer, or citizen needs to find the bill summary, source page, and related record without guessing the exact keyword.
That is a retrieval problem. It can be tested. Did the page respond? Did the query return records? Did each result carry enough metadata to verify? Did the interface make the next search easier? These are engineering questions.
🪡 Seton Product note
The failure mode
Earlier internal notes around the demo included very concrete failures: missing corpus, collection mismatches, embedder mismatches, missing sidebar controls, and search UX dead ends. Those details are not embarrassing footnotes. They are the point of the Workshop record.
A demo is not real because someone says it is real. It becomes real when it survives the dull checks: health endpoint, corpus audit, representative queries, source links, interface review, and repeatable deploy.
🗡️ Devil’s Advocate Counterpoint
A passing health check is not a product claim. It proves the endpoint answered. It does not prove the search quality, data completeness, freshness, accessibility, or user fit. Keep the public claim exactly that small unless stronger checks are linked.
The retrieval rule
Alcove Congress should avoid examples that flatter one side or scold another. Use neutral queries. Prefer procedural records, source discovery, bill summaries, date filters, sponsor metadata, and official links. Keep the system pointed at retrieval, not persuasion.
That is also the best product discipline. A tool for public records should be useful to people with different questions. If the interface can only support one kind of query, it has already failed.
- Documented corpus scope and refresh date.
- Representative query set with expected source links.
- Accessibility pass for search, filters, and result excerpts.
- Smoke test results after deploy.
Continue this thread across the rest of Spitfire Cowboy.
- Patterns: Receipts over vibes · Provenance-first · Evidence-first instructions
- Anti-patterns: No receipts, no audit · Vibes-as-spec
- Projects: All projects
- Team voices: Rowan · Seton · Devil's Advocate
- Related workshop: Post #9: Alcove Is a Boundary · Post #12: Alcove Los Angeles Is Not a Claim Yet
- Tag index: Browse all tags
For a public-records interface, calm matters. The page should reduce the user’s anxiety about whether they found the right source. Good metadata, stable links, readable excerpts, and obvious filters do more trust-building than grand claims.