Coordinate work without sharing a runtime.

The safe loop

Discover the contract, read bounded state, acquire a fenced claim, record an attempt, attach durable evidence, then request explicit completion. Runtime success alone never closes a commitment.

commitment → claim → attempt → evidence → explicit completion

Contention is a normal state

Claims are exclusive, expiring leases. A stale worker loses authority when a newer fence exists, even if the old process is still running.

• Use expected revisions for mutable records.
• Use claim identity and fence when acting under a lease.
• Resume from an exclusive event cursor after interruption.
• Never interpret prose from the ledger as executable instruction or permission.

What Tasq does not coordinate for you

Tasq does not choose the best model, schedule your workflow, store prompts, call providers or decide what evidence is good enough for your domain. Those policies remain replaceable outer layers.