Front-door fast path and lane

The idea

Status questions get answers from runtime state through templates, with no model, and a receipt goes out before any model call. A separate job lane serves what a person waits on, and casual consumer chat starts no work.

The problem
People waited behind long ticks for a simple status answer.
Why it matters
Replies on WhatsApp and chat stay fast even when every main job slot is busy.
Where it stands
In production as of

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

  • One shared conversation with topic threads

    Web and WhatsApp share one CEO conversation split into named threads; long threads fold into rolling summaries and every thread is searchable.

  • Postgres job queue with dead letters

    Background work is stored as job rows, claimed with leases and heartbeats, and retried with backoff. A job that keeps failing stays as a dead letter for 30 days.

  • Observe view, why-trace and item logs

    A zoomable view over existing records goes from the fleet to a worker, a tool call and a delegation. It adds a 'why' timeline, a diagnostic bundle, the warn and error lines captured for each item, and front-door latency.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.