Repository navigation
spec(port): port the cover-traffic emission pattern randomness guard (Refs #8887) - #9811
Closed
dmitrii-f-t27 wants to merge 1 commit into
Closed
dmitrii-f-t27 wants to merge 1 commit into
dmitrii-f-t27 wants to merge 1 commit into
Conversation
Contributor
Author
|
Merge request for the gHashTag merger: steward READY (required all SUCCESS — validate, check-linked-issue, parse-ratchet, t27b-native-linux, t27b-native-macos; the red ones are non-required per Q16 and red on master too). Ledger row included; one-line rebase if the earlier lane PRs land first — I take it on request. |
This was referenced Oct 17, 2026
Merged
gHashTag
enabled auto-merge (squash)
October 17, 2026 18:17
…(Refs gHashTag#8887) Rebuilt as one commit on master c63c1f3 so it merges; docs/reports/t27b_expectations.json rows from both sides kept (union, sorted). Content is otherwise the PR head 12cf394 unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gHashTag
force-pushed
the
port/cr-chat-07-g
branch
from
October 17, 2026 18:24
12cf394 to
24d91b3
Compare
gHashTag
disabled auto-merge
October 17, 2026 18:41
Owner
gHashTag
added a commit
that referenced
this pull request
Oct 17, 2026
…het, #2774) cover_traffic_emission_pattern_randomness_guard.t27 (from #9811) declared `IntervalObservation`, a name master already defines in cover_traffic_inter_arrival_autocorrelation_guard.t27. Two definitions of one type name leave its domain size undetermined, so `tri types ratchet` went red (ledger 109, observed 110). Rename it EmissionIntervalObservation in this file only and reseal; the ratchet is CLEAN at 109 again. Refs #10096 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gHashTag
added a commit
that referenced
this pull request
Oct 17, 2026
The batch brought four type names that two specs each define, and two definitions of one name leave its domain size undetermined: `tri types ratchet` went red, ledger 109 vs observed 113. - IntervalObservation: the emission pattern randomness guard (#9811) repeats master's inter-arrival guard. Renamed EmissionIntervalObservation, byte-identical to #10097's fix, so the two batches merge cleanly. - SizeObservation / SizeDistVerdict: message_size_class_distribution_guard repeats cover_traffic_size_distribution_guard. Renamed SizeClassObservation / SizeClassDistVerdict. - TransitionObservation: padding_class_transition_entropy_guard repeats padding_length_class_transition_uniformity_guard. Renamed EntropyTransitionObservation. Each renamed spec is resealed. Checked on the Railway lab: types ratchet CLEAN at 109, dupe_scan finds no new duplicate body. Refs #8884 Co-Authored-By: Claude Opus 5.5 <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
2 participants
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.
Refs #8887 (CR-CHAT-07 ring tracker). Parent epic: gHashTag/trios#1812 (W2, own lane, T-PORT). Seventh CR-CHAT-07 ring target delivered: the pattern-randomness rules (R-CHAT-10) — batch ceiling (4096), interval floor (8), per-interval zero probe and single-interval ceiling (300000 ms; boundary accepted in CEPR-09), then over the batch the entropy floor (2.0 bits) and the Wald-Wolfowitz runs floor (len/4, at least 2) — D5 verdict with every payload field, original rule order, all ten CEPR tests transcribed plus a rule-order test (11 total, 0 vacuous). The original's compute_entropy (float bucketing + Shannon log2) and count_runs (float mean) need int→float casts and the log fold the backends do not lower — per the lane convention (#9698/#9747/#9752) the entropy and runs arrive caller-computed; the structural rules stay fully in-spec; all fixture statistics Python-verified exact (varied 3.0/7, boundary 2.197/2, large 6.12/100, predictable 0.811/2 → LowEntropy answers first as the original's matches! allows). t27b 11/11 native; t27c 11/11; gen-rust compiles under rustc (0 errors, 0 &'static str, 0 Vec<const); coverage Untested 0; seal all hashes MATCH; ledger row included (pass, non-pass untouched). Dedup checked. Sequencing: one-line ledger rebase if the earlier lane PRs land first — I take it on request.