Skip to content

spec(port): port the network flow direction uniformity guard (Refs #8887) - #9854

Merged
2 commits merged into
gHashTag:masterfrom
dmitrii-f-t27:port/cr-chat-07-ac
Oct 17, 2026
Merged

2 commits merged into
gHashTag:masterfrom
dmitrii-f-t27:port/cr-chat-07-ac

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). Twenty-eighth CR-CHAT-07 ring target delivered: the flow direction rules (R-CHAT-10) — batch ceiling (65536), strictly-increasing timestamps, then over a non-empty batch the inbound floor (10), the outbound floor (10) and the ratio ceiling (larger/smaller rounded integer fold, ceiling 3; 20:10 passes at ratio 2 in NFDU-10, 50:10 answers the ceiling in NFDU-03) — D5 verdict with every payload field (count/min for the floors, inbound/outbound counts for the ratio), original rule order, all ten NFDU tests transcribed plus helper and rule-order tests (12 total, 0 vacuous). Pure usize arithmetic — the rounded ratio fold ports whole; the empty batch guards the 1..len range (empty slice range length underflow, caught locally); all ratio math Python-verified. t27b 12/12 native; t27c 12/12; 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.

…ashTag#8887)

The twenty-eighth CR-CHAT-07 ring target (W2, R-CHAT-10): the
flow direction rules - the batch ceiling, the
strictly-increasing timestamps (the empty batch accepted
before them), then over a non-empty batch the inbound floor
(ten), the outbound floor (ten) and the ratio ceiling (the
larger over the smaller, rounded integer fold, ceiling three)
- as the D5 verdict with every payload field (the count and
min for the floors, the inbound and outbound counts for the
ratio), the original's rule order, and all ten NFDU tests
transcribed plus helper and rule-order tests.

The original's rounded ratio is pure usize arithmetic and
ports whole; the empty batch guards the 1..len range before
it runs (the range length underflows on an empty slice).
Fixtures verify the ratio math exactly: twenty-to-ten passes
at a ratio of two, forty-to-ten answers the ceiling at four.

Checks (conventions 0-14): t27b test 12 passed 0 failed; t27c
test-report 12/12, 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 (added in the follow-up commit 12be5a5 — the first commit's insert script failed; the row is in this PR). 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:13
@gHashTag
gHashTag disabled auto-merge October 17, 2026 18:42
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