Health components and incident watch

The idea

Each module registers its own health checks, and /_health never calls a paid provider. A required component that fails past a grace period is filed once as an incident.

The problem
Deploy gates need a cheap, true readiness signal, and a lasting failure needs an owner.
Why it matters
Deploys stop on failed required components, survived process faults stay visible, and outages go into triage.
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.

  • Flow signal triage

    Ideas, requests and problems arrive as signals. Rules decide each signal at once, using the triage employee's accepted lessons, while System One is measured next to them. Each decision becomes held work or started work.

  • Model failure handling and outage recovery

    An unusable answer moves one tier up in the same call. Quota or auth failures put an arm on cooldown. A timeout retries at lower effort. A transient outage parks the item on a backoff timer and resumes the same run.

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.