The engine as a product

Root-cause analysis your organisation can click through

Fishbone diagrams end as a slide. causa keeps the same structure, problem domains branching into causes and effects, but makes every node interactive, every claim evidence-linked, and every verdict about actionability explicit. The graph you can open on this site is the flagship reference implementation; the engine behind it is topic-agnostic.

What changes when a diagram becomes a graph

A static diagram asks the reader to trust the author. A causal graph asks the author to show the evidence: which analysis supports this mechanism, which number quantifies it, and whether anyone has yet checked. Findings your organisation has validated look different from hypotheses still under investigation, and a reviewer can tell the two apart at a glance. That audit-grade distinction is the point.

The same model, your vocabulary

Whitelabel by design

No topic content lives in the code. Fields, claims, the roster and the blacklist are data; colours, type and spacing are one token file. A client deployment is a data import and a token swap, not a fork. One graph instance maps one topic, so each engagement gets its own graph with its own trusted voices.

What it is not, yet

There is no multi-tenancy, no user management and no hosted offering. The engine runs locally against one database and syncs its curated data to a repository. Those are known destinations, not current features, and they are listed here so the demo is not mistaken for a service.