Skip to content

feat: retire the relay room clock β€” the room is two numbers now (ADR-0009 final) - #513

Merged
quasor merged 3 commits into
mainfrom
claude/relay-retirement
Aug 2, 2026
Merged

quasor merged 3 commits into
mainfrom
claude/relay-retirement

Conversation

@quasor

@quasor quasor commented Aug 2, 2026

Copy link
Copy Markdown
Collaborator

The last chapter of ADR-0009, now that 5.0.0 is field-validated and there are no pre-5.0 clients to protect.

Two commits

  1. Client prep β€” every tempo/config adoption site (TempoDeclare, legacy TempoChange, the UI control, detector declarations, SetInterval, remote IntervalConfig) now calls engine.SetRoomConfig directly, so the engine's interval math no longer depends on anchor re-broadcasts. A client needs an anchor exactly once: at join, for seeding.
  2. The relay retirement β€” roomclock.go (authoritative index, boundary math, transition pin) and labelwatch.go (the label watchdog) are deleted. interval_anchor becomes what its one remaining consumer needs: a room-config message (tempo + interval shape, NINJAM's ConfigChangeNotify) with a vestigial zero index for wire-shape stability. The relay tracks two plain values per room and forwards everything else opaquely β€” pillar 5, fully honored again. observeSync also watches TempoDeclare, so dual-sending can retire in a future client release.

Verification

  • Relay suite green, including new roomcfg_test.go (TempoDeclare/TempoChange/IntervalConfig tracking, redundant-broadcast suppression, and a ChatMessage containing the literal string "TempoChange" that must not update the room)
  • App suites green (12 pkgs cgo + linkstub)
  • tier2 PASS (7 checks, 0 failures, 0 loss) β€” the script builds the relay from this tree, so this is the clock-free relay and adaptive clients verified together, end to end

Deploy note

Merging doesn't change production β€” the relay ships when you fly deploy. Pre-5.0 clients can't jam through the new relay (their labeler never aligns without a real index); per your call, there are none.

πŸ€– Claude Code β€” the relay now knows two numbers and minds its own business

quasor and others added 3 commits August 1, 2026 19:45
Until now the engine's interval math only heard about tempo/config through the
relay's anchor re-broadcasts. Every site that adopts or declares a tempo (UI
control, detector declaration, TempoDeclare adoption, legacy TempoChange,
SetInterval, remote IntervalConfig) now tells the engine directly, so the one
thing a client still needs an anchor for is joiner seeding β€” which is all the
relay is about to keep sending (ADR-0009, retirement step).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017fLXUgu5WbwyPwVg1v6pED
The last chapter of ADR-0009. The relay's interval_anchor becomes what its
one remaining consumer needs: a room-config message β€” tempo and interval
shape for joiner seeding, NINJAM's ConfigChangeNotify β€” with a vestigial zero
index for wire-shape stability. Deleted behind it: roomclock.go (the
authoritative index, boundary math, transition pin), the label watchdog
(labelwatch.go β€” nothing compares labels to anything anymore), and the
re-anchor mechanics. The relay now tracks two plain values per room and
forwards everything else opaquely β€” pillar 5, fully honored again.

observeSync also watches TempoDeclare alongside the legacy TempoChange, so
clients can eventually stop dual-sending. Redundant re-broadcasts are still
suppressed (join-time IntervalConfig gossip, the dual-sent legacy copy of an
already-observed declaration).

Verified end to end: tier2 builds the relay from this tree β€” PASS, 7 checks,
0 failures, 0 loss, over the clock-free relay and adaptive clients together.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017fLXUgu5WbwyPwVg1v6pED
@quasor
quasor merged commit 7082016 into main Aug 2, 2026
3 of 6 checks passed
@quasor
quasor deleted the claude/relay-retirement branch August 2, 2026 03:27
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.

1 participant