First regulated-adjacent deployment — start the service-history clock

[O6lvl4]

Part of #12 (Gap 3). Track-record rungs C1 and C3.

Why external

Product service history is certification currency and only accumulates in a real deployment. Smallsat flight software and UAS (specific category) have materially lower entry barriers than civil avionics and produce the right kind of operational record — but they require a design partner who flies Almide-generated code.

What is needed

• One partner running Almide (the flight profile, once Gap 2 — Certification seat: flight-profile requirements here first, keystones in the implementation, a qualified native toolchain in the chain #11 delivers it) in a space or UAS context.
• An in-service record format tied to the edition (Gap 4 — Baseline edition and content debt: the first tag, and a spec whose examples all compile #13) and to the known-problems ledger, in use from day one.

Exit

Almide code operating in a fielded system, with service history recorded in an audit-ready form.