It needs a verifiable record of where the work ran, which credential was used, what policy was enforced, which worker handled it, and whether non-compliant execution was blocked before it happened.
Provider logs can explain their platform. TaskQ proves customer-defined placement across customer keys, operator workers, colos, local inference, and sovereign regions — policy-bound AI work across approved infrastructure with proof that survives procurement review.
Requests can be constrained to approved jurisdictions and blocked from excluded regions before any model call or worker dispatch occurs.
TaskQ records credential fingerprints and access events instead of pretending a shared house account is an enterprise trust model.
HashIQ receipts record policy, placement, credential access, worker reference, usage, and chain verification material.
bad = sha256(sensitive_identifier) good = HMAC(customer_private_pepper, normalized_reference) chain proves consistency customer keeps the identifying pepper
Blocked attempts, credential access events, placement proofs, registry snapshots, settlement parity, and external anchors — scoped to your tenant and date range.
Technical controls and verifiable evidence. Counsel and auditors decide what satisfies a specific regime — the product’s job is to make the evidence impossible to hand-wave.