docs(backlog): far-future-timestamp fix + re-climb the ladder to Rung 4#36
Merged
Conversation
…adder to Rung 4 The far-future request-timestamp replay residual surfaced during PR #35 (by the Extended Rung 4 ReplayWindow model's NoFutureReplay witness). Rewrite the top backlog item so it is explicit that the work is two-part: (1) the code fix in check_freshness / parse_age, and (2) re-discharging every rung that covers the touched code — Rung 1 regression test, Rung 2 freshness property, Rung 3 Kani monotonicity, Rung 4 flipping NoFutureReplay to a held invariant — so assurance returns to the Rung 4 level rather than leaving the proofs trailing the code. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Rewrites the top backlog item so the far-future request-timestamp replay residual — surfaced during PR #35 by the Extended Rung 4
ReplayWindowmodel'sNoFutureReplaywitness — is captured as two explicit parts:check_freshness/parse_agereject timestamps more than a small clock-skew allowance into the future, instead of clamping to age 0 with no upper bound.src/prop.rsfreshness property to assert rejectionymd_hms_to_epochmonotonicity/totality proofsReplayWindowNoFutureReplayinvariant from surfaced-gap witness to a held invariantBacklog-only doc change; no code or build impact.
🤖 Generated with Claude Code