Your own repo
The default. Build a plugin, sign it with your own key, and publish it on a GitHub release. Operators install the downloaded file, or install by URL from GitHub (see URL install). Altnautica does not gate this channel; each agent gates trust through its enrolled publisher keys. You decide the licence, release cadence, supported boards and support policy. The agent enforces the manifest schema and the permission model.First-party extensions
altnautica/ADOSExtensions is the public monorepo for first-party extensions that Altnautica builds and signs. Inclusion is by invitation. The bar:
- Generic: useful to most operators, not a niche feature for one user.
- GPL-3.0-or-later: the repo’s licence.
- Tested: unit tests at minimum, with a mock backend for any hardware.
- Maintained: the maintainer triages issues and ships security fixes.
- Reviewed: the code passes review against the public repo’s content rules (technical scope only, no marketing copy).
ADOSExtensions describing the plugin and link a working repo. We will review it and either bring it into the monorepo or explain how to submit once third-party submissions open.
Filing host issues
Bugs in the plugin host belong in the host repos:- Agent host:
altnautica/ADOSDroneAgent - Mission Control host:
altnautica/ADOSMissionControl
.adosplug that reproduces the bug whenever possible. Security issues go through the private channel on Revocation and incidents, not a public issue.
Docs drift
If a manifest field, capability or slot id is documented one way here and behaves differently in the host code, the code is authoritative. File an issue againstaltnautica/Documentation and we will reconcile.
Discussion
Ask questions on Discord: discord.gg/uxbvuD4d5q. Other channels are on Community.Next steps
Contributing
Setup, branches and pull requests.
Open source
Repositories and licences.