# Blackops OS

> Privacy enforced at OS level system level

## Docs

- [Architecture overview](https://docs.blackops.army/architecture/overview.md): How the four enforcement layers compose, and why they are not independent.
- [Sandboxed execution](https://docs.blackops.army/architecture/secure-execution.md): How BlackOps OS confines applications to their own execution context, what crosses the sandbox boundary explicitly, and what does not cross it at all.
- [Session identity isolation](https://docs.blackops.army/architecture/session-isolation.md): The full client-distinguishable surface and how each surface is scoped to a session in BlackOps OS.
- [Session model](https://docs.blackops.army/architecture/session-model.md): Specification of what a session is in BlackOps OS: states, transitions, what each session owns, and what crosses session boundaries by design.
- [FAQ](https://docs.blackops.army/faq.md): Common questions about BlackOps OS: how it works, how it compares to existing tools, how to get access, and what happens to data.
- [Privacy enforcement](https://docs.blackops.army/get-started/privacy-enforcement.md): What happens at session start, during a session, and at session end  the runtime view of how the four layers operate together.
- [Introduction](https://docs.blackops.army/index.md): An operating system that enforces network privacy, identity isolation, and execution sandboxing as properties of the system, not as apps you install.
- [BlackOps Browser](https://docs.blackops.army/modules/browser.md): The browser shipped with BlackOps OS. Its privacy properties come from the OS layers it runs on top of, plus the browser-only surfaces it has to handle itself.
- [BlackOps Messenger](https://docs.blackops.army/modules/messenger.md): End-to-end encrypted messaging that runs inside the same session model as the rest of BlackOps OS. No provider server, no metadata routed outside the encrypted transport.
- [Ops AI](https://docs.blackops.army/modules/ops-ai.md): An agent that runs inside the session model. Inference, tool use, and any action it takes are constrained by the same privacy and execution boundaries as the rest of BlackOps OS.
- [BlackOps Route](https://docs.blackops.army/modules/route.md): The OS-level routing layer. All outbound traffic transits it; no userspace process can reach the network around it.
- [Tokenomics](https://docs.blackops.army/tokenomics.md): Supply, distribution, vesting, and utility for BLOPS, the unit of account in the BlackOps OS economy.

## Optional

- [Twitter](https://x.com/blckops)
- [Telegram](https://t.me/blckops)