Repository navigation
feat: retire the relay room clock β the room is two numbers now (ADR-0009 final) - #513
Merged
Merged
Conversation
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
β¦sted Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017fLXUgu5WbwyPwVg1v6pED
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
TempoDeclare, legacyTempoChange, the UI control, detector declarations,SetInterval, remoteIntervalConfig) now callsengine.SetRoomConfigdirectly, so the engine's interval math no longer depends on anchor re-broadcasts. A client needs an anchor exactly once: at join, for seeding.roomclock.go(authoritative index, boundary math, transition pin) andlabelwatch.go(the label watchdog) are deleted.interval_anchorbecomes what its one remaining consumer needs: a room-config message (tempo + interval shape, NINJAM'sConfigChangeNotify) 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.observeSyncalso watchesTempoDeclare, so dual-sending can retire in a future client release.Verification
roomcfg_test.go(TempoDeclare/TempoChange/IntervalConfig tracking, redundant-broadcast suppression, and aChatMessagecontaining the literal string "TempoChange" that must not update the room)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