"You do not need to trust us. Run the code. Verify the truth."
This guide enables any citizen—regardless of technical background—to independently verify the integrity of The Plainview Protocol. No special skills required.
The Plainview Protocol makes claims about transparency, security, and accountability. Words are cheap. This document hands you the tools to verify those claims yourself.
We use the same data the Labyrinth uses, but we use it for the people. Fork the code. Spread the light.
You need one thing: Docker Desktop
Docker is a free tool that runs code in an isolated environment. It ensures you're running the exact same tests we run—no modifications possible.
| Operating System | Installation Link |
|---|---|
| Windows | Download Docker Desktop for Windows |
| Mac | Download Docker Desktop for Mac |
| Linux | Docker Engine Install Guide |
After installation:
- Open Docker Desktop
- Wait for the whale icon to appear in your system tray
- Verify by opening Terminal/Command Prompt and typing:
docker --version
- Click the green "Code" button on GitHub
- Select "Download ZIP"
- Extract to a folder you'll remember
git clone https://github.com/YOUR_USERNAME/plainview-protocol.git
cd plainview-protocolOpen Terminal (Mac/Linux) or Command Prompt (Windows) and navigate to the project folder:
cd path/to/plainview-protocolThen run the audit capsule:
docker compose up --buildWhat happens next:
- Docker downloads the official Playwright testing environment
- The audit suite runs automatically (16 tests across 3 categories)
- Results display in real-time in your terminal
✓ Protocol loads successfully
✓ No sensitive data exposed
✓ All security headers present
Meaning: The system is operating as intended. Integrity verified.
✗ Security header missing
✗ Unexpected data exposure detected
Meaning: Something requires attention. Report it immediately.
| Symbol | Meaning |
|---|---|
| ✓ | Audit passed - integrity verified |
| ✗ | Audit failed - investigate immediately |
| ○ | Audit skipped - not applicable to this run |
At the end of the audit, you'll see:
16 passed (45.2s)
This means 16 out of 16 audits passed. 100% is the standard. Anything less requires investigation.
| Category | What It Checks |
|---|---|
| Homepage Audits | Protocol loads, navigation works, live data displays |
| Security Audits | HTTPS enforcement, data exposure prevention, header security |
| Contact Audits | Form validation, email protection, submission handling |
After running the audit, check these files:
| File | Contents |
|---|---|
tests/test-results/results.json |
Raw audit data (machine-readable) |
dashboard/index.html |
Visual status board (open in browser) |
dashboard/history.json |
30-day trend data |
If you discover a failing audit:
- Do not panic - Document what you see
- Screenshot the terminal output
- Open an issue on GitHub using the "Audit Failure Report" template
- Include your environment: OS, Docker version, timestamp
Yes. Docker creates an isolated environment, but the code runs locally. No data leaves your machine.
Yes. Fork the repo and add your own accountability tests. See CONTRIBUTING.md for guidelines.
Run it whenever you want verification. We run it automatically on every code change.
- Ensure Docker Desktop is running (whale icon visible)
- Try:
docker system prune -athen retry - Open an issue—we'll help
By running this audit, you join the Sentinel Network. You are not just a user—you are a guardian of transparency.
"The barrier to entry for truth must be zero."
# Full audit
docker compose up --build
# View results
open dashboard/index.html
# Clean up
docker compose downThe Plainview Protocol - Established January 8, 2026
"Truth, Kindness, & Security"