Manifesto
Why we're building Lemmatica
The tools used to argue that systems are safe to operate should be as rigorous as the systems themselves. We started Lemmatica because they aren't.
The problem
Assurance cases — safety, security, ethical — these documents argue why systems are safe to operate, secure to deploy, ethical to release. They underpin decisions in defence, aerospace, autonomous vehicles, medical devices, and critical infrastructure.
Yet the tools available to build them are stuck in a previous decade. Desktop-only editors tied to a single workstation. No real-time collaboration. Manual file merging when two people work on the same argument. Validation only at review time, long after structural errors were introduced. Interfaces that feel like they were designed for Windows XP and never revisited.
Teams building safety-critical systems operate under enormous scrutiny. Their tooling should match that standard. Instead, they spend time fighting file formats, reconciling divergent copies, and re-learning unintuitive interfaces — time that should be spent strengthening arguments.
They are, by definition, high-stakes documents.
What we believe
Assurance argumentation deserves the same quality of tooling that software engineers expect from their code editors, that designers expect from Figma, and that teams expect from modern project management. The bar has been raised everywhere else.
The people building safety-critical systems — the engineers, the assessors, the reviewers — shouldn’t have to fight their tools. They should be able to focus entirely on the quality of the argument itself.
Assurance case development should not be the exception.
How we’re building it
Lemmatica is web-native and collaborative-first. No installers, no file syncing, no version conflicts. Open a browser and your team is working on the same argument in real time, with live cursors, presence indicators, and instant structural feedback.
We implement full GSN V3 compliance with dialectic extensions — including challenge nodes and defeat tracking. Continuous structural validation catches errors as you build, not weeks later at review. Evidence traceability links claims to their supporting artefacts. Auto-layout keeps complex hierarchies readable.
If it doesn’t help teams build stronger arguments, it doesn’t ship.
Every design decision starts from the same question: does this help teams build stronger arguments?
What’s next
This is v0.1.0 — an alpha. The foundation is solid, but there is a long road ahead.
We are committed to open standards, community-driven development, and making assurance argumentation accessible to every team that needs it — not just those with the budget for legacy enterprise software. Lemmatica is built by OpenForte, based in Canberra, Australia.
We’re building in the open, iterating quickly, and shaped by the people who actually use this tool day to day.
Ready to modernise your assurance cases?
Join high-assurance teams building with confidence. Free during beta.