[AZ-243] Update autodev state and dependencies table

- 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.
2026-06-21 07:01:14 +00:00 · 2026-05-06 23:57:09 +03:00
parent cab7b5d020
commit 3d2c22d8ba
4 changed files with 108 additions and 7 deletions
@@ -1,8 +1,8 @@
 # Dependencies Table

 **Date**: 2026-05-05
-**Total Tasks**: 24
-**Total Complexity Points**: 108
+**Total Tasks**: 25
+**Total Complexity Points**: 113
 **Lessons applied**: No `_docs/LESSONS.md` file exists; no prior estimation or dependency lessons were available.

 | Task | Name | Complexity | Dependencies | Epic |
@@ -22,9 +22,10 @@
 | AZ-231 | anchor_verification_matching | 5 | AZ-223, AZ-225, AZ-230 | AZ-215 |
 | AZ-232 | safety_anchor_state_machine | 5 | AZ-223, AZ-224, AZ-227, AZ-228, AZ-231 | AZ-216 |
 | AZ-240 | native_vio_backend_integration | 5 | AZ-228 | AZ-213 |
+| AZ-243 | integrate_production_native_vio_runtime | 5 | AZ-240 | AZ-213 |
 | AZ-241 | real_satellite_vpr_descriptor_retrieval | 5 | AZ-230 | AZ-214 |
 | AZ-242 | real_anchor_feature_matching_ransac | 5 | AZ-231, AZ-241 | AZ-215 |
-| AZ-233 | test_infrastructure | 5 | AZ-240, AZ-241, AZ-242 | AZ-218 |
+| AZ-233 | test_infrastructure | 5 | AZ-243, AZ-241, AZ-242 | AZ-218 |
 | AZ-234 | replay_geolocation_confidence_tests | 3 | AZ-233 | AZ-218 |
 | AZ-235 | vio_replay_performance_tests | 5 | AZ-233, AZ-240 | AZ-218 |
 | AZ-236 | satellite_anchor_cache_tests | 5 | AZ-233, AZ-241, AZ-242 | AZ-218 |
@@ -42,7 +43,7 @@
 ## Test Coverage Verification

 - AZ-234 covers FT-P-01, FT-P-02, and NFT-PERF-01.
- AZ-235 covers FT-P-03 and NFT-PERF-02 after AZ-240 provides the real native VIO path.
+- AZ-235 covers FT-P-03 and NFT-PERF-02 after AZ-243 provides the real native VIO path.
 - AZ-236 covers FT-P-04, FT-N-01, FT-N-03, NFT-PERF-03, NFT-RES-04, NFT-SEC-01, NFT-SEC-02, NFT-SEC-04, and NFT-RES-LIM-03 after AZ-241 and AZ-242 provide real VPR retrieval and anchor matching.
 - AZ-237 covers FT-N-02, NFT-RES-01, and NFT-SEC-03.
 - AZ-238 covers NFT-RES-02, NFT-RES-03, NFT-PERF-04, and NFT-RES-LIM-05.
@@ -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.
@@ -40,3 +40,7 @@ Checked changed component source for unresolved implementation markers:
 ## 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.
@@ -7,8 +7,8 @@ name: Implement
 status: in_progress
 tracker: jira
 sub_step:
-  phase: 15
-  name: product-completeness-gate
-  detail: "Reset after failed reality check: VIO/A-Z runtime path is scaffolded; tests passed stubs/contracts instead of actual system behavior"
+  phase: 1
+  name: parse
+  detail: "Remediation task AZ-243 created from product completeness gate; resume product implementation"
 retry_count: 0
 cycle: 1