Apollo Avatar M1

Andi Lamprecht ·2026-05-11· 2 min read· Accepted

Avatars @ Milestone One.

Context

Milestone One is the planned first deployment of Apollo. In it, we focus on deploying most of the actors and establishing contracts between them. We leave a lot for later, notably:

• We support simulated UAVs only, so we don’t have to worry about this security perimeter.
• We think ensuring and exposing one Avatar per UAV may be difficult, so we start with just a traditional “static” k8s deployment and one Avatar per many UAVs.

This pulls the rug from under the Avatar Controller depriving it from the Inventory and the obligation to spawn Avatars. But it should maintain the contract it offers to the Missions Service, i.e.: return it an Avatar that’s connected to a (simulated or otherwise) UAV.

Decision

@Milestone One, the Avatar Controller shall maintain its target contract with the Missions Service and hide the absence of real UAVs, Inventory and cardinality of the Avatars.

As stated simulations aren’t the product of the AirBoss application. In MS1 they will be created by the CI/CD pipeline. AirBoss will simply be deployed with a number of simulated UAVs to furnish it with this organically limited resource. If needs be, anyone, like a tester or a test, can additionally spin new simulators manually to fit their needs.

Consequences

I keep on leaving this section empty. Maybe it’s not needed.

Alternatives Considered

Nothing else came to mind, open to suggestions.