The inversion that helps users
Standard privacy documents list what data may be collected to maximize wiggle room. A product-grade alternative: enumerate what is structurally not collectable. Capability statements aren't caveats — they're specs a binary either satisfies or doesn't.
Sample clauses that must survive contact with reality
- “No network SDK is linked.” Verifiable: import-table inspection, runtime traffic silence.
- “The export path is allowlist-only.” Verifiable: the exporter physically can't accept arbitrary paths; the allowlist exporter post walks the mechanics.
- “Undo restores byte-exact prior state.” Verifiable: your journal stores the old blob and you can verify restoration manually.
When the policy is the engineering spec, legal review cycles turn into conformance tests — and trustworthy patterns compound: each new feature either fits the contract or gets declined. In a tuning-tool landscape where “our data practices may evolve” is the ceiling, a document your build pipeline can fail against is the marketing surface that age-checks best.
ProofTune ProjectEngineering notes — every claim here names the bytes a real tool touches. Verify first, install second.