Follow accountable work across machines, graph transactions, audit evidence, and costs.
Start with the user request and follow the work it causes, wherever it runs. See the executing machines, delegated tasks, progress, failures, and resulting changes together.
Every task identifies the user or accountable principal on whose behalf it executes. Delegation preserves that attribution; the executor and the person responsible for the work remain distinct.
See Distributed task trees for the execution model behind this view.
Move from a failed operation to its input, branch, transaction, and recorded outcome. A task completing, a data change being committed, and its charges settling are distinct facts that can be investigated together.
Transaction-linked audit trail explains the immutable workspace journal and its correlation with knowledge graph changes.
Usage and cost belong to the same accountable operation. Inspect measured contributions, paying wallets, receiving providers, and settlement outcomes without reconstructing them from a separate billing log.
Payments and budgets owns financial authorization and settlement. Prices by contribution explains the breakdown among participants.
Developer reference
TaskTreeId, TaskNodeId, session, workspace transaction and commit IDs connect the distributed execution graph to durable outcomes. Trace/span identifiers align with W3C Trace Context and OpenTelemetry conventions; a session can own multiple traces.
Parentage survives remote delegation. The accountable principal on whose behalf work executes remains distinct from executor identity and wallet authority. The live task projection and immutable workspace journal expose different lifetimes of the same operation.
Task trees aggregate usage metrics and cost metrics across many workspace transactions. Token calculations run during execution; claims retain payer, recipient, quantity, price and task/transaction context. Multiple paying parties can attach their wallets to one tree. Authorization still controls which evidence a viewer can inspect.