Oleksandr Bezdieniezhnykh c4eff40dbc [AZ-680] [AZ-681] operator_bridge command dispatch + safety lane
Add the operator-command dispatcher behind a typed CommandAck:
60 s per-command-id idempotency cache, surfaced-POI registry with
unknown_poi_id + expired gates, BIT-degraded ack severity check, and
SafetyOverride forwarding to mission_executor with structured audit
log (redacts signature + session_token).

Cross-layer wiring goes through three new traits in shared::contracts
(ScanCommandRouter, MissionSafetyRouter, BitReportSeverityLookup) so
operator_bridge stays free of direct scan_controller / mission_executor
imports. scan_controller::ScanControllerHandle implements the scan
router; a new mission_executor::SafetyDispatchHandle wraps the BIT
ack channel + battery monitor handle and implements the safety router;
BitControllerHandle gains a bounded (16-entry) report-severity cache
for the lookup trait.

scan_controller also picks up ConfirmPoi handling: PoiQueue::confirm
removes the entry and SubmitOutcome::Confirmed carries the typed
(target_mgrs, target_class) hint for AZ-684/AZ-686 downstream.

Tests: 9 new integration tests in operator_bridge/tests/dispatcher.rs
cover AZ-680 AC-1..AC-5 + AZ-681 AC-1..AC-4. scan_controller adds 2
ConfirmPoi tests. All modified-crate suites green; one pre-existing
mission_executor state-machine test flake (already documented in
_docs/_process_leftovers) updated to note ac1 also affected.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-05-20 17:32:59 +03:00

autopilot

Onboard mission executor for the AZAION reconnaissance UAV. Single Rust binary; runs on NVIDIA Jetson Orin Nano Super (aarch64). See _docs/02_document/architecture.md for the authoritative system design.

Layout

crates/
  shared/                # canonical DTOs, config, error, health, observability, clock, contracts
  autopilot/             # binary crate — runtime composition root + /health endpoint
  mavlink_layer/         # hand-rolled MAVLink v2 transport
  mission_client/        # missions API REST client + MapObjects sync
  frame_ingest/          # RTSP pull + decode
  detection_client/      # bi-directional gRPC to ../detections
  movement_detector/     # ego-motion-compensated residual-motion clustering
  semantic_analyzer/     # Tier 2 — primitive graph + ROI CNN
  vlm_client/            # Tier 3 — optional NanoLLM/VILA local IPC
  mapobjects_store/      # H3-indexed on-device map + ignored items
  gimbal_controller/     # ViewPro A40 UDP control
  scan_controller/       # central typed state machine (ZoomedOut/ZoomedIn/TargetFollow)
  operator_bridge/       # POI surface + operator command authentication
  mission_executor/      # multirotor + fixed-wing FSMs + geofence + failsafe
  telemetry_stream/      # always-on uplink to Ground Station

config/                  # TOML config per environment (dev / staging / prod)
deploy/systemd/          # on-airframe native systemd unit (Option A)
fixtures/                # replay clips (RTSP, MAVLink, missions, detections)
tests/e2e/               # workspace-level blackbox scenarios
benches/                 # NFR benchmark-gate harness

Build

# Host-arch build + tests
cargo build --workspace
cargo test  --workspace --locked

# Optional VLM feature path
cargo build --workspace --features vlm

# No-default-features path (enforces the VLM optionality contract)
cargo build --workspace --no-default-features
cargo test  --workspace --no-default-features

# aarch64 cross-build (CI uses cargo-zigbuild; locally `cross` also works)
cargo install --locked cargo-zigbuild
rustup target add aarch64-unknown-linux-gnu
cargo zigbuild --release --target aarch64-unknown-linux-gnu --workspace

Run (dev)

cp .env.example .env
docker compose up -d
# Then inspect:
curl -s http://127.0.0.1:8080/health | jq

Documentation

The full document tree lives under _docs/. Start with:

  • _docs/00_problem/problem.md — the problem statement
  • _docs/02_document/architecture.md — system architecture
  • _docs/02_document/system-flows.md — sequence diagrams
  • _docs/02_document/components/<name>/description.md — per-component specs
  • _docs/02_document/deployment/{containerization,ci_cd_pipeline,observability}.md

CI

.woodpecker.yml drives the pipeline. Stages: fetch → lint → unit-test → build-arm64 → build-no-vlm → integration-test → sitl-conformance → security-scan → package → sign → publish → benchmark-gate (opt-in).

S
Description
No description provided
Readme 58 MiB
Languages
C 58.6%
C++ 40%
QMake 1%
CMake 0.3%