How one event spreads. Mapped, sourced, and checked later.
StratIQX publishes 341 cascade analyses. Each case traces how one event moved through six parts of an organization or sector, links every claim to its source, ships the CAL code that scored it, and, when it makes a prediction, sets a date to check it.
Reading a mark
Six columns, one per dimension. The large dot is the origin, where the event started. Each row down is the next layer of effects. In UC-342, 719 machine-written proofs began in Quality, reached Employee and Operational next, then Regulatory and Customer. Revenue is not scored, so its column stays empty.
Diagnostic
Something broke. The case traces back to the origin and forward to the damage.
Amplifying
Something is working. The case maps how success in one dimension compounds in others.
At risk
The numbers look good, but there is a weakness inside the success that could cascade.
Prognostic
A prediction with named triggers and a review date. These are the cases that get graded.
The record
A prediction is only useful if someone goes back and checks it. These are the calls that have been graded, including any that did not hold, and the ones still waiting.
68 reviews are scheduled in all.
How a case is made
The same pipeline runs for every case. The analysis is written in CAL, a small language for cascade scoring, and the page is compiled by RECALL, so any score on a case page can be traced back to the line that produced it.
- TriggerAn event worth tracing: a deal, a ruling, a release, a strike.
- SourcesResearch, with a dated link for every claim.
- CAL analysisDimensions scored, cascade ordered, FETCH computed.
- RECALL compileThe case page is generated from the analysis.
- Fact checkEvery claim in the brief is checked again before publishing.
- PublishLive at its own address, uc-NNN.stratiqx.com.
- ReviewPrognostic cases are reopened on their review date.
More on scoring and reviews on the method page. The full method is at 6d.semanticintent.dev, and CAL at cal.stratiqx.com.
Working together
If one of these cases is close to something you are dealing with, write. There are three ways this usually goes.
A case on your question
One event, traced through the six dimensions, with sources. Published to the library or kept private.
A running series
One sector or theme followed over time, with cross-case patterns and scheduled reviews.
The pipeline itself
Help building the same kind of system for your own team: structured input, generated output, and results you can check later.