mirror of
https://github.com/koala73/worldmonitor.git
synced 2026-04-26 01:24:59 +02:00
09a582e089
* fix(docs): correct variant count from 4 to 5 Updated overview.mdx and architecture.mdx to reflect all 5 platform variants (World Monitor, Tech Monitor, Happy Monitor, Finance Monitor, Commodity Monitor). Previously only 2 were listed in the table and the text said "four". * fix(docs): correct all numerical inaccuracies across documentation Updated counts verified against actual codebase: - AI datacenters: 111 → 313 - Undersea cables: 55 → 86 - Map layers: 45 → 49 - News sources: 80+ → 344 - Service domains: 22 → 24 - CII countries: 20 → 24 - Military bases: 210/220+ → 226 - Strategic ports: 61/83 → 62 - Airports: 30/107 → 111 - Chokepoints: 6/8 → 9 - Signal entities: 100+/600+ → 66 - Variant count: four → five (added Commodity Monitor) * docs(overview): add Happy, Finance, and Commodity Monitor sections Added detailed documentation sections for the three previously undocumented platform variants, including layers, panels, and news categories for each. * docs(features): document 13 previously undocumented features Added: trade routes, FIRMS fire detection, webcam surveillance, country brief, aviation intelligence panel, climate anomalies, displacement tracking, Gulf economies, WTO trade policy, central banks & BIS, market watchlist, NOTAM closure detection, and offline ML capabilities. * docs: standardize terminology, add cross-references, fix stale refs Phase 4: Renamed "News Importance Scoring" to "Headline Scoring", "Signal Correlation" to "Cross-Stream Correlation". Added cross-refs between CII/convergence, CORS/API-key, maritime/finance chokepoints. Deduplicated Population Exposure content. Clarified hotspot vs focal point distinction. Phase 5: Rewrote daily_stock_analysis as historical context. Added legacy note for api/*.js files. Added OREF 24h rolling history boost and GPS jamming classification thresholds to algorithms.mdx. Fixed orbital-surveillance tier table contradictions. Phase 6: Fixed orphaned markdown separator in orbital-surveillance. * fix(docs): catch remaining stale numbers in secondary doc files Fixed stale counts in data-sources.mdx, strategic-risk.mdx, documentation.mdx, ai-intelligence.mdx, PRESS_KIT.md, and roadmap-pro.md that were missed in the initial pass. * fix(docs): address review findings from fresh-eyes pass - desktop-app.mdx: "four variants" → "five", "22 services" → "24" - infrastructure-cascade.mdx: chokepoints 8 → 9, node total 279 → 350 - data-sources.mdx: chokepoints 8 → 9 - overview.mdx: remove duplicated intro sentence - getting-started.mdx: fix stale file tree comments (AI clusters, airports, entities)
120 lines
4.5 KiB
Plaintext
120 lines
4.5 KiB
Plaintext
---
|
||
title: "Infrastructure Cascade Analysis"
|
||
description: "Dependency graph modeling for critical infrastructure and undersea cable monitoring, visualizing how disruptions cascade across countries and systems."
|
||
---
|
||
Critical infrastructure is interdependent. A cable cut doesn't just affect connectivity; it creates cascading effects across dependent countries and systems. The cascade analysis and cable monitoring systems visualize these dependencies and provide early warning of disruptions.
|
||
|
||
## Dependency Graph
|
||
|
||
The system builds a graph of **350 infrastructure nodes** and dependency edges:
|
||
|
||
| Node Type | Count | Examples |
|
||
|-----------|-------|----------|
|
||
| **Undersea Cables** | 86 | MAREA, FLAG Europe-Asia, SEA-ME-WE 6 |
|
||
| **Pipelines** | 88 | Nord Stream, Trans-Siberian, Keystone |
|
||
| **Ports** | 62 | Singapore, Rotterdam, Shenzhen |
|
||
| **Chokepoints** | 9 | Suez, Hormuz, Malacca, Gibraltar, Bosphorus, Dardanelles |
|
||
| **Countries** | 105 | End nodes representing national impact |
|
||
|
||
## Cascade Calculation
|
||
|
||
When a user selects an infrastructure asset for analysis, a **breadth-first cascade** propagates through the graph:
|
||
|
||
```
|
||
1. Start at source node (e.g., "cable:marea")
|
||
2. For each dependent node:
|
||
impact = edge_strength × disruption_level × (1 - redundancy)
|
||
3. Categorize impact:
|
||
- Critical: impact > 0.8
|
||
- High: impact > 0.5
|
||
- Medium: impact > 0.2
|
||
- Low: impact ≤ 0.2
|
||
4. Recurse to depth 3 (prevent infinite loops)
|
||
```
|
||
|
||
## Redundancy Modeling
|
||
|
||
The system accounts for alternative routes:
|
||
|
||
- Cables with high redundancy show reduced impact
|
||
- Countries with multiple cable landings show lower vulnerability
|
||
- Alternative routes are displayed with capacity percentages
|
||
|
||
## Example Analysis
|
||
|
||
**MAREA Cable Disruption**:
|
||
```
|
||
Source: MAREA (US ↔ Spain, 200 Tbps)
|
||
Countries Affected: 4
|
||
- Spain: Medium (redundancy via other Atlantic cables)
|
||
- Portugal: Low (secondary landing)
|
||
- France: Low (alternative routes via UK)
|
||
- US: Low (high redundancy)
|
||
Alternative Routes: TAT-14 (35%), Hibernia (22%), AEConnect (18%)
|
||
```
|
||
|
||
**FLAG Europe-Asia Disruption**:
|
||
```
|
||
Source: FLAG Europe-Asia (UK ↔ Japan)
|
||
Countries Affected: 7
|
||
- India: Medium (major capacity share)
|
||
- UAE, Saudi Arabia: Medium (limited alternatives)
|
||
- UK, Japan: Low (high redundancy)
|
||
Alternative Routes: SEA-ME-WE 6 (11%), 2Africa (8%), Falcon (8%)
|
||
```
|
||
|
||
## Use Cases
|
||
|
||
- **Pre-positioning**: Understand which countries are most vulnerable to specific infrastructure failures
|
||
- **Risk Assessment**: Evaluate supply chain exposure to chokepoint disruptions
|
||
- **Incident Response**: Quickly identify downstream effects of reported cable cuts or pipeline damage
|
||
|
||
## Undersea Cable Activity Monitoring
|
||
|
||
The dashboard monitors real-time cable operations and advisories from official maritime warning systems, providing early warning of potential connectivity disruptions.
|
||
|
||
### Data Sources
|
||
|
||
| Source | Coverage | Data Type |
|
||
|--------|----------|-----------|
|
||
| **NGA Warnings** | Global | NAVAREA maritime warnings |
|
||
| **Cable Operators** | Route-specific | Maintenance advisories |
|
||
|
||
### How It Works
|
||
|
||
The system parses NGA (National Geospatial-Intelligence Agency) maritime warnings for cable-related activity:
|
||
|
||
1. **Keyword filtering**: Warnings containing "CABLE", "CABLESHIP", "SUBMARINE CABLE", "FIBER OPTIC" are extracted
|
||
2. **Coordinate parsing**: DMS and decimal coordinates are extracted from warning text
|
||
3. **Cable matching**: Coordinates are matched to nearest cable routes within 5° radius
|
||
4. **Severity classification**: Keywords like "FAULT", "BREAK", "DAMAGE" indicate faults; others indicate maintenance
|
||
|
||
### Alert Types
|
||
|
||
| Type | Trigger | Map Display |
|
||
|------|---------|-------------|
|
||
| **Cable Advisory** | Any cable-related NAVAREA warning | Yellow marker at location |
|
||
| **Repair Ship** | Cableship name detected in warning | Ship icon with status |
|
||
|
||
### Repair Ship Tracking
|
||
|
||
When a cableship is mentioned in warnings, the system extracts:
|
||
|
||
- **Vessel name**: CS Reliance, Cable Innovator, etc.
|
||
- **Status**: "En route" or "On station"
|
||
- **Location**: Current working area
|
||
- **Associated cable**: Nearest cable route
|
||
|
||
This enables monitoring of ongoing repair operations before official carrier announcements.
|
||
|
||
### Why This Matters
|
||
|
||
Undersea cables carry 95% of intercontinental data traffic. A cable cut can:
|
||
|
||
- Cause regional internet outages
|
||
- Disrupt financial transactions
|
||
- Impact military communications
|
||
- Create economic cascading effects
|
||
|
||
Early visibility into cable operations, even maintenance windows, provides advance warning for contingency planning.
|