till/managarten
1
0
Fork 0
mirror of https://github.com/Memo-2023/mana-monorepo.git synced 2026-05-14 19:41:09 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 4
managarten/docs/plans
History
Till JS 4fc9d6c59c feat(wardrobe): module foundation — garments + outfits space-scoped data layer (M1) 
M1 of docs/plans/wardrobe-module.md — pure data layer + backend plumbing,
zero UI (that's M2). A user can now hold a digital wardrobe per space:
brand merch, club Trikots, family Kleiderschrank, team Kostüme, practice
Dresscode, and personal closet all live as separate pools under the same
Dexie tables, space-scoped like tags/scenes/agents after Phase 2c.

Data model — two tables, no join:

- wardrobeGarments (Dexie v41): single clothing items / accessories.
  Indexed on `category` + `createdAt` + `isArchived`. Encrypted:
  name/brand/color/size/material/tags/notes. Plaintext: category,
  mediaIds, counters, timestamps — all indexed or structural.
  `mediaIds[0]` is the primary photo used for try-on; additional
  ids are alternate views (back, detail) for M7.

- wardrobeOutfits (Dexie v41): named compositions referencing
  garment ids. Encrypted: name/description/tags. Plaintext:
  garmentIds (FK array), occasion (closed enum — useful for
  undecrypted filtering), season, booleans, lastTryOn snapshot.

- picture.images gains `wardrobeOutfitId?: string | null` as a
  plaintext back-reference. Try-on results land in the Picture
  gallery like any other generation; the outfit detail view
  queries them via this id rather than maintaining a third table.

Space scope:

- `wardrobe` added to all five explicit allowlists in shared-types/
  spaces.ts (personal is wildcard, no edit needed). Each space type
  gets a one-line comment explaining the real-world use case.
- App registry: `wardrobe` entry in shared-branding/mana-apps.ts
  with a rose→fuchsia gradient icon (T-shirt on hanger silhouette),
  color #e11d48, tier 'beta', status 'beta'.
- Module registry: wardrobeModuleConfig imported + appended to
  MODULE_CONFIGS so SYNC_APP_MAP picks it up automatically.

Backend:

- MAX_REFERENCE_IMAGES bumped 4 → 8 in picture/generate-with-
  reference (plus the client-side default in ReferenceImagePicker).
  Justified with a comment: face + body + top + bottom + shoes +
  outerwear + 2 accessories = 8. Cost doesn't scale with ref count
  (OpenAI bills per output), so the bump is a pure capability
  expansion with no credit-side risk.
- New POST /api/v1/wardrobe/garments/upload wraps uploadImageToMedia
  with app='wardrobe'. Registered under /api/v1/wardrobe in index.ts.
  Pattern 1:1 with the profile/me-images/upload endpoint; tier-gating
  falls out of wardrobe NOT being in RESOURCE_MODULES (tier='guest'
  works — consistent with picture's plain CRUD).

Stores emit domain events (WardrobeGarmentAdded, WardrobeOutfitCreated,
WardrobeOutfitTryOn, etc.) so later mana-ai missions can observe
activity without polling.

No UI in this commit. M2 (Garments-Grundlayer) wires the route + grid
+ upload-zone; M3 the Outfit composer; M4 the Try-On integration.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-23 18:27:37 +02:00
..
agent-loop-improvements-m1.md docs(plans): agent-loop plan reflects M1 shipped + M2 core shipped 2026-04-23 18:12:58 +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-mcp-and-personas.md feat(personas): M5.a — Playwright visual suite scaffold 2026-04-23 14:33:06 +02:00
mana-research-service.md feat(research): Phase 3a — 4 sync research agents 2026-04-17 15:06:12 +02:00
me-images-and-reference-generation.md docs(plans): me-images M1-M5 status + new wardrobe plan 2026-04-23 15:08:45 +02:00
me-images-space-scope-migration.md refactor(profile,tool-registry): flip meImages from user-scoped to space-scoped (v40) 2026-04-23 18:09:57 +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): point at-rest-sweep row at the restored commit 2026-04-22 22:43:19 +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
wardrobe-module.md docs(plans): wardrobe is space-scoped, allow in all six space types 2026-04-23 15:23:10 +02:00
website-builder.md feat(wardrobe): module foundation — garments + outfits space-scoped data layer (M1) 2026-04-23 18:27:37 +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

README.md

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