What could go wrong around a subject, how it would propagate, and where the concentration sits.
3 credits·deep dive·about 3–6 min·11 domains
Name the subject: a company, a project, a supply arrangement, a program. It scores the exposure, maps the nodes in the network around it and the chains a disruption would travel along, names the critical vulnerabilities, the concentration risks and the shared dependencies, and orders the mitigations by priority.
Risk officers, operations leads, program managers and anyone signing off on something with many moving parts.
These are the headings the result renders, read from the same promise the form makes before you spend a credit. A section that depends on what the record holds is rendered when it can be and never promised here.
A risk is rated on what the record shows, not on how alarming it sounds. It is not a guarantee of coverage; a dependency the record does not document is listed as something the read cannot see.
A claim the scan could not source is marked as such rather than dressed up. How the grades work →
A domain may name it in its own words and price it on its own terms; each row is what that domain shows.
How Ukraine's strikes on Russian refineries are exposing critical vulnerabilities in Moscow's wartime logistics chain—a structural breakdown playing out in real time.
The fastest way to judge the result is to pick a subject you know cold and read it against what you know. The scan names its credit cost before it runs.