Action provenance, often called an action trace, is tracing a change back to what caused it: which actor, on what instruction, produced which effect, in what order.
Logging answers what happened. Provenance answers where it came from: the actor, the instruction and the order. You can have complete logs and no provenance at all.
FlurryPORT sequences and stores; a stream arrives in order and every entry carries its own arrival time and its signer. When two actions race, the record says which landed first, and that answer does not change on re-reading.
Provenance inside a system is not provenance a stranger can check. A shared stream lets its participants hold each other to the record. On its own it does not let an outsider audit the platform that kept it. Knowing which of the two you need is most of the work.
Each capture carries who signed it, what it asked for, and when it landed, in an order the server assigns rather than one the sender claims; each delivery carries which destination, what it received, and what it answered. The walkthrough below shows the record for one action fanned out to three destinations.
The glossary is the canonical index of every FlurryPORT term these pages use.