Path diversity
Resilience comes from independent, mission-capable alternatives—not from drawing more lines between components that share the same dependency.
A network is forming
Compose the path.
Test the failure.
Preserve authorized options.
KillWebs.com turns the shift from a fixed kill chain to a resilient, governed network into an interactive synthetic learning environment. Inspect the nodes, remove a dependency, and watch the option space contract or recompose.
- 13
- abstract nodes
- 17
- possible relationships
- 7
- deterministic scenarios
- 0
- external runtime services
Current scenario
Primary relay denied
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.
- Boundary
- Fictional nodes, illustrative state, no operational data.
Kill Web Explorer
One graph. Several possible chains.
Rotate the scene, select a node, degrade it, then ask the system to find another path that still passes compatibility, trust, and authority gates.
Canvas view unavailable
The complete node register and selected pathway remain available beside and below the visualization.
Accessible graph register
Every node outside the canvas
The visualization is optional. Keyboard users and non-Canvas clients can inspect the same state through these semantic controls.
What the web changes
From protecting one route to preserving the outcome.
Later binding
Pair sensors, data services, authorities, and effect nodes when current availability, evidence, timing, and policy are known.
Explicit authority
A technically possible edge is not an authorized path. The model keeps compatibility, trust, and command decisions separate.
Graceful degradation
When the preferred route fails, continue a safe reduced function, expose the loss, and recompose only through validated alternatives.
Capability marketplace
How ACK turns options into comparable offers.
Explore a synthetic version of DARPA’s marketplace model: consumers request an outcome, providers advertise bounded capabilities, and a Virtual Liaison-style layer exposes constraints without assuming authorization.
Enter the ACK LabHuman authority
Where judgment actually lives.
Trace the roles of evidence review, policy, mission configuration, recommendation, authorization, supervision, abort, and accountability across the lifecycle.
Open the Authority LabVulnerability surface
When a connected network is not a trustworthy network.
Examine integrity, timing, identity, data poisoning, supply-chain, electromagnetic, and common-mode risks at a defensive architecture level.
Study resilienceSister-site bridge
The chain remains. The web changes how it is assembled.
Use KillChains.com to study a selected sequence and its interruption points. Use KillWebs.com to study the option space around that sequence—especially when nodes, links, data, or authority change.
Answer-ready summary
Direct answers
What is a kill web?
A kill web is a governed network of sensing, data, communications, command, support, and effect capabilities from which one or more authorized mission chains can be composed.
Read the supporting pageDoes a kill web replace the kill chain?
No. The web is the changing option space; a chain is the selected path used to sense, decide, authorize, act, and assess for a particular mission.
Read the supporting pageIs this an operational planning tool?
No. Every scenario, node, score, latency band, and outcome is fictional and designed only to teach architecture, evidence, resilience, and authority.
Read the supporting pageResearch corpus
Fourteen preserved reports. One traceable memory system.
Every uploaded report is stored under /docs/long-term-memory/reports, assigned a stable ID and SHA-256 digest, and routed through the project’s .uai memory without copying full report bodies into startup state.