urt-rs / docs /research /RUST_SCOREBOARD.md
nmarshall's picture
gameplay: port scoreboard dispatch policy
744c236
|
Raw History Blame Contribute Delete
1.1 kB
# Rust scoreboard recipient policy and bounded ranking publication plan
RE-800. Reproduce with `python3 scripts/analyze_rust_scoreboard.py`; focused validation: `cargo xtask test-group rust-scoreboard`. [Machine report](rust-scoreboard.json).
The recipient policy filters only connection state2 in scan order and bounds safe slices at64. A pure ranking plan composes the recovered mixed-population ranking contract with this gate.21 standalone and48 full source fixtures check exact order, ranks, globals and recipients. Unit tests cover signed connection states,64/65 boundaries and spectator rank preservation.7805 exit-rule effects and179363 scoreboard body/native sends remain unimplemented; a live runtime must execute exit-rule effects before selecting fresh recipients.
Original executable/native runtime and complete Linux/macOS Rust/Bevy/Solari acceptance remain unverified.
Formatted input paths in all five new Rust parity producers are declared explicitly in the xtask registry. The registry regression verifies each source-report-to-producer/test mapping without full fallback.