Frequently Asked Questions

Volumes 0, 1, and 2 are fully compatible with macOS, Windows, and Linux. However, Volume 3 (Kernel space) requires a native Linux kernel (v5.8+).

This is because Windows and macOS do not expose Linux namespacing primitives or the eBPF sub-system. Windows users can complete Volume 3 using WSL2, provided the underlying kernel is updated to v5.15 or newer. Native Linux installations are highly recommended for the final modules.

Volume 3 compiles code for two completely separate environments:

1. sentinel-core: A user-space daemon executing on your normal machine processor.
2. sentinel-ebpf: Kernel-space safety hooks running directly inside the operating system's bytecode machine.

Because the kernel program targets a custom runtime architecture (bpfel-unknown-none), it requires unique compiler flags and optimization pipelines. A Cargo Workspace groups them neatly while allowing them to build into separate target frameworks.

If the compiler throws errors stating modules like models or engine cannot be found, verify your folder layout. Volume 2 scales the code out from a single main.rs file into a multi-module setup. Ensure that your volume-2-systems/src/ directory contains exactly three files: ├── src/
│ ├── main.rs
│ ├── models.rs
│ └── engine.rs

Injecting instrumentation routines into the Linux Kernel requires specialized capabilities. Specifically, you need administrative clearance to call bpf() system routines. Always initialize the built binary in your workspace using sudo or root privileges: sudo ./target/debug/sentinel-core

No! Once you paste your license token into verify.html and successfully log in, our Cloudflare edge architecture stores a secure session handshake inside an HTTP cookie. This cookie persists automatically for 30 days, giving you instant entry into all premium volumes without prompting you again.

Project Sentinel uses a secure, local browser token to keep you logged in without requiring a username and password. Because of this, your unlocked status is tied directly to the specific browser you used to verify your key.

If you switch from Chrome to Safari, use a different computer, or browse in Incognito/Private mode (which deletes tokens when closed), the system will not recognize you and will ask for your License Key again. To stay logged in continuously, use a standard, non-private browser window.

Your license key is generated instantly upon checkout. You can locate it in two places:

• Directly on the interactive receipt page shown in your browser immediately after buying.
• Inside your inbox as a dedicated field within the automated receipt email dispatched by [email protected].