Addressable detail
Occurrences
Individual transfers, work results, nutrition outcomes, successions and tallies nested inside larger events—each with its own stable Explorer address.
6matching occurrences
Occurrences are Explorer addresses projected from event payloads. Choose a domain and apply once to see only matching kinds.
| Occurrence | Tick | What happened | Actor | Source |
|---|---|---|---|---|
CASEBOOK ENTRY · TICK 12 · OCCURRENCE 1occ_42ed2f4be8… |
12 | The engine is named on this casebook entry record.Casebook Entry | Engine record | #761 |
CASEBOOK ENTRY · TICK 12 · OCCURRENCE 2occ_42e07b2402… |
12 | The engine is named on this casebook entry record.Casebook Entry | Engine record | #761 |
CASEBOOK ENTRY · TICK 12 · OCCURRENCE 3occ_8cc19eb18b… |
12 | The engine is named on this casebook entry record.Casebook Entry | Engine record | #761 |
CASEBOOK ENTRY · TICK 12 · OCCURRENCE 4occ_1d72630bdd… |
12 | The engine is named on this casebook entry record.Casebook Entry | Engine record | #761 |
CASEBOOK ENTRY · TICK 12 · OCCURRENCE 5occ_795cbe33ac… |
12 | The engine is named on this casebook entry record.Casebook Entry | Engine record | #761 |
CASEBOOK ENTRY · TICK 12 · OCCURRENCE 6occ_f4f7a89fd8… |
12 | The engine is named on this casebook entry record.Casebook Entry | Engine record | #761 |