nasa/ogma

OGMA is a specialized domain tool for generating runtime monitors from formal specifications in aerospace/robotics—a niche but defensible market position. With 553 stars and zero recent velocity, it shows adoption within its specialized community (NASA, aerospace contractors) but is not actively maintained. The project combines temporal logic parsing (ANTLR) with monitor synthesis, which is novel in application domain but built on established formal methods research. DEFENSIBILITY: Score of 7 reflects infrastructure-grade tooling for a specific, regulated domain. Real users exist (NASA, flight safety teams), and there is technical depth in formal specification handling. However, zero recent commits suggest maintenance risk. The domain expertise and regulatory context provide switching costs—competitors would need to build similar assurance evidence—but the codebase itself is not growing. PLATFORM DOMINATION: Low risk. Major platforms (AWS, Azure, GCP) don't directly compete in safety-critical monitor synthesis. OpenAI/Anthropic are not targeting aerospace certification tooling. This is too domain-specific and regulated for generic cloud platforms to absorb. MARKET CONSOLIDATION: Medium risk. Aerospace/robotics safety is dominated by a few large integrators (Lockheed, Boeing, Raytheon) and specialized tool vendors (model-checking companies, formal methods firms). A well-funded competitor or acquisition by a tier-1 defense contractor is plausible if OGMA gains more traction. The project would be attractive as an in-house tool for organizations needing runtime assurance. DISPLACEMENT HORIZON: 3+ years. The regulatory capture and domain expertise provide a buffer. Formal methods adoption in aerospace is slow but deepening. However, zero velocity and stalled maintenance suggest the project risks becoming irrelevant if not actively developed. New competitors (commercial formal verification tools) have time to enter the space. COMPOSABILITY: Strong. OGMA is designed as a generator (takes specs, outputs monitors), making it a reusable component in a larger verification pipeline. Can be integrated into CI/CD or safety workflows. IMPLEMENTATION DEPTH: Beta-grade. The tool is functional and deployed in real systems but shows no active maintenance (0 velocity in 1705 days). Runtime monitors are likely battle-tested in aerospace contexts, but lack of updates suggests deprecated dependencies or stalled development. NOVELTY: Novel combination. Temporal logic-to-monitor synthesis is established research, but applying it at scale to flight-critical systems with NASA-grade tooling is a meaningful combination. Not a breakthrough, but valuable in context. KEY RISKS: Maintenance vacuum. A 4.7-year-old NASA project with zero recent activity is vulnerable to technical debt, deprecated dependencies, and loss of institutional knowledge. If key maintainers leave NASA or shift priorities, the project could become unmaintained. Displacement risk rises if a competitor (or internal tool at a major contractor) provides the same capability with active support.