---
title: "The Sovereign Verification Protocol"
description: "Forensic analysis and open knowledge documentation for just3ws/dehum"
license: "CC-BY-SA-4.0"
open_knowledge_foundation: "Open Definition 2.1 Conforming"
maintainer: "Mike Hall"
project: "just3ws/dehum"
date: "2026-10-12"
---
The Sovereign Verification Protocol
*"Code generation is free. Verification is everything."*
The Economic Ledger: Synthetic Inflation vs. Sovereign Ground Truth
Rather than hypothetical estimates, the exact physical SQLite conversation logs across the investigation record 3,695 steps and 501,096,098 tokens (0.501 Billion tokens) processed (16.8M uncached input, 483.2M context cache read, 1.0M generated output).
At developer API list rates, this represents ~$10.63 in raw compute value. In cash accounting, the maintainer operated on a Google Gemini Pro subscription under a $5/month promotional rate ($0.00–$1.25 amortized out-of-pocket project spend), bridging to a free account only once when weekly Pro quota was consumed.
Meanwhile, specialized human engineering forensic labor was valued at $10,010 across five disciplines:
- Acoustic & DSP Engineering: $3,000
- POSIX Systems & CLI Architecture: $2,000
- Static Site & Infrastructure Architecture: $2,000
- Forensic Editorial & Epistemological Direction: $2,000
- Physical Verification & Ground-Truth Auditing: $1,010
The resulting leverage ratio ranges from ~1,000:1 (developer API list value) to over 2,000:1–8,000:1 (amortized out-of-pocket spend). The popular 250:1 metric serves as a conservative floor under commercial unbundled compute.
---
The 4 Steps of Sovereign Verification
To prevent AI code generation from collapsing into automated slop, every change must pass through the Sovereign Verification Protocol:
1. Physical Grounding First:
- Probe container durations, but compare against real-world video frames.
- Never accept an algorithm that sounds wrong to human ears, no matter how elegant the math looks.
2. Zero Loss Muxing:
- Never re-encode uncorrupted streams. If only audio is broken, copy video bit-for-bit (
-c:v copy).
3. Automated Boundary Guards:
- Run strict TMI/PII scanners (
bin/audit_tmi.rb) on every commit and push to prevent credential leaks, machine-name disclosures, or personal phone/email leaks.
4. Emptying the Cup (*Shoshin*):
- When the script exits with code 0, you are not done. You are only done when the master recording has been watched, listened to on headphones, and subjected to public scrutiny.