> ## 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.

# Architecture overview

> How the four enforcement layers compose, and why they are not independent.

## 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.

<Steps>
  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Wallet depends on all three">
    A private wallet is the conjunction of its transport (routing), its identity
    (session-scoped), and its execution surface (sandboxed). Removing any one
    weakens the wallet's privacy claim.
  </Step>
</Steps>

<Note>
  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.
</Note>

## Specification pages

<CardGroup cols={2}>
  <Card title="Session model" icon="arrows-rotate" href="/architecture/session-model">
    The session as a formal concept: states, transitions, what's in scope, and
    what's wiped at end.
  </Card>

  <Card title="Session identity isolation" icon="user-secret" href="/architecture/session-isolation">
    The full identity surface hardware, kernel, network, userspace and what is
    scoped per session.
  </Card>

  <Card title="Sandboxed execution" icon="cube" href="/architecture/secure-execution">
    The execution boundary, IPC channels, per-app storage roots, and what
    crosses the boundary explicitly.
  </Card>

  <Card title="Threat model" icon="bullseye" href="/architecture/threat-model">
    Adversaries the layers are designed to defeat, and adversaries they are not.
  </Card>
</CardGroup>