TaskQ’s dashboard is not a vanity analytics screen. It is the operational surface for requests, policies, credentials, workers, chain verification, audit exports, and settlement state.
The request table is only the starting point. The proof panel shows what happened, why it happened, and which evidence can be exported or replayed.
Every panel maps to a system invariant: authenticated requests, explicit custody, verified capacity, replayable placement, signed chain, and reconciled money movement.
Inspect request IDs, route class, plane, policy hash, credential fingerprint, worker reference, status, and proof headers.
See every credential unwrap event by request, worker, custody class, key domain, and timestamp.
Monitor worker health, jurisdiction, trust tier, attestation expiry, price, available slots, and lease failures.
Manage default policies, request-level tightening, cost ceilings, custody floors, approved regions, and blocked routes.
Open HashIQ entries, verify signatures, check anchors, replay placement, and export signed evidence.
Confirm every billable chain entry maps to one journal entry, one customer debit, and one operator credit.
The console does not exist to make bad routing look pretty. It exists to enforce policy, show refusal evidence, and prove when the system chose not to execute.
{
"event_type": "placement.refused",
"reason": "NO_COMPLIANT_CAPACITY",
"policy_hash": "sha256:...",
"must_run_in": ["CA"],
"must_not_run_in": ["US"],
"eligible_set": 0,
"chain_written": true
}
Policy enforcement, credential access history, chain verification, and settlement parity — live against your workloads.