Activity
One operational record. Uncertainty included.
Every operation is recorded as what was requested and what the provider actually reported. When the two disagree — or the provider never answers — the record says so, and it is never quietly overwritten later.
Illustrative example · not customer data
Four operations, four honest outcomes.
| Requested | Provider observation | Outcome | Receipt |
|---|---|---|---|
| Purge one cache path | Provider confirmed the purge request | Observed | example-r-01 |
| List workflow runs | Provider returned the run list | Observed | example-r-02 |
| Start a deployment | No response before timeout | Unknown | example-r-03 |
| Rotate a credential | Agent reported success; provider shows the old key still active | Conflicted | example-r-04 |
Example records for illustration. Identifiers prefixed example- do not exist in any workspace.
How the record behaves.
Stable identity
Each operation keeps one identifier from request to final observation, so history and receipts always line up.
No second ledger
Activity is a view over the canonical history, not a separate copy that can drift from it.
Uncertainty is kept
A later observation is appended. An earlier “unknown” stays visible rather than being rewritten as success.