Order lifecycle mirrors by event time

This commit is contained in:
Meta Vens 2026-07-13 00:19:54 +01:00
commit 3f7d6dcbda
5 changed files with 129 additions and 3 deletions

View file

@ -501,3 +501,13 @@ for each service family; attention is derived from that event. History retains
older failures without letting them impersonate current state. Adversarial
tests prove a newer recovery supersedes an old failure and a newer failure is
not hidden by an old recovery.
## Last writer presented as latest lifecycle event
The lifecycle `latest` mirror was overwritten on every write. A delayed retry
or replay of an older receipt could therefore move the stored present backward
even though immutable history contained the correct ordering. Lifecycle writes
now validate RFC3339 start/completion timestamps, reject completion before
start, and update the mirror only when `(event time, receipt ID)` is not older
than the current mirror. A delayed old receipt remains in history without
becoming current.

View file

@ -128,6 +128,9 @@ The confirmed conceptual substitutions have been cut:
- Service lifecycle projection selects the actual latest family event. An old
attention receipt no longer masquerades as current state after recovery;
newer failures still surface immediately.
- The lifecycle `latest` mirror is event-time-owned, not last-writer-wins.
Invalid/reversed timestamps are refused and delayed old receipts cannot move
the mirror backward.
The presentation boundary is now plain: `swarm overview` is a generic compact read-only projection. Gjallar is a downstream TUI application on Nightwing and is not an Epiphany organ, provider, owner, runtime, or architectural dependency. Eve/CultUI graphs may be lowered or composited downstream without Epiphany caring which presentation client does it.