Repository navigation
Add camera and actuator corroboration v0.4 - #25
Merged
Merged
Conversation
added 10 commits
October 19, 2026 10:41
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.
The v0.3 local verifier trusts its primary observation packet. This change adds a separately processed RGB camera path and PiPER drive-channel checks, then measures where those extra signals catch or miss false completion readings.
The fresh native benchmark covers 272 cases across eight layouts: 96 native scenes, 80 primary-packet forgeries, 64 auxiliary-channel faults and 32 cross-channel controls. The gate prevents 69 of 112 baseline false completions, while 43 remain through orientation, visual identity, support, temporal aliasing and replay blind spots. It also abstains on 73 of 80 baseline true completions, including 64 injected evidence faults and nine unobservable native positives. All denominators and every case are retained.
The complete run is in
benchmarks/sensor-goal-verifier-v04/evidence/. Its source-frozen benchmark used90e84701ce7d5bc330ef41b02793e2ce037d702d. Median/p95 processed-window latency is 22.1/31.5 ms; acquisition of the 200 ms evidence window, native rendering and actuation are excluded. These are shared-simulator synthetic channels, not authenticated physical sensors or hardware qualification.Validation: 107 core tests and 27 Hugging Face publication tests pass; 11 native test cases requiring an asset environment variable are skipped in this generic unittest invocation. The pinned 8-layout benchmark itself generated all 96 scenes with zero invalid cases and was independently replayed before publication. OpenCV's CPU kernel was used for the recorded timing run.