Privacy
Proof gates
Progress is gated, not promised. Each gate is a concrete, runnable check, and the project does not move past a gate until it passes.
Gates, not milestones
A milestone is a date; a gate is a test. NoviQ organizes its development as a ladder of gates, each one a specific claim you can reproduce. This keeps the roadmap honest: a feature is not "done" because it shipped, it is done because its gate passes.
The ladder
Run them yourself
The gates are not screenshots - they are scripts that finish in seconds on a laptop CPU.
# correctness: bit-identical split vs whole
.venv/bin/python -m proof.correctness_gate
# privacy diagnostic: shows boundary pinning alone is NOT enough
.venv/bin/python -m proof.privacy_probe
# privacy gate: obfuscation drops recovery to near chance, output identical
.venv/bin/python -m proof.obfuscation_gateThe diagnostic is included on purpose
The
privacy_probe is the failing case: it demonstrates that pinning the boundary leaves the embedding in the residual stream and the prompt fully recoverable. Shipping the failure alongside the fix is the honesty rule in code.The sequencing rule
Order is load-bearing
Correctness (A), then real WAN (B), then cache (C), then the privacy proof (D). Speed optimizations and the permissionless economy come after the network can prove the two things the product name promises: the output is right, and the input stayed hidden.
