Website Translation And Privacy Requirements
Why This MattersRead the earlier reference in its original context, with its historical statements and limits preserved.
Read the v0.2 requirements for a future educational website, including transparent calculations, visitor privacy, and explicit limits on security and effectiveness claims.
The future site should explain the philosophy and show calculations whose inputs, assumptions and limits remain visible. This page is a requirements specification; no site, account system or security certification is delivered in v0.2.
| Module | Required behavior |
|---|---|
| Learn | Definitions, 24 rules, exceptions, source links and version history. |
| Measure | Separate balance sheet, cash margin, runway, coverage and concentration views; no character or freedom grade. |
| Compare | A maintain/decline option, opening costs, time horizon and the same disclosed shocks across alternatives. |
| Understand | Cash paths with both zero and reserve floor; dates of first breach; explanations of undefined results. |
| Record | Facts, estimates, unknowns, qualitative constraints, reasons and review date. |
| Evidence | Source access status and a clear distinction between examples, research components and untested package claims. |
Privacy And Integrity Baseline
An initial calculator can run locally in the browser without account linking or server retention. Make any saving or export explicit. Avoid placing entered financial values in analytics, page URLs or logs. Do not load hidden third-party collection code into the calculator.
Validate inputs with an explicit schema; reject missing values rather than converting them to zero. Match the disclosed rounding and timing rules, provide keyboard and screen-reader access, and test small-screen displays. Keep the educational content usable without entering personal data.
If accounts or cloud saving are later added, define access controls, deletion, encryption, retention and an incident response process before collecting information. Deployment-specific security review remains necessary. A static prototype or passing unit tests cannot establish secure production operation.