Documentation

Proposed design: durable analysis runs, gated generation, incremental visibility, validated baseline and modeled report revisions, with snapshot recovery and explicit open decisions.

Production slot heatmaps for 20 July–11 October 2026: FrontDesk selected-time requests, booked starts, and a clearly qualified completion proxy, with exact data and outcome coverage.

12-hour conversation audit: outstanding client requests, follow-through gaps, and verified Linear links. Saved snapshot, not live monitoring.

September 8–December 31, 2026: all 87 active, non-test FrontDesk-enabled locations plus incremental additions, reaching 219. Target-only weekly graph with a user-set 64,000-minute 30-day exit rate. Assumptions, not a forecast.

A repeatable read-only review of HTTP latency, worker health, database access, AI and integration outcomes—with a verified September 7 baseline, investigation priorities and a manual monitoring cadence.

Status report: business_id on 23 resource tables, 11 location-mapping tables, the owner resolver, which writers fill them, mobile compatibility, verification, and what is left before backfill, APIs and UI.

Status report: 24 web endpoints that list a business's records across the locations a user may read. Address and answer shape, who sees what, the endpoint list, preview VM results, and open decisions.

The single plan for the backend: seven library layers, twelve domains, two HTTP servers. Six phases with measurable exits, what is already built, risks and open decisions.

Seven layers for the 192 libraries, the 146 runtime dependencies that break them, and the three fixes: contracts, ports and queues. Includes a ratchet check and two worked fixes.

Most servers import about 25 libraries and carry about 100. Measured rspack bundle size, heap and RSS for all 13 servers and workers, the dependency edges that cause the weight, and a six-phase plan to cut them.

The canonical booking doc — architecture and customer journey, the per-customer pricing model, API contracts, screen-by-screen implementation, catalog sync, guardrails, and testing evidence.

One holistic map of the front desk and six journeys cut from it — inbound call, website self-serve, win-back by SMS, win-back by call, inbound SMS, handover — with the tables, states, and rules each one touches, and the metric each one owns.

Pick a week and see front-desk health, widget demand, follow-up activity, and lead-to-booking conversion across every channel — with the spam story and paid-traffic ramp called out as highlights.