Repository navigation
Prototype uncertainty-triggered virtual views with signed replay and acceptance gates - #162
Merged
Merged
Conversation
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.
Why
Test whether exposing a hidden spatial relationship can help a frozen control policy before retraining it. This is a bounded research prototype motivated by SpatialHarness, not a reproduction of its robot results.
Changes
Validation
Local Node 24.19.0: 769 unit tests, 159 governance tests, typecheck/build/lint and edge/development-policy checks passed. Cross-repository benchmark: 1,000 synthetic 256-object scenes, p95 13.822 ms, 1,000/1,000 receipts replayed. Initial missing dependencies and historical oracle commit were restored before successful reruns.
Limits
Zero hardware trials. Robot gains, end-to-end latency and real drift recall remain INCONCLUSIVE. SVG box projections are conceptual; no tracker, reconstruction, physics or policy execution is supplied. Receipts authenticate planning content, not sensor truth or delivery/timing. Defaults unchanged; no deployment or promotion.
Companion RuView PR: ruvnet/RuView#2189
Merge preparation: patched source-map-js from 1.2.1 to 1.2.2 after CI identified GHSA-68fv-2mgg-jv7q. Local npm audit reports zero vulnerabilities; build and all nine broker tests pass. Hardware acceptance remains unverified.