vjrj
ec5dca1e1c
Make Tane primary in README, VISION, CLAUDE, the intros and the plain-language explainer (renamed que-es-tanemaki.md → que-es-tane.md, dropping its "provisional name" caveats); keep Tanemaki (種まき) only as the etymology. PLAN.md is the origin record: its naming section §5-ter is preserved verbatim as history under a dated "superseded" note, and the Nota de vigencia now records Tane + the tane.comunes.org domain.
33 lines
2.5 KiB
Markdown
33 lines
2.5 KiB
Markdown
# Tane 種
|
|
|
|
*A local-first, decentralized app for managing and sharing traditional seeds and seedlings.*
|
|
|
|
**Tane** (種, "seed" in Japanese) helps people and collectives keep a friendly inventory of their seed bank, decide what they offer, and share it locally — without a central intermediary that could control, censor, or be fined for it. Its name comes from **tanemaki** (種まき), "to sow / scatter seeds". The goal is both practical and political: to support traditional seed varieties and push back against the seed monopoly.
|
|
|
|
The name honors the old Japanese mutual-aid traditions around rice — *yui* (shared community labor) and *tanomoshi* (reciprocity funds) — that inspired the paper **Plantare**, the "community currency for seed exchange" (BAH-Semillero, 2009, CC-BY-SA). Tane is the digital Plantare.
|
|
|
|
- Web: https://tane.comunes.org
|
|
- Package id: `org.comunes.tane`
|
|
|
|
## Status
|
|
|
|
Early design. See [`PLAN.md`](PLAN.md) for the full analysis and roadmap (in Spanish). The valuable prior work lives in [`docs/mockups/`](docs/mockups/).
|
|
|
|
## Principles
|
|
|
|
- **Local-first.** Works fully offline, no account, no central server. Stays useful even if no one maintains it.
|
|
- **Decentralized.** Identity is a single key you own (Duniter/Ğ1-style, with a derived subkey for transport); sharing rides on open protocols (Nostr), with optional interoperability with the Ğ1/Duniter web of trust and currency. Never a central marketplace.
|
|
- **Free/libre.** Copyleft software, open data formats, multilingual from day one.
|
|
- **Layered.** Inventory -> Offer -> Local sharing -> Web of trust. Each layer is useful on its own.
|
|
|
|
## Conventions
|
|
|
|
**English is the project language for all code.** Identifiers, class/field/column names, code comments, commit messages, branch names, and technical documents (data model, schemas) are written in English, without exception. This keeps the project contributable by anyone, anywhere.
|
|
|
|
- User-facing strings are **never hardcoded** — they go through i18n (the app itself is multilingual by design).
|
|
- Planning and discussion documents may be written in Spanish (e.g. `PLAN.md`, `docs/design/data-notes.md`); technical specs that feed code are in English (e.g. `docs/design/data-model.md`).
|
|
- Database schema changes ship as versioned Drift migrations (`drift_schemas/`), one new version per change, never editing a released version. See `docs/design/data-model.md` §5.
|
|
|
|
## License
|
|
|
|
Software: **AGPL-3.0** (GPLv3 strengthened with the network clause; compatible with GPLv3 and with Duniter/Ğ1nkgo, which we reuse). Docs & assets under CC-BY-SA where noted.
|