Documentation Index
Fetch the complete documentation index at: https://docs.blackops.army/llms.txt
Use this file to discover all available pages before exploring further.
How the layers compose
The four enforcement layers are not independent features bolted onto a shared OS. Each layer’s guarantee depends on a property of the layer below it.Routing is the foundation
Without mediated egress, the network surfaces a stable client identity IP
address, link characteristics regardless of what userspace does. Everything
above depends on Route doing its job first.
Identity isolation depends on routing
Session-scoped MAC, hostname, timezone, and fingerprint signals are only
meaningful because the network-layer identity rotates with them. Isolation
without routing is just incognito mode.
Sandboxed execution depends on session isolation
A sandbox protects an app from other apps within a session. The
cross-session value of that protection is the session wipe otherwise state
leakage across session boundaries undermines the sandbox.
These layers are not modular in the “swap one out” sense. They are layered in
the “the lower one is the foundation the upper one’s claim rests on” sense.
Specification pages
Session model
The session as a formal concept: states, transitions, what’s in scope, and
what’s wiped at end.
Session identity isolation
The full identity surface hardware, kernel, network, userspace and what is
scoped per session.
Sandboxed execution
The execution boundary, IPC channels, per-app storage roots, and what
crosses the boundary explicitly.
Threat model
Adversaries the layers are designed to defeat, and adversaries they are not.