// QUESTION CLASS

What changed, and does it matter?

Most intelligence consumers drown in headlines. The Current Developments 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 Anticipatory engine — and it does not re-establish baselines — that's Foundational. It reports.

Current Developments

"What is changing in [country]'s cyber-operational posture week over week? Route alerts when indicator crosses threshold."

Current Developments

"Monitor [named executive] for public statements regarding [topic]. Daily digest with source citations."

Current Developments

"Track [regulatory body]'s rule-making activity around [sector]. Flag material changes; suppress procedural noise."

Current Developments

"Observe [entity]'s supply chain for disruption signals. Alert on deviations from six-month baseline."

// ANATOMY

A Current Developments report contains:

A Current Developments 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.

§ 01

Change Summary

1–2 paragraphs, what moved since last cycle

§ 02

Indicator Readings

Named indicators with current values and deltas

§ 03

Source Coverage

How many sources scanned, by type

§ 04

Noise Filtered

What was suppressed as routine

§ 05

Tripwires

Anything that crossed a pre-declared threshold

§ 06

What to watch

Forward-looking leading indicators for next cycle

// AN INDICATOR READING

Rolling indicators, live.

INDICATOR DASHBOARD

// VISUAL · PHASE 2B

// WORKED EXAMPLE

From question to brief.

// THE KIQ

"Monitor [country]'s visible-and-public cyber posture indicators against the rolling 90-day baseline. Daily cadence. Alert on threshold crossing."

// PIPELINE TRACE

// INTAKE
PIOT complete. Population: [country] · Indicator: cyber posture
Outcome: posture delta · Timeframe: daily

// DECOMPOSITION
12 sub-indicators identified from baseline:
  · Public statements (MFA, defense ministry) — 2 indicators
  · Force posture signals (exercises, deployments) — 3 indicators
  · Legal/doctrinal changes — 2 indicators
  · Private-sector activity (cyber firms tied to state) — 3 indicators
  · Allied/partner mirroring behavior — 2 indicators

// RUN
Cycle: 2026-04-23 00:00Z – 24:00Z
Sources scanned: 1,847
Sources incorporated: 113
Indicators with movement: 3 of 12
Indicators crossing threshold: 1

// OUTPUT
Threshold crossing: Sub-indicator 7 (doctrinal change)
Delta: Moderate
Confidence: Supported by three independent sources of varied reliability

// SAMPLE OUTPUT EXCERPT

Over the reporting period, [country]'s Ministry of Defense published revised cyber-defense doctrine emphasizing preemptive response authority.¹ This represents a posture shift from the previous doctrine (dated 2024-07), which characterized response as reactive-only.² The change was accompanied by coordinated public statements from two deputy ministers.³ No change in force posture indicators was observed. Sub-indicator 7 (doctrinal change) has crossed the pre-declared material-change threshold.

// 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 assumption

Signal 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 Warning

Source 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 Requirements

Often paired with: Foundational (baseline), Anticipatory (response to threshold crossing).

// AUTHORED BY