Military OS product walkthrough
Produced September 20, 2026, using synthetic local captures from September 20, 2026.

Product roadmap
This walkthrough summarizes the current Military OS roadmap using the maintained product direction and local planning documents.
The product is one maintained codebase with separately configured deployments, centered on people, memberships, chapters, events, awards and association administration.

1. Close the security evidence gaps
The first active track is security baseline follow-through: complete recovery targets and realistic-volume exercises, verify a representative hosted environment, and finish the operational procedures around operator access, monitoring and incident response.
The public Security page separates implemented work, local checks, hosted verification and remaining work. This roadmap item does not change the current evidence snapshot.

2. Prepare a funded hosted environment
The hosted launch track keeps demonstrations local until a paying client or explicitly funded pilot covers the recurring infrastructure cost and authorizes an isolated environment.
Before launch, the product must pass callback, database TLS, configuration, migration, health, monitoring, backup, rollback, authentication, email and enabled-payment checks. CloudFormation completion alone is not a launch decision.

3. Add the next operational foundations
Additional active roadmap areas include optional seminar PDF text extraction with page provenance and evaluation of a real configured model on authorized material.
Online event phase two is a separate provider-neutral track for embedded meetings, scoped host and attendee capabilities, and an explicit decision about recording, transcription and other extra infrastructure.

4. Keep candidate ideas separate
After the awards foundation, further policy variations, scheduling, voting and shipping or medal-order fulfilment are recorded as candidate operations, not approved implementation slices.
Safe profile previews and customer-funded deployment locks also need their own scope and approval. The roadmap distinguishes current product behavior, active work and ideas that remain uncommitted.