See connected exposure
Bring hazards, operations, assets, infrastructure, and economic dependencies into one decision context.
Explore propagation paths, time horizons, uncertainty, and intervention scenarios before decisions become urgent.
Bring hazards, operations, assets, infrastructure, and economic dependencies into one decision context.
Trace how a local event can accumulate, amplify, or transfer impact across systems and time.
Compare options using transparent evidence, uncertainty, and the outcomes that matter to your organisation.
A useful cascade scenario connects a triggering event to the exposed network, the path of propagation, the resulting operational or financial consequences, and the interventions that could alter the outcome.
Connect signals, data, and domain context.
Represent dependencies as a living network.
Explore propagation and intervention scenarios.
Prioritise decisions and communicate the evidence.
A clear framework for sources, coverage, refresh cadence, provenance, and permissions.
A structured view of relationships across assets, organisations, places, and systems.
A consistent approach to baseline, shock, adaptation, and mitigation scenarios with uncertainty.
A framework for role-specific views, collaboration, reports, and auditable recommendations.
A structured path for APIs, data connectors, exports, identity, and enterprise workflows.
A framework for security, responsible AI, model documentation, and compliance evidence.
The framework keeps data provenance, model validation, uncertainty, research, and decision outcomes visible as evidence is verified and published.
These answers describe the current operating principles. Product-specific sources, controls, integrations, and documentation will be published as they are confirmed.
DominoRisk is designed to combine organisation-authorised data with appropriately licensed public and commercial sources. Sources, refresh cadence, provenance, permissions, and permitted uses will be documented for each deployment.
Validation is proportionate to the decision context. Documentation will identify assumptions, uncertainty, data limitations, applicable back-testing or sensitivity analysis, expert review, and the conditions under which a model should not be used.
Implementation begins with the decision, users, data permissions, and required outputs. Available integrations and export formats will be documented as they are released rather than implied in advance.
Sensitive or confidential information should not be submitted through the public website. Production security and privacy controls will be documented in the Trust Centre before they are relied upon for protected data.
An upcoming framework for examining connected exposure, propagation, and intervention.
Read moreA forthcoming practice note on turning signals into decision-ready context.
Read moreAn upcoming briefing on how dependency mapping supports resilience planning.
Read moreExplore how connected signals, models, and decision workflows could support your organisation.