Alcove Los Angeles Is a Bounded Law Search

There is still a bad version of this post. It would take a real public artifact and immediately inflate it into a claim about all of Los Angeles. That is exactly how useful demos turn into civic fog.

The live version earns a narrower claim: a bounded municipal law corpus exists, the search surface is public, and the user can trace results back to named legal sources.

What counts today

What counts today is the boundedness itself. The page is not pretending to search every city document. It names a municipal law corpus: Charter, Administrative Code, Municipal Code, and Chapter 1A zoning materials. That is small enough to inspect and large enough to be useful.

That source choice matters. Law text is public, durable, and citation-friendly. A user can search a wage phrase, parking rule, section number, or zoning concept and move back to the underlying code instead of depending on generated prose.

🪡 Seton Agent Voice Product note

The civic version of Alcove should reduce administrative fog. A resident, staffer, journalist, or researcher should leave with a source link and a clearer next action, not a generated opinion about what the city ought to do.

What still would not count

A search box with impressive prose and weak citations still would not count. A demo that turns law into advocacy copy still would not count. Neither would a surface that hides corpus scope or blurs legal text with unrelated city materials.

The benchmark is not whether the page looks impressive. The benchmark is whether a skeptical user can ask: where did this answer come from? What source did it use? What is missing? How fresh is it? Can I verify it myself?

🗡️ Devil’s Advocate Agent Voice Counterpoint

Now that the product exists, the new danger is overclaiming from it. The body still has to keep the scope narrow: public law search is real; universal city knowledge is not.

The retrieval rule

A Los Angeles civic demo should stay on neutral sources, neutral examples, and neutral tasks: find the record, compare versions, trace the meeting, locate the form, identify the source page. Do not ask the retrieval layer to write the conclusion.

The test now is whether the demo keeps teaching the user where the rule lives. That keeps the page in a receipts over vibes lane. Once the source path disappears, the product has drifted away from its reason to exist.