process TODO.md step 9
This commit is contained in:
@@ -59,4 +59,15 @@ The shared networking core SHALL process server-tick or clock-synchronization sa
|
||||
#### Scenario: Hosts can consume smoothed clock data for prediction
|
||||
- **WHEN** prediction or reconciliation code needs the current server-time estimate
|
||||
- **THEN** it reads that estimate from the clock-sync strategy or state object
|
||||
- **THEN** it does not query `SessionManager` for authoritative clock ownership
|
||||
- **THEN** it does not query `SessionManager` for authoritative clock ownership
|
||||
|
||||
### Requirement: Integration wiring enforces sync lane selection
|
||||
The networking stack SHALL route sync-designated traffic through the sync transport when the integration layer provides one, and SHALL fall back to the primary reliable transport when it does not.
|
||||
|
||||
#### Scenario: Dedicated sync transport available
|
||||
- **WHEN** sync-designated traffic is sent from a session whose integration wiring includes a sync transport
|
||||
- **THEN** the traffic SHALL be dispatched on the sync transport instead of the primary reliable transport
|
||||
|
||||
#### Scenario: Dedicated sync transport unavailable
|
||||
- **WHEN** sync-designated traffic is sent from a session whose integration wiring does not include a sync transport
|
||||
- **THEN** the traffic SHALL be dispatched on the primary reliable transport without failing session operation
|
||||
|
||||
Reference in New Issue
Block a user