Transaction-linked audit trail

Correlate immutable workspace activity with the graph transactions and costs it produced.

Evidence belongs to the workspace

Task lifecycle, transaction outcomes, and usage evidence enter their respective workspace journals. These are immutable, append-only records associated with the governed knowledge, rather than logs stranded on the machine that executed the work.

The journal follows the workspace's access, encryption, and replication policies. Live progress provides immediate operational feedback; retained records provide the historical audit trail. Workspace policy controls working-branch recording and retention.

Tie activity to the data it changed

A transaction identity correlates each produced graph commit with its journal publication record. Follow that relationship to identify who acted, which operation ran, and which knowledge graph changes belong to that transaction.

An operation that failed before producing a commit still has an execution outcome. An audit record must not invent a successful data change merely to describe the failure.

Preserve accounting evidence

Usage measurements, priced contributions, and settlement references share the task and transaction lineage. Financial records can therefore be traced back to the work and graph context that produced them.

Corrections and settlement append further evidence instead of rewriting the original usage record. An unsettled obligation remains distinct from a completed task.

Developer reference

Technical details

Atomic correlation

Journal entries are encrypted workspace content, separate from application RDF triples. Content addressing makes sealed entries tamper-evident; transaction identity and commit references join them to the exact published graph state.

Journal-enabled publication couples data visibility to durable evidence for that commit.

A task tree groups an initiating task and the child tasks it delegates, possibly across machines. The tree provides a shared execution identity; individual data-writing tasks commit through separate workspace transactions. Journal records link those commits back to the operation. Atomic publication applies per workspace transaction, so the tree can contain several independently committed outcomes.

Retention semantics

The journal is append-only: recorded outcomes remain immutable. Retention policy distinguishes durable evidence from transient progress samples; unsettled usage records cannot be dropped as settled accounting.

End-to-end observability investigates execution. Provenance models source/derivation semantics. Distributed task trees defines parentage.