Data minimization
Only necessary data should be handled; no unnecessary collection or tracking.
The goal is not to expose internal technical details publicly, but to follow principles that reduce failure risk and long-term operational burden.
For security-oriented software planning or system design, send a message.
Only necessary data should be handled; no unnecessary collection or tracking.
Permissions, roles and sensitive actions need clear boundaries.
The default state should be cautious: fewer permissions and fewer risky paths.
Important changes need visible state, fallback paths and repairable operation.
Users should understand what happens with their data and why.
Errors, states and support paths should be traceable rather than hidden.