> ## 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. # Introduction > An operating system that enforces network privacy, identity isolation, and execution sandboxing as properties of the system, not as apps you install. ## What is BlackOps OS? BlackOps OS is an operating system where privacy is enforced below the application layer. Every process on the system routes through the privacy stack, every session wipes its own identity, and every app is sandboxed from every other. None of this is opt-in. You cannot turn it off from userspace because userspace does not have that switch. ## The Problem Every privacy tool that ships above the OS covers one surface and leaks around the others. A VPN routes only what binds to its tunnel. A misconfigured app reading from the default route bypasses it silently — and the kernel has no opinion about that. Private browsing resets cookies and storage. It does not change your MAC address, hostname, NTP offset, font set, or clock skew. Fingerprinting moves below the browser. Encrypted messengers protect message bodies. They don't hide your IP, timing, contact graph, or device identifier. Anyone correlating those still wins. Each tool does its own job. They cannot enforce each other — and the OS underneath is not enforcing anything at all. That is the gap BlackOps OS closes. ## The Four Enforcement Properties These are not features. They are properties of the system. Every process running on BlackOps OS operates inside all four, simultaneously, with no off switch surfaced to userspace. All outbound traffic transits the routing layer. No escape via raw sockets, alternate interfaces, or the default route. If the routing layer is unhealthy, traffic fails closed — never falls back to clear. Cookies, fingerprints, MAC, hostname, timezone, locale, and every other client-distinguishable surface are scoped to the active session. Session end wipes them all. Apps run in confined environments with explicit IPC boundaries and per-app storage roots. State written by one app is not readable by another. State written in one session does not carry into the next. The wallet operates inside the same session lifecycle as everything else. Sending or receiving does not produce identifiers that outlive the session. Removing or disabling these properties is not a setting. The enforcement lives in the OS itself. ## What BlackOps OS Does Not Claim BlackOps OS is precise about its boundaries. * **It does not make compromised endpoints private.** If a service logs your traffic, the routing layer cannot control what happens at the other end. * **It does not defeat a global passive adversary.** The threat model is ISP, app vendor, ad network, and casual correlator — not a nation-state with full link visibility. * **It does not anonymize voluntary disclosures.** Logging into an account links the session to that account for its duration. * **It does not prevent behavioral side channels.** Reusing the same writing style or visiting the same niche sites across sessions can be correlated by an observer with no access to the OS at all. ## Explore the Docs How the four enforcement layers compose — and why removing one weakens the others. What a session owns, its lifecycle states, and what survives the wipe. The full client-distinguishable surface — hardware, kernel, network, and userspace — and how each is scoped. How apps are confined, how they communicate when they need to, and what the sandbox does not defend against.