Repository navigation
P0-C: classify SBOw 400ms safety-observation latency and reject delayed LastApplError before Operate - #184
Closed
masarray wants to merge 2 commits into
Conversation
… gate without reducing safety
This was referenced Oct 20, 2026
Closed
Owner
Author
|
Cleanup of verified stacked Git ancestry on 2026-10-22: original source SHA Closing this now as consolidated/superseded, NOT merged to main; no branch deletion, no source history loss, no ARSAS repin, no mainline engine source promotion. Original physical validation and follow-ups still apply, and #190 remains draft. If #190 is discarded, this PR is available to reopen. |
5 of 12 tasks
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
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.
Baseline & scope
Engine PR #183 exact
c85d4e20db722bd0c2729f2533b323b13d3ef735. This does not change default 400msApplicationErrorGracePeriod, command order, MMS writes, timeouts, subscriptions or release policy. The consumer remains pinned to #183 until an independently qualified engine commit exists.Evidence-first root cause
Physical SIEBCU/CSWI4 traces: accepted SBOw MMS in 5.198–7.417ms,
postResponseWaitMs399.282–404.249ms, accepted Operate MMS 2.098–2.907ms. Source confirmsSelectWithValueCoreAsyncawaitsWaitForApplicationErrorAsync(_options.ApplicationErrorGracePeriod)with a 400ms default. Shortening it alone would risk emitting Operate after an asynchronous SBOw rejection.Engineering changes
postResponseStage=sbo-application-error-observationandconfiguredApplicationErrorGraceMsalongside pre-existing service and monotonic elapsed evidence; Operate remains separately labelledoperate-termination-observation. Diagnostic classification, not a new clock or control state machine.Next gate
Exact-head engine CI and negative scenario suite. A future transaction-correlated observer may shorten the successful path only after proving late-negative, old transaction, ctlNum/origin, disconnect, timeout and duplicate controls. No unqualified immediate-Operate fast path is enabled here; no physical speed claim or main merge.