docs(timeline): explain the per-interval tick schedule - #1130
Merged
tcoratger merged 2 commits intoJun 17, 2026
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
# Conflicts: # src/lean_spec/spec/forks/lstar/timeline.py
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
1 participant
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.
What
Expands the docstring of the interval-tick method in the lstar timeline so it explains the five-interval slot schedule, not just that it "advances time and performs interval-specific actions".
The body now names each action point within a slot:
Why
The match arms encode a consensus-critical schedule, but the one-line docstring gave no hint why there are five intervals, why aggregation sits at interval 2, or why fast confirmation sits at interval 3. The new prose states the rationale: aggregation waits until interval 2 so a block proposed at slot start has time to propagate and gather votes before bundling, and fast confirmation follows at interval 3 so the safe target reflects the freshest votes.
Docs-only change. No behavior change.
just checkpasses.🤖 Generated with Claude Code