managarten/docs/plans
Till JS fd1ea47075 feat(backup): client-driven v2 snapshot export, drop server-side backup
Replaces the mana-sync event-stream export (GET /backup/export) with a
fully client-driven `.mana` v2 archive: webapp reads Dexie, decrypts
per-field, packages JSONL + manifest, optionally PBKDF2+AES-GCM seals
with a passphrase.

- New: backup/v2/{format,passphrase,export,import}.ts + format.test.ts
  (10 tests: round-trip, sealed path, 3 failure modes incl. wrong-
  passphrase vs. tamper distinction).
- UI: ExportImportPanel with module multi-select, optional passphrase,
  progress + sealed-file detection — replaces the old backup flow in
  Settings → MyData.
- Removes services/mana-sync/internal/backup/ and the corresponding
  client helpers + v1 tests. No parallel paths, no legacy shim.
- Why client-driven: zero-knowledge users hold their vault key only
  client-side, so a server exporter cannot produce plaintext archives;
  GDPR Art. 20 portability is better served by plaintext-by-default.
- Cross-account restore works via re-encryption under the target
  vault key (no MK transfer needed).

DATA_LAYER_AUDIT.md §8 rewritten to reflect the new architecture.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-22 18:46:29 +02:00
..
ai-mission-key-grant.md feat(ai): Mission Grant rollout gating — flag, alerts, runbook, user docs 2026-04-15 14:02:47 +02:00
articles-homepage.md feat(articles): M9 workbench homepage — 4-tab shell + QuickAdd + StatsView 2026-04-22 17:50:38 +02:00
articles-module.md feat(articles): M8 highlights view + stats + dashboard widget 2026-04-22 14:12:18 +02:00
broadcast-module.md docs(broadcast): plan newsletter / broadcast module 2026-04-20 19:32:53 +02:00
data-export-v2.md feat(backup): client-driven v2 snapshot export, drop server-side backup 2026-04-22 18:46:29 +02:00
event-discovery.md feat(events): add Event Discovery — Phase 1 + 2 2026-04-18 15:30:46 +02:00
invoices-module.md docs(invoices): mark all milestones done, list Phase-2/3 open items 2026-04-20 18:23:02 +02:00
library-module.md feat(library): M3 — progress tracking (pages, episodes, issues) + restart 2026-04-17 13:17:22 +02:00
mail-module-plan.md docs(mail): add TODO checklist for remaining Phase 1-4 work 2026-04-13 20:46:00 +02:00
mana-research-service.md feat(research): Phase 3a — 4 sync research agents 2026-04-17 15:06:12 +02:00
multi-agent-workbench.md docs: flesh out Multi-Agent plan shipping log + Team Workbench forward plan 2026-04-15 22:17:04 +02:00
news-research-module.md docs: flesh out Multi-Agent plan shipping log + Team Workbench forward plan 2026-04-15 22:17:04 +02:00
per-space-vs-user-global-tags.md docs(plans): per-Space vs user-global tags — decision deferred 2026-04-22 15:32:15 +02:00
planner-function-calling.md docs(plans): mark shared-llm tool-call integration as deferred 2026-04-20 18:36:07 +02:00
README.md docs: update tool coverage table + server-side research + templates 2026-04-16 12:35:40 +02:00
scene-scope-empty-state.md docs(workbench): plan for scene-scope empty state 2026-04-18 16:23:13 +02:00
shared-space-smoketest.md feat(spaces): end-to-end shared-space sync (membership lookup + plaintext) 2026-04-20 20:46:53 +02:00
social-relay-module.md feat(spaces): add space types + module allowlist as multi-tenancy foundation 2026-04-20 15:57:57 +02:00
space-scoped-data-model.md docs(plans): log 2d.5/2d.6/2e/2c/2e-followup to the shipping table 2026-04-22 18:35:51 +02:00
spaces-foundation.md feat(spaces): migrate calendar module to scoped-db wrapper (pilot) 2026-04-20 16:42:10 +02:00
team-workbench.md docs: flesh out Multi-Agent plan shipping log + Team Workbench forward plan 2026-04-15 22:17:04 +02:00
tipps-module.md Create tipps-module.md 2026-04-22 14:21:57 +02:00
workbench-cards-migration.md docs(plans): revise workbench-cards plan for cards-for-workflows rule 2026-04-22 15:05:48 +02:00
workbench-templates.md feat(templates): generalise to WorkbenchTemplate + ship Calmness pilot (T1) 2026-04-16 01:07:41 +02:00

Plans

Design + rollout plans, grouped by topic. Plans are long-form docs with baked-in decisions, phasing, open questions, and (when shipped) a history section with commit refs.

AI / Workbench roadmap

The Mana AI Workbench has evolved in three successive planned waves — each one laying foundations the next one relies on:

  User hat einen Companion (v0 — shipped before these docs)
        │
        ▼
  AI Missions + Proposals + Policy + Revert
        │
        ▼
  Mission Key-Grants  ←  ai-mission-key-grant.md  ✅
    (encrypted inputs decryptable by the server runner)
        │
        ▼
  Multi-Agent Workbench  ←  multi-agent-workbench.md  ✅
    (named agents, per-agent policy/memory/budget,
     identity-aware Actor, scene→agent lens)
        │
        ▼
  Team Workbench  ←  team-workbench.md  📝 (not started)
    (multi-user + shared AI context,
     admin lens on team members)
Plan Status Scope
ai-mission-key-grant.md Shipped Per-mission RSA-wrapped key grant so mana-ai can decrypt allowlisted encrypted records when user opts in.
multi-agent-workbench.md Shipped Identity-aware Actor + named AI agents owning missions + per-agent policy + scene lens. 28 tools across 11 modules including server-side web-research.
workbench-templates.md T1 Shipped Generalised templates: 3 agent-templates + 3 non-AI workbench starter-kits. Seed-handler registry for per-module data seeding.
team-workbench.md 📝 Forward-looking TeamSpace with membership, team-encrypted records, admin lens on team members. Reuses Actor.principalId + key-wrapping patterns from the two above.

Cross-references:

Other plans

Plan Topic
mail-module-plan.md Mail module — IMAP/SMTP integration
news-research-module.md News + research pipeline