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

[AZ-243] Update autodev state and dependencies table

Browse Source 
- Changed the autodev state to reflect the new phase and task name for remediation related to AZ-243.
- Updated the dependencies table to include the new task AZ-243 and adjusted dependencies for AZ-233.
- Added a section in the implementation completeness report to document the creation of the AZ-243 remediation task aimed at integrating the production native VIO runtime.
This commit is contained in:
Oleksandr Bezdieniezhnykh
2026-05-06 23:57:09 +03:00
parent cab7b5d020
commit 3d2c22d8ba
4 changed files with 108 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
_docs/02_tasks/todo/AZ-243_integrate_production_native_vio_runtime.md
+96
View File
@@ -0,0 +1,96 @@
# Integrate Production Native VIO Runtime
**Task**: AZ-243_integrate_production_native_vio_runtime
**Name**: Integrate Production Native VIO Runtime
**Description**: Close the VIO completeness gap by making production VIO execution use a real native runtime path instead of replay/scaffold behavior.
**Complexity**: 5 points
**Dependencies**: AZ-240_native_vio_backend_integration
**Component**: VIO Adapter
**Tracker**: AZ-243
**Epic**: AZ-213
## Problem
The VIO adapter exposes a native backend boundary, but the product completeness gate found that production behavior still does not execute a real native/BASALT VIO runtime. This lets downstream tests pass against scaffold behavior while the promised runtime capability is missing.
## Outcome
- Production VIO configuration selects and executes a real native runtime path.
- Missing native prerequisites fail closed with explicit configuration or runtime errors.
- Replay-only behavior remains available only for replay/development modes that explicitly opt into it.
## Scope
### Included
- Production native VIO runtime selection behind the VIO adapter boundary.
- Explicit startup/runtime errors when native runtime prerequisites are missing or invalid.
- Preservation of replay behavior for replay-only tests and development workflows.
- Tests proving production configuration does not silently fall back to replay behavior.
### Excluded
- Absolute WGS84 authority or safety fusion.
- Satellite-anchor fallback logic.
- Jetson performance tuning beyond reporting the native runtime prerequisite state.
## Dependencies
### Document Dependencies
- `_docs/02_document/components/02_vio_adapter/description.md`
- `_docs/02_document/contracts/shared/runtime_contracts.md`
- `_docs/02_document/contracts/shared/config_errors_telemetry.md`
- `_docs/03_implementation/implementation_completeness_cycle1_report.md`
## Acceptance Criteria
**AC-1: Production profile requires native VIO**
Given the system is configured for production VIO execution
When VIO initialization runs
Then the adapter selects the native runtime path and does not silently use replay behavior.
**AC-2: Missing native runtime fails closed**
Given production VIO configuration and an unavailable or invalid native runtime prerequisite
When VIO initialization or processing runs
Then the adapter reports an explicit configuration or runtime failure instead of emitting a successful replay-derived VIO state.
**AC-3: Replay mode remains explicit**
Given a replay-only development or test configuration
When VIO processing runs
Then replay behavior remains available only through that explicit mode and cannot be mistaken for production native execution.
## Non-Functional Requirements
**Reliability**
- Production startup must not hide missing native VIO capability behind deterministic or replay fallback success.
**Compatibility**
- Existing public VIO adapter contracts must remain stable for downstream safety, FDR, and test consumers.
## Unit Tests
| AC Ref | What to Test | Required Outcome |
|--------|--------------|------------------|
| AC-1 | Production VIO configuration | Native runtime path is selected, not replay fallback |
| AC-2 | Missing native runtime prerequisite | Explicit failure is surfaced and no successful replay-derived state is emitted |
| AC-3 | Replay-only configuration | Replay path works only when explicitly configured |
## Blackbox Tests
| AC Ref | Initial Data/Conditions | What to Test | Expected Behavior | NFR References |
|--------|-------------------------|--------------|-------------------|----------------|
| AC-1, AC-2 | Representative synchronized replay with production VIO profile | Runtime path selection and prerequisite handling | Native execution runs when available, or blocks with a real prerequisite reason | Reliability |
## Constraints
- Keep backend-specific dependencies behind the VIO adapter native boundary.
- Do not make the VIO adapter the safety or WGS84 authority.
- Do not satisfy production runtime behavior with a fake, deterministic, scaffold, or test-only backend.
- If local machines cannot execute the native runtime, tests must skip or block with an explicit prerequisite reason rather than passing through replay fallback.
## Risks & Mitigation
**Risk 1: Native runtime unavailable in local CI**
- *Risk*: The real native VIO runtime may not be installed on all developer machines.
- *Mitigation*: Gate native execution tests on explicit prerequisites, while still testing that production configuration fails closed when prerequisites are absent.