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
Scope boundary
Scenario catalog
Each exercise is deterministic. Submitting the same scenario recreates the same disabled nodes and relationships without storing a server-side profile.
0 of 7 scenarios reviewed. Stored only in this browser.
Orientation
Path diversity and usable alternatives
Visible effect
The preferred path is available and at least one alternate exists.
Lesson
A web is valuable only when alternative paths are compatible, trusted, and authorized—not merely drawn on the screen.
Recovery
Compare the highlighted route with the unused alternatives.
Failure focus
Communications independence
Visible effect
The preferred low-latency route disappears.
Lesson
Communications diversity matters only when the fallback does not share the same failure domain.
Recovery
Recompose through the alternate relay and observe the changed path.
Failure focus
Evidence age and local processing
Visible effect
The wide-area and passive paths no longer feed the option composer.
Lesson
Availability without freshness can be misleading; stale evidence should fail visibly rather than flow as current truth.
Recovery
Use the locally processed path and retain an explicit evidence-age warning.
Failure focus
Permission and command-path continuity
Visible effect
No approved effect path can complete.
Lesson
Connectivity cannot manufacture permission. A technically feasible route remains unusable when the required authority is absent.
Recovery
Restore the authority node; the exercise intentionally does not invent substitute authority.
Failure focus
Timing integrity and provenance
Visible effect
Two sensing paths are removed from the trusted graph.
Lesson
Timing and provenance are hidden dependencies. A connected network can produce an incoherent picture if timestamps cannot be trusted.
Recovery
Continue only with a corroborated path or hold for more evidence.
Failure focus
Shared services and correlated failure
Visible effect
The web contracts to one slower local route.
Lesson
Several visible paths may still depend on the same data or control service. Node count is not the same as independent resilience.
Recovery
Identify the surviving path and the common dependency that caused correlated loss.
Failure focus
Source integrity and trusted recomposition
Visible effect
The network loses breadth but preserves a trusted local path.
Lesson
Integrity attacks can be more dangerous than outages; rejecting an untrusted source is safer than silently using plausible false data.
Recovery
Recompose from independently trusted evidence.
Design questions
Use the same six questions after every run. They keep availability, independence, evidence, authority, reduced function, and reconstruction from collapsing into one vague “resilience” judgment.
A node can remain online while its data, timing, identity, or configuration becomes unusable.
Two paths that share one gateway, clock, identity provider, or software lineage may fail together.
A slower fallback may preserve connectivity but no longer satisfy the mission’s freshness requirement.
Technical recomposition cannot silently invent new command permission.
Graceful degradation may mean continued sensing, warning, or assessment rather than the original action.
Recovery and accountability require the exact path, evidence, policy checks, and human actions.
Answer-ready summary
Yes. A path may be technically reachable yet unusable because data is stale, incompatible, insufficiently trusted, or not authorized.
Read the supporting page