Why we refuse features
Most software products compete by adding features.
NonnoTech competes by refusing them.
We refuse any feature that compromises truth, evidence, or accountability — even if it is requested by clients.
Section 1
What we refuse
- "Delete" buttons for historical records
- Silent edits and overwrites
- Configurable audit rules
- Optional evidence
- Approvals without named authority
- "Trust us" modes
If a feature weakens proof, it is rejected.
Section 2
Why this is intentional
Features create flexibility.
Flexibility creates ambiguity.
Ambiguity destroys truth.
NonnoTech systems are intentionally constrained.
Constraints are what make evidence possible.
Section 3
How we handle corrections
We do not delete.
We do not rewrite.
We correct through:
- Reversals
- Counter-documents
- New events
- Explicit authority
The past remains intact.
Section 4
Who this is not for
NonnoTech is not designed for organizations that:
- Want convenience over correctness
- Need to "clean up" history
- Treat audits as paperwork
- Rely on personal trust instead of systems
We are explicit about this by design.
Final statement
The product is the constraint
If a feature makes the system more comfortable, but less provable — we refuse it.
This is not a limitation. It is the product.
Issued by
NonnoTech
Systems of Truth