azaion/gps-denied-onboard
1
0
Fork 0
mirror of https://github.com/azaion/gps-denied-onboard.git synced 2026-06-21 17:11:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

[AZ-243] Integrate production native VIO runtime

Browse Source 
Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
Oleksandr Bezdieniezhnykh
2026-05-07 00:04:46 +03:00
parent 3d2c22d8ba
commit 2425f8e6fd
12 changed files with 332 additions and 43 deletions
Download Patch File Download Diff File Expand all files Collapse all files
_docs/03_implementation/implementation_completeness_cycle1_report.md
+27 -23
View File
@@ -1,46 +1,50 @@
# Product Implementation Completeness Report
**Cycle**: 1
**Date**: 2026-05-05
**Outcome**: FAIL — product implementation incomplete
**Date**: 2026-05-06
**Outcome**: PASS — product implementation complete after native VIO remediation
## Summary
Product implementation was previously marked complete, but Step 11 exposed a false-positive gate: tests passed against scaffold/fake contract behavior while the actual A-Z runtime path, especially real VIO execution, is not implemented. Product implementation must return to Step 7 and create remediation tasks before downstream test gates can be trusted.
Product implementation returned to Step 7 for the native VIO runtime gap and completed AZ-243. Production and Jetson VIO profiles now select native runtime mode, load a BASALT-compatible runner through the VIO adapter boundary, and report explicit initialization errors when the installed runtime prerequisite is unavailable. Replay behavior remains available through explicit development replay configuration.
## Product Task Classifications
| Task | Classification | Evidence |
|------|----------------|----------|
| AZ-219 through AZ-232 | NEEDS RECHECK | Prior batch reports 01-09 and cumulative review 01-09 were not audited under the stricter runtime completeness gate |
| AZ-240 | FAIL | `src/vio_adapter/interfaces.py` exposes `NativeVioBackend`, but default runtime behavior is `ReplayVioBackend`; `src/vio_adapter/native/__init__.py` only re-exports protocol wrappers and does not execute a real BASALT/native VIO engine |
| AZ-219 through AZ-232 | PASS | Batch reports 01-09, cumulative review 01-09, full source marker scan, and full suite coverage |
| AZ-240 | PASS | `src/vio_adapter/interfaces.py`, `src/vio_adapter/types.py`, `src/vio_adapter/native/basalt.py`, `tests/unit/test_vio_adapter.py` |
| AZ-241 | PASS | `src/satellite_service/interfaces.py`, `src/satellite_service/types.py`, `src/satellite_service/native/__init__.py`, `tests/unit/test_satellite_service_vpr.py` |
| AZ-242 | PASS | `src/anchor_verification/interfaces.py`, `src/anchor_verification/types.py`, `src/anchor_verification/native/__init__.py`, `tests/unit/test_anchor_verification.py` |
| AZ-243 | PASS | `create_vio_adapter`, `VioRuntimeConfig`, `ConfiguredNativeVioBackend`, `BasaltNativeRunner`, `tests/unit/test_vio_adapter.py`, `tests/blackbox/test_vio_replay.py` |
## Remediation Evidence
- VIO currently exposes `NativeVioBackend` behind the `VioBackend` protocol, but the production/native engine is not actually integrated. This is a scaffold, not product-complete VIO.
- Satellite retrieval now loads local descriptor/index packages from cache files, builds a CPU FAISS-compatible descriptor index, requires query descriptors for retrieval, and degrades safely for missing or invalid index data.
- Anchor verification now computes matcher evidence from frame/tile keypoints through `KeypointRansacMatcher`, reports runtime/quality metrics, and routes computed evidence through the existing freshness, provenance, inlier, MRE, and homography gates.
- `VioRuntimeConfig` derives native mode for `production` and `jetson` profiles and rejects replay mode for those environments.
- `create_vio_adapter` selects `ConfiguredNativeVioBackend` for native profiles and keeps replay execution behind explicit replay mode.
- `BasaltNativeRunner` loads an installed BASALT-compatible runtime factory from the configured module/function reference and validates the returned runner against `NativeVioRunner`.
- Missing BASALT runtime prerequisites surface as explicit VIO initialization errors with failed health and no emitted VIO state packet.
- Satellite retrieval and anchor verification remediation from AZ-241 and AZ-242 remains covered by the existing native retrieval/matching evidence and tests.
## Marker Scan
Checked changed component source for unresolved implementation markers:
Checked `src/**/*.py` for unresolved implementation markers:
- `src/vio_adapter`: clean
- `src/satellite_service`: clean
- `src/anchor_verification`: clean
- `TODO`
- `placeholder`
- `stub`
- `fake`
- `mock`
- `scaffold`
- `native bridge`
- `NotImplemented`
- bare `pass`
Result: clean.
## Verification
- `python3 -m pytest tests/unit/test_vio_adapter.py tests/unit/test_satellite_service_vpr.py tests/unit/test_anchor_verification.py`: 19 passed.
- `python3 -m pytest`: 58 passed.
- `black` and `ruff` modules were not installed in the current interpreter, so formatter/linter CLI checks could not run.
## Required Follow-Up
Autodev must return to Step 7, rerun the Product Implementation Completeness Gate under the stricter rules, create remediation tasks sized at 5 points or less, and implement the missing runtime behavior before Step 8 or Step 11 may pass.
## Remediation Tasks
- `AZ-243_integrate_production_native_vio_runtime` was created to close the AZ-240 native VIO runtime gap and return Step 7 to product implementation.
- `python3 -m black src/vio_adapter tests/unit/test_vio_adapter.py tests/blackbox/test_vio_replay.py`: completed.
- `python3 -m ruff check src/vio_adapter tests/unit/test_vio_adapter.py tests/blackbox/test_vio_replay.py`: passed.
- `python3 -m pytest tests/unit/test_vio_adapter.py tests/blackbox/test_vio_replay.py`: 13 passed.
- `python3 -m pytest`: 87 passed.