Deterministic teaching exercises
Remove a relay, reject stale evidence, lose an authority path, or expose a common dependency. Each exercise changes only fictional graph state and teaches why recovery must remain compatible, trusted, and authorized.
Research basis KW-RPT-002 KW-RPT-004 KW-RPT-011
They do not estimate lethality, weapon effectiveness, real system performance, real response time, casualties, or operational feasibility. The only outputs are educational path state, evidence quality, authority status, and recovery logic.
Scenario catalog
Each scenario is deterministic. Opening the same scenario recreates the same disabled nodes and relationships without storing a server-side profile.
The preferred path is available and at least one alternate exists.
The preferred low-latency route disappears.
The wide-area and passive paths no longer feed the option composer.
No approved effect path can complete.
Two sensing paths are removed from the trusted graph.
The web contracts to one slower local route.
The network loses breadth but preserves a trusted local path.
Design questions
| Question | Why it matters |
|---|---|
| What failed or became untrustworthy? | A node can remain online while its data, timing, identity, or configuration becomes unusable. |
| Which alternatives are genuinely independent? | Two paths that share one gateway, clock, identity provider, or software lineage may fail together. |
| Did the evidence age or confidence change? | A slower fallback may preserve connectivity but no longer satisfy the mission’s freshness requirement. |
| Did authority move? | Technical recomposition cannot silently invent new command permission. |
| What safe reduced function remains? | Graceful degradation may mean continued sensing, warning, or assessment rather than the original action. |
| Can the decision be reconstructed? | Recovery and accountability require the exact path, evidence, policy checks, and human actions. |
Answer-ready summary
They compare path availability, evidence age, authority, compatibility, and recovery—not lethality or real-world system performance.
Read the supporting pageYes. A path may be technically reachable yet unusable because data is stale, incompatible, insufficiently trusted, or not authorized.
Read the supporting page