previews · RCAs

Root-cause analyses

Investigations into why something failed and what to do about it. Each RCA can have companion docs (architecture grounding, prompt edits, fix proposals) bundled in the same folder.

Date Title Author
2026-08-31 Lawrence US family-law test session — trace triage
James's Texas divorce test end-to-end: finalised documents invisible to the agent, two zero-output turns at the context ceiling, twelve blank CourtListener timeouts, OpenLaws unable to find "insupportability", and the missing court-filing pre-flight. 42 traces, live reproductions, ranked fixes.
Adolfo
2026-08-13 prd-us-db memory exhaustion — the shared v3 instance ran out of headroom
Why the 95% memory alarm fired: 16 services and 2 CDC readers on a 2 GiB db.t4g.small, with CDC holding two-thirds of all connections. Three months of metrics, the front-office step change, the live pg_stat_activity breakdown, and the one-line resize.
Adolfo
2026-08-11 Client care letters named the wrong lawyer
Draft CCL generation took “Your lawyer” from the logged-in user, so an assistant drafting for their supervising solicitor named themselves. 393 letters in 12 months, 340 already signed, plus the fix and the queries to re-measure it.
Libaan
2026-08-04 Lawrence document retrieval failures — production incident analysis
Why processed documents appeared unavailable: whole-matter query scope, a 1,000-object S3 page limit, child-asset selection, and misleading processing responses.
Libaan
2026-05-13 Lawrence-2 — US team rollout trace analysis
Day-one adoption + failure analysis across Georgia, Sabrina, Scott. 14 traces, two real defects, citation-channel gap, cost-accounting caveat.
Adolfo
2026-05-11 Lawrence-2 — document edit pipeline RCA
Why bold / italic / heading / alignment / list-conversion tests fail end-to-end, and where to fix.
Adolfo