The full index lists six tasks planned as isolated packages: vision navigation, optical payload, follow-me, MAVLink gimbal, thermal camera and battery diagnostics. Each direction has its own reserved KairOS package ID.
The cards describe development directions; install-compatible packages and the KairOS registry have not yet been published.
KairOS repository ↗On this page +
Six KairOS extension directions
Vision Navigation
Optical flow and VIO for GPS-denied navigation; ArduPilot, PX4 and iNav; degradation ladder and safety fallback.
SIYI Optical Pod
A2/A8/ZR10/ZR30/ZT6/ZT30: gimbal, zoom, thermal, laser rangefinder and AI tracking.
Follow‑Me
Click-to-follow at a specified distance/height; stop on uncertain/lost targets; no automatic reacquisition.
MAVLink Gimbal v2
Manual, ROI and vision aim; component 154; external controller and universal board profiles.
FLIR Lepton
Radiometric Y16, palette, gain, FFC and thermal overlay for USB UVC integration.
Battery Health
Cell diagnostics, time-to-minimum, divergence, sag and temperature alerts; the panel remains read-only.
Package installation starts with verification
Choose a package
Check publisher, version, boards, firmware assumptions, third-party licenses and changelog.
Download the .kairosplug
The package comes from a trusted registry or an explicitly chosen local file.
Verify Ed25519
The host checks the signature and revocation status before extraction and execution.
Review capabilities
The operator sees hardware, MAVLink, mission and network permissions; sensitive grants are confirmed separately.
Install, then enable
Package installation is separate from execution; enable creates the sandbox process and health state.
kairos plugin install ./extension.kairosplug
kairos plugin info <name>
kairos plugin perms <name>
kairos plugin enable <name>A manifest ID cannot be renamed only in marketing copy
The ru.msk.bezpilota.kairos.* prefix establishes the ecosystem’s own package identity. The registry URL, manifests, update channel and grants must use the same ID; changes are allowed only through a versioned migration policy.
What an independent KairOS registry needs
- A public package schema and versioned SDK contracts.
- Publisher identity, signing root, rotation and revocation processes.
- Automated validation of manifests, dependencies, capabilities and license metadata.
- A board/firmware compatibility matrix with reproducible test results.
- Security review for MAVLink write, mission write, hardware access and network egress.
- Version pages, changelog, rollback path and incident notification.
- Separate labeling of experimental features, including GPS-denied operation, follow-me and autonomous gimbal control.