TaskQ turns every AI request into signed evidence: where it ran, which worker handled it, which credential was used, what policy was enforced, what it cost, and whether cheaper compliant capacity was skipped.
Every serious AI buyer eventually asks the same questions. Where did this work execute? Which credential touched it? Which worker saw the data? Did the system obey policy? TaskQ does not answer with a screenshot. It answers with a signed chain entry, placement proof, registry snapshot, credential access event, and anchor witness.
| Evidence | Chain field | What it proves |
|---|---|---|
| Customer auth | customer_id + request_id | The request was customer-attributed before execution. |
| Policy enforcement | policy_hash | The effective policy was resolved and frozen before placement. |
| Placement decision | placement_proof_hash | The chosen worker satisfied hard constraints and selection rules. |
| Credential custody | credential_fpr | The key fingerprint was recorded without exposing the secret. |
| Response integrity | canonical_response_hash | The returned bytes can be matched to the closed event. |
| Settlement | settlement_ref | Every dollar movement reconciles back to a chain entry. |
| External anchor | range_root + witnesses | The chain head was witnessed so silent rewrites become detectable. |
A verifier reconstructs the policy, registry snapshot, worker attestations, price table, health state, and deterministic tie-breakers. If the selected worker was not eligible, the proof fails. If a cheaper eligible worker existed, the proof fails.
The moat is not hostage data. The moat is witnessed history. A customer can export their chain segment, but another vendor cannot retroactively sign events they were not present to witness.
{
"customer_id": "cus_live_...",
"range": [184000, 184999],
"includes": [
"chain_entries", "placement_proofs",
"credential_access_events", "registry_snapshot_proofs",
"attestation_references", "settlement_journals",
"anchor_witnesses", "verifier_spec"
],
"status": "export_ready"
}Bring your own credentials. Set the policy. Route to verified capacity. Return with proof.