Situational Intelligence.
Rolling updates on topics, actors, and regions. What's new, what changed, and what matters now.
- TYPICAL CADENCE
- Daily, hourly, or on-event
- TYPICAL SOURCE COUNT
- 500–2,000 per cycle
- TYPICAL OUTPUT LENGTH
- 300–800 words + indicator deltas
- TYPICAL CONFIDENCE REGISTER
- Descriptive, not estimative
// QUESTION CLASS
What changed, and does it matter?
Most intelligence consumers drown in headlines. The Situational Intelligence engine is built for the opposite problem: when the question is "what actually moved," most of what's in front of you is noise. This engine is a monitoring product, not an investigation. It runs on a rolling cadence | daily, hourly, or on-event | against a stable question and a defined source horizon. Every update is delta-focused: what's new, what's consistent with prior baselines, and what crosses a threshold that an analyst pre-declared. This is the engine you use when the KIQ is persistent. It runs until you turn it off. The output shape is short: a summary of change, a set of indicator readings, the sources that drove each, and the confidence in the reading. It does not speculate about future paths | that's the Forecast engine | and it does not re-establish baselines | that's Baseline. It reports.
// ANATOMY
A Situational Intelligence report contains:
A Situational Intelligence report is shorter than the others because it's recurring. The job is to tell you what's different, not to re-explain what you already know. Every report references the prior cycle and flags material changes. Indicators are pre-registered; the engine reports on them whether they moved or not, which prevents the omission that comes from "nothing new to report." Sources are attributed per indicator, so a reader can trace a delta back to the specific document that produced it.
// TRADECRAFT
The engine is built around thresholds, not guesses.
Pre-registered indicators.
Before the monitoring run begins, the Intake defines the specific indicators to watch — both their readings and the thresholds that constitute material change. This is how you eliminate confirmation bias in a monitoring product. If it's a threshold today, it was a threshold before the thing happened.
ICD 203 · Standard 3: Distinguishes intelligence from assumptionSignal and noise are both reported.
A report that says "nothing changed" is an output. The engine does not silently omit cycles where nothing happened. Absence of change is itself information, and concealing it creates the illusion of activity. Every cycle, every indicator, reported — moved or not.
I&W Methodology · Indications and WarningSource attribution per indicator.
Each indicator reading is tied to the specific source passage that drove it. If a delta came from a single source, that single source is named and its reliability stated. If it came from multiple, each is cited. A reader can replicate the reasoning without running the engine.
ICD 206 · Sourcing RequirementsOften paired with: Baseline, Forecast (response to threshold crossing).
// OTHER ENGINES