ODK

Stator Open Labs

OMS Developer Kit

Scaffold an OMS mission-systems service, pin the platform libraries, run shared CI and UCI conformance, then bring up a local bus and watch traffic. One kit, two languages, a single path from empty directory to a heartbeat on the wire.

Why this exists

What the kit solves

A mandated lifecycle

OMS services are not ordinary microservices. They publish ServiceStatus heartbeats, answer status data requests, run BIT, and shut down through the CAL. The templates and runtimes own that plumbing so you write domain logic.

One contract, two languages

Rust and Python share the same Service model, OWP transport, and schema pin. Pick a language; keep the same CI umbrella, the same Gherkin harness, and the same local bus.

Schemas stay upstream

UCI and A-GRA types are generated at build time from Open Arsenal. The kit does not relicense Government Owned XSDs.

How it fits

From scaffold to live traffic

Author

service-template-rust
service-template-python

Depend

platform-crates
platform-pylib

Prove

pipelines-oms
cucumber-uci

Run and observe

Skylark
PostMaster
Open Arsenal — UCI / A-GRA XSDs at build time (not vendored)

templates → platform libraries → CI + harness · Skylark deploys the bus and collector

Pick a path

Get a service running

After you have a service, run the stack with Skylark and watch the bus in PostMaster. New to the vocabulary? Start with Concepts.