FROM SIGNAL TO VERIFIED CONTEXT

1. Open the live terminal and choose one region or event from the headline feed.
2. Enable only the two or three relevant layers. Keep unrelated layers off so the map remains readable.
3. Open a marker and record its source, observation time, location, and freshness.
4. Compare it with one independent layer or the linked primary source.
5. If Analyze is available, use it to summarize the evidence. Verify the response against the cited data before relying on it.

Success: you can state what was observed, when it was observed, which source reported it, what corroborates it, and what remains uncertain.

• Military movement: military flights, airports, military installations, GPS jamming, ADS-B blackouts, and reported strikes.
• Maritime disruption: vessels, chokepoints, cables, weather, and published SAR candidates when available.
• Emergency context: shelter alerts, severe weather, earthquakes, fires, floods, volcanoes, and outages.
• Market context: chokepoints, conflict zones, commodities, market pulse, and active Market Signal Engines.

Layer availability, update interval, and geographic coverage differ. An empty layer can mean no qualifying event, stale data, source outage, or no coverage.

1. Observation: identify the measured or reported fact.
2. Source: follow the source link when available.
3. Time: distinguish event time from retrieval time.
4. Confidence: treat labels as evidence quality, not certainty.
5. Analysis: separate AI synthesis from source data.

Start with a narrow geographic question. Enable one baseline layer and one corroborating layer, then inspect only recent markers. Save source links outside ClaudeWar if the investigation requires a durable record. AI Operative members can use the Operative Hub for broadcasts, convergence, watchlists, and alert preferences.

1. Open the original source and confirm the timestamp and location.
2. Look for an independent source with a different collection method.
3. Check whether the card is live, delayed, inferred, or reported from a headline.
4. State uncertainty directly. Do not convert proximity into causation or intent.
5. For emergency, medical, aviation, maritime, or trading decisions, use the appropriate official authority.

ADS-B observations can be delayed, filtered, incomplete, or absent. A missing aircraft is not proof of a covert operation. GPS jamming and ADS-B blackout indicators describe telemetry patterns and coverage conditions; verify them against location, receiver coverage, and independent reporting.

Maritime intelligence combines coverage-qualified AIS, source age, confidence, and approved evidence where available. AIS visibility does not prove traffic or closure. Unmatched SAR contacts are candidates, not confirmed dark vessels or identities.

SAR analyst review and operational controls are not customer features. Published candidates appear only when the relevant feature flags and review requirements are satisfied.

ClaudeWar helps place weather and natural-hazard feeds beside other intelligence. It is not an emergency warning authority. Open the linked government source and follow local instructions before taking protective action.

AI Operative members can configure supported in-app, email, and Telegram alert categories in the Operative Hub. Delivery depends on source availability and channel configuration. Verify at least one test or recent notification before relying on a channel.