managarten/docs/plans
Till JS 38d35247cd feat(spaces): end-to-end shared-space sync (membership lookup + plaintext)
Closes the gap between "invite flow UI exists" and "two users in the
same space actually see each other's data". Three pieces land together
because they're meaningless without each other.

mana-auth — new internal endpoint:
  GET /api/v1/internal/users/:userId/memberships
  Returns [{organizationId, role}, ...] for the user. mana-sync uses
  this to populate the multi-member RLS session config.

mana-sync — membership lookup:
  new internal/memberships package with an HTTP client + 5 min
  per-user cache, fail-open (empty list = pre-Spaces behavior).
  Config gets MANA_AUTH_URL (default http://localhost:3001).
  Handler.NewHandler takes the Lookup. Every Push/Pull/Stream call
  now passes spaceIDsFor(userID) to Store methods.
  GetChangesSince + GetAllChangesSince extend their WHERE clause:
    WHERE (user_id = $1 OR space_id = ANY($memberSpaces))
  so co-members see each other's rows, not just the author.

apps/web — encryption skip for shared-space records:
  encryptRecord now checks record.spaceId:
    - `_personal:<userId>` sentinel OR no active shared space → encrypt
      with user master key (E2E as today).
    - Active space resolves to non-personal type AND spaceId matches
      that space → skip encryption; write lands plaintext.
  decryptRecord is unchanged because its per-field isEncrypted() guard
  already passes plaintext through.
  Phase-1 compromise: shared-space data is protected by server RLS
  only, not E2E. Phase 2 adds per-Space shared keys with per-member
  wrap — tracked in docs/plans/spaces-foundation.md.

Plus docs/plans/shared-space-smoketest.md: step-by-step Zwei-User-Test
mit erwarteten Ergebnissen und Debugging-Hinweisen bei Problemen.

Build + go test + web check all green.

Plan: docs/plans/spaces-foundation.md

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-20 20:46:53 +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
broadcast-module.md docs(broadcast): plan newsletter / broadcast module 2026-04-20 19:32:53 +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
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
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
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