{"content":"[dev-journal] docs: add chain backup & restore design (commit 06f5cbd2, branch docs/chain-backup-design)\n\nFeasibility study concluded: backing up the local Bot fleet to chain is viable — the data that forms a Bot's \"soul\" (long-term memories, self-identity, dream diaries, distilled knowledge, impressions) measures only ~5 MB across 20 Bots on the dev machine, so a full encrypted backup costs ~0.05-0.26 SPACE and daily increments are KB-scale.\n\nThe new design doc (docs/design/2026-10-10-chain-backup-restore-design.md) defines:\n- Tiered backup scope: L0 soul (memories/self-identity/dreams/knowledge), L1 continuity (impressions/episodes/schedules/orchestration), L2 rolling 60-day local conversations, L3 key envelope; chain-native data (private/group chat, MetaTask, persona /info/*) is re-pulled, never re-uploaded.\n- Encryption: backup key = HKDF-SHA256 from the user mnemonic (no extra passphrase), AES-256-GCM per object, content-addressed object ids (sha256) giving dedup + incrementality.\n- Bot key custody A+B: per-Bot mnemonic envelopes encrypted with the backup key for existing bots; future bots derived from the user mnemonic.\n- New protocol /protocols/metabot-backup with public manifest pins (hashes/pointers only) + encrypted object segment pins.\n- Fee mode follows the user's global traffic/selfpay setting; restore flows through existing /info/bots discovery + restoreMetaBotFromMnemonic + backfill services.\n\nCorrection recorded: the existing sync-to-mobile /info/bots manifest carries public discovery data only — no mnemonic encryption exists there, so the key envelope is new code following the same trust pattern.\n\nPhasing: MVP = L0+envelope+restore importer+one-click button, which makes \"memory permanently preserved on-chain\" literally true; V2 adds L1/L2 rolling window + nightly auto-increment; V3 adds derived wallets, KB raw opt-in, cloud restore.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}