Assurance Forge
Assurance Forge is an open-source tool for creating, reviewing, and maintaining structured assurance cases and safety cases.
The application is built in C++ using Dear ImGui and is designed around structured argumentation concepts such as SACM and GSN.
Alpha software
Assurance Forge is under active development. SACM XML is the source of truth and preserving it is a primary design constraint, but keep your assurance data in version control and keep backups. What is claimed, per capability and with the tests behind it, is the capability matrix; if a capability is not there, treat it as not claimed.
-
SACM-First Foundation
Consumes and produces SACM 2.3 XML through an independent, reusable SACM library. An edit the standard cannot express is refused, not approximated.
-
GSN Visualization
Structured safety arguments rendered automatically — including pattern, dialectic and ACP notation. No manual node positioning.
-
AI-Assisted Review
Provider-agnostic AI with configurable profiles evaluates arguments and identifies weaknesses. Nothing is sent without your explicit action.
-
SCCG Integration
Safety Case Core Guidelines built into review, into mechanical checks, and into the guidance an external AI client is given.
-
Your Own AI Client, Over MCP
An AI client you run yourself can read the case and propose changes — landing in a working draft a human accepts, never applied behind your back.
-
Audited by Construction
Every edit is a replayable transaction with undo boundaries, baselines, snapshots, and a timeline that reconstructs the argument as it stood.
-
Two Languages, Reviewed
Arguments carry a second language end to end; machine-translated text is held for an explicit reviewer acceptance.
-
See what is stable, what is planned next, and what is on the long-term horizon.
Documentation
- User Guide — open a project, navigate and edit the argument, review it, work with evidence, export, and connect an AI client.
- Features — the capability matrix plus per-feature documentation: terminology assist, the MCP server, the confidence panel.
- Standards — SACM 2.3 conformance, GSN v3 conformance, the SACM–GSN mapping, and the verification records behind them.
- Architecture — component layout, layers and ownership, and the decision records.
- Developer Guide — building, testing, generating diagrams, and the repository's own quality evidence.
Not sure which page is authoritative? The documentation map says which document wins on conflict.