Skip to content

spec(port): port the cover-traffic timing correlation guard (Refs #8887) - #9828

Closed
dmitrii-f-t27 wants to merge 1 commit into
gHashTag:masterfrom
dmitrii-f-t27:port/cr-chat-07-r
Closed

dmitrii-f-t27 wants to merge 1 commit into
gHashTag:masterfrom
dmitrii-f-t27:port/cr-chat-07-r

Conversation

@dmitrii-f-t27

Copy link
Copy Markdown
Contributor

Refs #8887 (CR-CHAT-07 ring tracker). Parent epic: gHashTag/trios#1812 (W2, own lane, T-PORT). Eighteenth CR-CHAT-07 ring target delivered: the timing-correlation rules (R-CHAT-10) — window ceiling (256), presence of both trains (NoRealTraffic before NoCoverTraffic), per-emission consecutive-real probe, one-cover floor between reals (MIN=1), whole-window always-follows rejection (every cover directly after a real = correlated pattern) — D5 verdict with the code alone (no payloads), original rule order, all ten CTCG tests transcribed plus a rule-order test (11 total, 0 vacuous). Honest pin: the original's CTCG-02 ignores its result; the verified outcome is CoverAlwaysFollowsReal (the single cover of real, cover, real sits directly after a real) — the port pins it with the discrepancy named; the original's duplicate counter declarations port as one each. 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.

…shTag#8887)

The eighteenth CR-CHAT-07 ring target (W2, R-CHAT-10): the
timing-correlation rules - the window ceiling, the presence of
both trains, then per emission the consecutive-real probe and
the one-cover floor between reals, then over the whole window
the always-follows rejection (every cover directly after a
real is a correlated pattern) - as the D5 verdict (no
payloads, the code alone), the original's rule order, and all
ten CTCG tests transcribed plus a rule-order test.

The original's CTCG-02 ignores its result; the verified
outcome is CoverAlwaysFollowsReal (the single cover of real,
cover, real sits directly after a real), and the port pins it
with the discrepancy named. The original declares two counters
twice; the port declares each once.

Checks (conventions 0-14): t27b test 11 passed 0 failed; t27c
test-report 11/11, 0 vacuous; gen-rust output compiles under rustc;
coverage Untested 0; ASCII only; seal saved, all hashes MATCH;
@dmitrii-f-t27

Copy link
Copy Markdown
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.

@gHashTag
gHashTag enabled auto-merge (squash) October 17, 2026 18:12
@gHashTag
gHashTag disabled auto-merge October 17, 2026 18:42
gHashTag pushed a commit that referenced this pull request Oct 17, 2026
Landed from #9828 as part of one combined PR (the Actions queue could not
carry 28 single runs while master kept moving under the ledger rows).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@gHashTag

Copy link
Copy Markdown
Owner

Carried unchanged, with its original author, as one commit of #10097 (tracking #10096). That PR lands all 25 green CR-CHAT-04/07 ports at once, because each single PR kept conflicting on the ledger rows before its CI could finish. Closing this one so its queued jobs free the Actions queue.

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.

2 participants