Write in the Studio
Author the model directly on the Studio canvas as FtaDSL/FmeaDSL — structured, versionable, instantly checkable.
From your architecture and failure model: fault tree (IEC 61025), FMEA, prioritized cut-sets, common-cause and report. Three ways to the model — editor, chat or from source code.
Deterministic engines — they compute, they don’t guess.
Safety analyses live in spreadsheets and drawing tools today — hand-maintained, hard to keep current, barely reproducible.
How you reach the model is your choice. What comes out the other end is always the same: a fault tree per IEC 61025 and an FMEA — computed, not guessed.
Author the model directly on the Studio canvas as FtaDSL/FmeaDSL — structured, versionable, instantly checkable.
rfChat produces the DSLs from your description. You state the case in words, the model takes structured shape.
rfRecover reconstructs the model from your source code. In pilot today — the entry point for existing codebases.
The target is the core: a fault tree (mcsa + fta-render) and an FMEA. The three ways are just how you get there.
Real and live today.
The analysis engines compute, they don’t guess. No black-box LLM decides your safety claim.
Cut-sets, common-cause and prioritization are calculated — traceable back to the source.
If something is missing from the model, it is reported as a gap — completeness instead of silent omission.
Same model, same result. Repeatable any time, defensible in every review.
RiskForge Studio produces artifacts that have their place in the relevant functional-safety standards.
Request Early Access or get in touch — we’ll show you the path from your model to a finished analysis.
Or directly: info@riskforge.studio