Facilitation Tool · Browser-local · Timebox Planning · 2026 · Solo — product framing, browser-local scheduling model, direct-manipulation interaction design, and production delivery
Agenda Loom
A browser-local agenda rehearsal bench that keeps the hard stop fixed while editable segment durations reveal exactly where a meeting crosses it.
The problem
Meeting agendas often add up on paper while hiding the moment discussion will exceed the promised end time. Agenda Loom fixes the start and hard stop, lets a facilitator name and resize each segment, and immediately labels work that remains inside the timebox, crosses the stop, or begins after it. The result is a timestamped run of show that can be copied for facilitation. The production surface explicitly makes no calendar-integration or availability claim and says that its agenda state remains browser-local and unsaved.
Architecture
Key decisions
Keep the hard stop fixed
Changing the timebox does not silently compress every agenda segment. The production check changed the default 45-minute frame to 20 minutes; the app preserved the 37 minutes of authored work, reported a 17-minute overrun, and identified the segment that crosses the stop plus the segment that starts afterward.
Make schedule risk visible before export
The primary output is not a generic duration total. Every segment receives a timestamp and boundary classification, while breathing room or overrun remains visible beside the fixed start-to-stop frame before the facilitator copies anything.
Keep the integration claim narrow
The shipped footer states no calendar integration, no availability claim, and browser-local state. The dossier preserves that boundary rather than implying scheduling automation, persistence, collaboration, or calendar writes that the production artifact does not expose.
Publish only the evidence that still exists
Vercel production deployment dpl_2b8WhaXoqrECwAdUfxQQQxwcmmYJ is Ready and its stable core-action route returned HTTP 200 during reconciliation. No matching source repository was present in the connected GitHub inventory, so this case study links to contact for implementation notes instead of inventing a repository or commit claim.