Zero-input case tracking where the state gives you nothing

Courts publish case statuses, orders, and cause lists — the day's hearing schedule — on public websites built for a different decade. There is no API, no notification, no way to say 'tell me when my case moves'. A lawyer with forty live matters checks each one by hand, or pays a junior to, or misses something.

Missing something has a special cost in litigation: an unnoticed listing means an unprepared appearance or an absent one. The stress isn't the work; it's the permanent low-grade fear of the unchecked page.

The product insight is that the data is public but the vigilance is private. Nobody needed a better court website; they needed to never look at one again. That means the system carries the vigilance: fetch, diff, and speak only when something changed.

Engineering reality shaped product scope: public court systems are fragile, inconsistent, and occasionally simply down. So the pipeline treats 'couldn't check today' as a first-class status the user sees — a silent failure in a vigilance product is a betrayal, the exact thing users came to escape.

Alert design was the actual UX battleground: too many notifications and lawyers mute you (vigilance lost), too few and you've recreated the fear. The answer was severity tiers — 'listed tomorrow' interrupts, 'order uploaded' informs.

Every day the system sweeps the public sources for every tracked matter, diffs against yesterday's truth, and pushes only meaningful changes — tomorrow's listings loudest of all. Lawyers stopped refreshing pages; the system does the midnight worrying.

Products built on infrastructure you don't control teach defensive product design: every upstream flakiness becomes your reliability story. The discipline of surfacing what the system doesn't know became a pattern I now apply to AI products everywhere — confidence honesty is the same feature in a different costume.