Skip to content

The event record: a badge on the identity circle, a list behind it (#132) - #133

Merged
lannbot merged 1 commit into
mainfrom
visor/event-record
Aug 26, 2026
Merged

The event record: a badge on the identity circle, a list behind it (#132)#133
lannbot merged 1 commit into
mainfrom
visor/event-record

Conversation

@lannbot

@lannbot lannbot commented Aug 26, 2026

Copy link
Copy Markdown
Collaborator

Implements #132 (design memo filed from the announcements-vs-notification-list discussion; the NOTES.md entry in this PR is its summary).

What

  • The split. Moment cues stay push and record-less; standing conditions are new visor-held keyed state (setCondition/clearCondition, session-live, lit while standing); event records are a persistent, acknowledgeable list (addEvent/events/markEventsSeen/unseenEventCount, optional eventsKey persistence, cap 50, erase() wipes it).
  • The badge: a dot (never a count) on #visor-settings, absolutely positioned (zero layout shift — strip-geometry now takes every measurement with the badge lit), framework voice by construction, lit = unseen ∪ standing. Author rule documented at the only door: engine/visor-authored text only.
  • The list: a "recent events" light drawer tenant behind a visor-owned settings-sheet row, using the erase entry's suspend/resume motion; conditions first, records newest-first with coarse ages; opening marks seen.
  • The mechanical rule: every consequential announcement leaves a record — one hook in visorAnnounceSink's consequential branch (exactly-once verified: both hosts' consequential paths flow through that sink; statusWriter never records).
  • solo's sync watch: the syncFailureAnnounced edge-trigger boolean is replaced by the condition edge; announce-once-per-crossing preserved exactly.

Review

Independent review against #132 + the three-voices policy: non-blocking; its one actionable advisory (strip-geometry should measure a lit badge rather than trust the CSS) is addressed in this PR, with a negative control run against a bogus seed key.

Gates

  • e2e 36/36 (full suite; visor-events new, store-outage-recovery extended with the condition beats, strip-geometry lit)
  • check-invariants.sh green (incl. check (h): no new foreign assignments)
  • just site / just e2e-check / todomvc spike type-check green (no eventsKey → in-memory, proving the config stays optional)

Automerge will be armed per repo convention.

…tity circle

Design memo #132, NOTES entry included. The strip's timed announcement
was one transient line multiplexing three jobs; the split gives each
its mechanism: moment cues stay push (announce/pulse/speak,
record-less), standing conditions become visor-held keyed state
(set/clear, lit while standing, session-live), and event records
become a persistent acknowledgeable list behind a dot on
#visor-settings — lit = unseen records ∪ standing conditions, opened
through a visor-owned settings-sheet row into a 'recent events' drawer
tenant (erase-entry suspend/resume motion; opening marks seen).

The mechanical rule that makes wiring one line per host: every
consequential announcement leaves a record — hooked in
visorAnnounceSink's consequential branch only (statusWriter never
records). solo's sync watch now sets/clears the 'sync' condition and
the edge return replaces its hand-rolled syncFailureAnnounced boolean,
preserving announce-once-per-crossing exactly.

Gates: e2e 36/36 — visor-events new (seeded stale boot cache drives a
real reconcile-announced event into badge, list, seen, reload
persistence); store-outage-recovery extended (condition lights the
badge, failure record outlives the ambient recovery announce,
condition block clears); strip-geometry now measures with the badge
lit. Invariants green; harness and hosts type-check green.
@lannbot
lannbot enabled auto-merge August 26, 2026 21:50
@lannbot
lannbot merged commit ff55755 into main Aug 26, 2026
3 checks passed
@lannbot
lannbot deleted the visor/event-record branch August 26, 2026 21:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants