Case Studies¶
Case studies → outcomes
Theory is cheap. Decision-grade outcomes are not.
These case studies show what changes when systems are built around causal memory, enforceable constraints, and traceability. The common thread: reliability becomes a system property, not a prompt suggestion.
How to read these
These are representative patterns.
They illustrate the mechanism: provenance → constraints → traces → auditable decisions.
flowchart LR;
D["Domain"] --> M["Causal memory"];
M --> G["Constraint gate"];
G --> T["Trace objects"];
T --> O["Auditable decisions"];Curated case studies
Biomedicine
Mechanism discovery: connecting entities into testable causal chains beyond document similarity.
Finance
Compliance by design: constraints make policy violations impossible and produce audit-ready traces.
Legal
Contract logic conflicts: graph structure surfaces contradictions and hidden dependencies.
High-value verticals we also focus on
Insurance
Claims and underwriting under hard constraints, with traceable evidence and deterministic abstention.
Cybersecurity
SOC decision support: evidence paths, playbook constraints, and incident traces you can replay.
Manufacturing
Quality and root-cause analysis: causal chains across process steps, suppliers, and sensor evidence.
Energy & Utilities
Grid operations: safety gates, operating constraints, and replayable incident reasoning.
Pharma / Clinical Ops
Protocol and safety constraints with inspection-ready evidence paths and deterministic escalation.
Enterprise central memory
Meetings and projects as governed decision artifacts: owners, assumptions, constraints, and change logs.