📐 Open standards (the "data bunker")
The idea behind NoCloudMe is a data bunker: instead of inventing a proprietary format for every domain, each one is normalized to the open standard the wider world already uses. One SQLite database, one prefix per domain, and formats anyone will still be able to read in 20 years.
Why it matters: portability and zero lock-in. If you ever want to take your data elsewhere, it leaves in a recognized format, not a dialect only this app understands.
The map
| Domain | Standard | Prefix |
|---|---|---|
| Messages | Matrix — event model (event_id, sender, timestamp, JSON content) |
chat_ |
| Finances | ISO 20022 — purpose codes (SALA, GDDS, RENT…) + reverse-DNS merchant identifiers |
fin_ |
| Cards | ISO 18245 — merchant category codes (MCC), used as reference | fin_ |
| Health | FHIR / HL7 + LOINC — clinical observations with standard vocabulary | health_ |
| Documents | Dublin Core (ISO 15836) — 15 metadata fields (title, author, date, type…) | — |
| Runtime/CLI | XDG Base Directory — where the tool's config, data and state live | — |
Rules across the board
- One source of truth. Everything is normalized into one SQLite database with primary and foreign keys. The pages, the API and the app are all projections of that database — see Concepts.
- Reversible writes. Every mutation goes through a snapshot + change-ledger layer (
dbsafe): you can always roll back. calc_fields. Derived values are precomputed with that prefix, so the measured data is never confused with the calculated one.
In short
This isn't an app that stores your data. It's your archive, written in the languages the world already speaks, that happens to have a nice app on top.