Current project notes · 13 October 2026
Understand the mechanism.
Keep the evidence in view.
These notes describe documented designs and their limits. A working webpage does not establish a validated operational service.
Download readable project notes
Sovereign Clean Sky
Airspace identity, operator authority and mission permission answer different questions. The October prototype uses browser-generated P-256 signatures, independent trust pins, freshness and revocation checks, and signed audit evidence to keep those findings separate.
The verification lab uses synthetic enrollment and simulated sensors. It retains contacts for behavior review and confers no enforcement authority. Hardware protection, real registries, durable replay state and institutional deployment remain development work.
Its local console makes no third-party requests; session evidence lives in browser memory until downloaded. Offline review needs separately retained trust anchors. P-256 does not provide post-quantum protection.
Sovereign Studio
A private knowledge workflow needs to know what its sources are, which rules govern a question and where the sources disagree. The documented catalog, ranking, routing, contradiction and border tools address those needs.
Browser intake hashes and classifies files locally. The model console needs a separately running loopback model. Private source files are not supplied by this showcase, and live local GPU inference was not verified during this session.
Preserve each program’s role.
Operation Angels is the BB2G showcase. Angel’s Post and The Shield Project remain distinct programs. Pro ID does not determine voter eligibility. Paper-authoritative custody work remains non-tabulating. Safe Perimeter’s original wearer-feedback concept and v0.3 retain separate designs and evidence.
Original concepts and historical materials remain preserved. Later clarifications are described as refinements; no patent, clinical validation or production-readiness claim is inferred.