[AZ-219] [AZ-228] Generalize VIO component layout

Keep VIO package and native bridge paths backend-neutral so BASALT remains an implementation choice rather than a component boundary.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
Oleksandr Bezdieniezhnykh
2026-05-03 12:20:41 +03:00
parent 79997e39ac
commit 72a9df6b57
34 changed files with 123 additions and 114 deletions
+3
View File
@@ -0,0 +1,3 @@
# Anchor Verification Native Bridge
Reserved for native feature extraction, matching, and RANSAC acceleration code owned by `anchor_verification`.
-1
View File
@@ -1 +0,0 @@
"""BASALT VIO adapter component."""
-3
View File
@@ -1,3 +0,0 @@
# BASALT Bridge
Reserved for native BASALT integration code wrapped by `basalt_vio_adapter`.
-3
View File
@@ -1,3 +0,0 @@
# Feature Matching Bridge
Reserved for native feature extraction, matching, and RANSAC acceleration code.
-3
View File
@@ -1,3 +0,0 @@
# TensorRT Bridge
Reserved for Jetson/TensorRT descriptor inference integrations.
+3
View File
@@ -0,0 +1,3 @@
# Satellite Service Native Bridge
Reserved for ONNX/TensorRT descriptor inference integrations owned by `satellite_service`.
+1
View File
@@ -0,0 +1 @@
"""Replaceable VIO adapter component."""
@@ -1,4 +1,4 @@
"""Public BASALT VIO adapter interfaces."""
"""Public VIO adapter interfaces."""
from typing import Any, Protocol
+3
View File
@@ -0,0 +1,3 @@
# VIO Native Bridge
Reserved for native VIO backend integration code owned by `vio_adapter`.
@@ -1,4 +1,4 @@
"""Public BASALT VIO type aliases."""
"""Public VIO type aliases."""
from typing import Any