An execution contract around your code

Your runner schedules the job. Captor checks the operations you route through it. The application still owns transactions, stable input ordering, idempotency and cancellation.

1. Declare resource limits and required outcome metrics.
2. Reserve capacity before guarded work starts.
3. Commit usage after successful work; release unused capacity when appropriate.
4. Record a checkpoint after application progress is safe to acknowledge.
5. Persist and inspect the receipt.

The SDK includes batching, local JSONL and SQLite stores, a CLI, fetch and Prisma adapters. Backfills process batches sequentially; built-in rate limiting, distributed budgets and distributed locks are not provided.

An execution receipt contains status, resource totals, metrics, checkpoints and violations. It does not contain a full reservation event log, contract snapshot or resume lineage. Hosted Runs imports these receipts as snapshots; it does not start, stop or resume your jobs.

Follow the quickstart or recover a stopped backfill.