comunes/tane
1
0
Fork 0
Code Issues Pull requests Projects Releases 7 Packages Wiki Activity Actions

docs: rename Tanemaki → Tane in design docs and notes

Browse source 
Product-name mentions → Tane; backup-file extension .tanemaki → .tane;
website tanemaki.app → tane.comunes.org. Etymology-bearing docs
(README, VISION, PLAN, CLAUDE, intros) handled separately.
This commit is contained in:
vjrj 2026-07-12 13:09:12 +02:00
parent a534c14983
commit 1e2c66a982
16 changed files with 51 additions and 51 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/design/data-model.md
View file

@ -1,4 +1,4 @@
# Tanemaki — Data model (v0 draft)
# Tane — Data model (v0 draft)
*Technical spec feeding the Flutter/Drift implementation. Written in English (project convention). Implements the concepts discussed in [data-notes.md](data-notes.md) and PLAN §3 / §5-bis.*
@ -172,7 +172,7 @@ The *shop window*: a signed statement published to the network so others can dis
| `author_key` | TEXT | Publishing public key. |
| *(+ common columns)* | | |
A closed deal may produce a `Movement` (`given`) and, if it is an exchange with a return promise, a `Plantare`. The app never processes payments, takes commissions, or holds funds (keeps Tanemaki neutral infrastructure, not a central market operator).
A closed deal may produce a `Movement` (`given`) and, if it is an exchange with a return promise, a `Plantare`. The app never processes payments, takes commissions, or holds funds (keeps Tane neutral infrastructure, not a central market operator).
## 3. Entity map
@ -229,7 +229,7 @@ Together: Drift handles the *local database* migration; the compatibility rules
## 7. Interchange export/import (Phase 1) — decided & implemented
The user-triggered **interchange export** (Settings → Backup). Distinct from the future encrypted full backup (`.tanemaki`, [backup-and-recovery.md](backup-and-recovery.md) mechanism 1): the interchange files are the *only* plaintext the app ever writes, and only because the user explicitly asks for them. Import reads the picked file straight into memory — no temp copies.
The user-triggered **interchange export** (Settings → Backup). Distinct from the future encrypted full backup (`.tane`, [backup-and-recovery.md](backup-and-recovery.md) mechanism 1): the interchange files are the *only* plaintext the app ever writes, and only because the user explicitly asks for them. Import reads the picked file straight into memory — no temp copies.
Two formats, one canonical: