Capabilities that carve up how events unfold and who set them in motion.
Holding questionHow would a system reason about change if time were a first-class citizen?
Event sourcing gestures at this trail without walking it. Each stop is a distinction that mainstream code either drops or bolts on.
- 01
Aspect and Event State
Is the action beginning, continuing, repeated, attempted or completed?
Why hereWas the action completed, ongoing, or habitual? Aspect is a viewpoint on the shape of an event.
Time and Action·Research · Illustrative·Graft · Conceptualised - 02
Temporal Reference
When, relative to what, did this happen?
Why hereLocate the event on a timeline. Temporal reference is the axis event stores usually provide only for wall-clock time.
Time and Action·Research · Under review·Graft · Documented - 03
Causativity and Agency
Who caused this to happen, and how directly?
Why hereWho or what caused this? Causative marking treats causation as a role, not a comment.
Participation and Agency·Research · Source required·Graft · Documented - 04
Switch-Reference
Is the subject of this action the same as the subject of the previous one?
Why hereWhen actions chain, does the doer stay the same? Switch-reference tracks continuity across events.
Participation and Agency·Research · Source required·Graft · Documented
Aspect, tense and causation are not the same thing. Software that conflates them loses the difference between what happened, when it happened, and what made it happen.