Track-back, never hack-backWe only ever operate on infrastructure you own. We never reach into, damage, or steal from anyone else's systems.
Deceive, don't just blockAttackers meet convincing decoys. Everything they touch is fake, marked, copied, and traced.
Evidence, not vengeanceWe build a documented, court-ready trail for law enforcement — lawful under 18 U.S.C. §1030.
The whole build · start to finish
The full story
Everything created in this project, gathered in one place — the doctrine, how the pieces connect, the modules, the Ballot Fortress, the audit's best catches, and the roadmap. Nothing left out.
01 · The doctrine
Track-back, never hack-back
Cyber Sentinel never attacks anyone. It only operates on infrastructure you own — luring intruders into decoys, recording everything they do, and handing court-ready evidence to law enforcement. Lawful under the Computer Fraud and Abuse Act (18 U.S.C. §1030). Local-first, with zero egress by default.
02 · How it all connects
One umbrella, one console
Cyber Sentinel is the umbrella platform — the product that lives here at cybersentinel.bornbetween2generals.com. VigilantGuard is one module inside it: the live Command Console you can try above. And Dexter's Lab (StrongRoomSE/dexters-lab) is where the code gets written — edit there, push, and Vercel deploys the change automatically.
03 · The Command Console
VigilantGuard, Sovereign-class
Built to match and beat the 97/100 Sovereign control-tower. Three tiers — Protégé → Operator → Expert — and three live tools: threat triage that scores your exposure out of 100, a deception grid across eight domains, and a five-ring sphere-of-protection readiness view. It runs a transparent local engine by default, and an AI model only if you supply a key.
04 · The Ballot Fortress
Your ballot question, answered
The election-integrity idea you raised wasn't a new invention — it's the beating heart of what Cyber Sentinel already is. It maps onto existing modules: the air-gap layer, the sovereign identity fabric, the honeypot deception grid, and the forensics lab. The one genuinely new piece — a concurrent “shadow fraud-run” that fools an attacker while the real count stays sealed — became the interactive breach demo above and its own architecture spec.
05 · The audit's best catches
Four great catches from the cluster audit
When your Sovereign AI Cluster was audited, four additions stood out — exactly the kind of hardening that turns a strong build into a shippable one:
- Typed, rotating tokens everywhere. A person's token, a business token, and a government token are structurally different. The moment a forged or stolen token appears, its whole type rotates across your systems — so the stolen one is already useless.
- Fill the missing
.env.example files. Several repos needed secrets that weren't documented, so a fresh deploy silently half-worked. Documenting them was the single biggest shared gap.
- Add a
vercel.json build command to the static sites. So Vercel builds them automatically instead of relying on a local script being run by hand.
- Write READMEs for the two silent repos.
lockchain — 403 files with no front-door explanation — and conductor. Mature code deserves a door people can walk through.
06 · The roadmap
Four things, in order
- Start coding today — the Dexter's Lab guide (done).
- VigilantGuard Sovereign-class console — the live console above (done).
- America's Future → Born Between 2 Generals email + logo sweep across every repo.
- Passphrase-gate runbook — make every project private-but-shareable.
07 · Where it lives
Deployed and yours
This platform is live at cybersentinel.bornbetween2generals.com, deployed on your Kristen's Lab team on Vercel, branded in your black-and-teal. The full architecture spec and this whole story are packaged as downloadable documents so you always have the complete picture.