Roadmap.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This is a risky dev-server refactor (repoints CSS custom-property sources across the w...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Restructure the dev-server sidebar (the FILES panel at app.jsx:273–365) so it stops drowning daily work in non-canvas noise:

Part of the Maude Cloud arc — read cloud-phase-0-economics-and-architecture.md first. Nothing else in the arc may start before this phase's gates pass (breaker precondition: "superseding DDRs writt...

Part of the Maude Cloud arc — read cloud-phase-0-economics-and-architecture.md first. Requires Phase 9. The production-release phase.

maude-cloud DB via MCP — D1 works on Free, so this is buildable NOW), Queues producer/consumer (deploy-gated on Phase 11), cron trigger (hourly reconcile), static assets dir for the signup SPA (Pha...

users.mjs — same code, control-plane D1 storage) AND Google OAuth (buyer-side only; OAuth on the Worker via PKCE, no client secret in a browser). never to maude.sh. First magic link IS email verifi...

containment boot-assert verified in the pushed artifact. → The image had never been built and could not be (better-sqlite3 under Bun). It now derives FROM the hub image; containment is asserted at...

hub docs, drives the EXISTING createAutoCommit (import the studio module — it is runtime-agnostic Node/Bun TS) against the server-side checkout at /data/workspace. Author = the human who edited (fr...

Part of the Maude Cloud arc — read cloud-phase-0-economics-and-architecture.md first. Requires Phase 1 complete.

Part of the Maude Cloud arc — read cloud-phase-0-economics-and-architecture.md first. Requires Phases 1–2.

Part of the Maude Cloud arc — read cloud-phase-0-economics-and-architecture.md first. Requires Phases 1–3. This phase keeps the self-host path first-class (positioning guard) and doubles as the cel...

Part of the Maude Cloud arc — read cloud-phase-0-economics-and-architecture.md first. Requires Phases 1–4. First phase that touches vendor-operated infrastructure.

Part of the Maude Cloud arc — read cloud-phase-0-economics-and-architecture.md first. Requires Phase 5 (a live cell to invite people into). Still no money.

Part of the Maude Cloud arc — read cloud-phase-0-economics-and-architecture.md first. Requires Phases 5–6. Billing still manual (no Stripe yet).

Part of the Maude Cloud arc — read cloud-phase-0-economics-and-architecture.md first (§2 economics + §3 pricing table are the input). Requires Phase 7.

Part of the Maude Cloud arc — read cloud-phase-0-economics-and-architecture.md first. Requires Phase 8. Gate for lifting the ≤ 3 tenant cap — you cannot responsibly onboard tenant #4 without this (...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports — this touches the canvas mount harness and canvas-lib, which are load-bearing for ever...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Land every outstanding dependency bump across the pnpm workspace (., site, plugins/design/dev-server, plugins/design/hub) and the side projects (plugins/design/hub bun.lock, scripts/video/final), s...

This plan converts the retro at .ai/logs/system-reviews/design-system-bootstrap-review.md (R1–R6) into sequenced work, plus folds in the multi-DS portion of the old Phase 5 (Tasks 2–7) since multi-...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This plan touches the export pipeline that was just hardened (graceful Playwright-miss...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This mirrors feature-acp-panel-dynamic-claude-code-capabilities' Milestone B (permissi...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports — especially the ACP composer paste-chip flow, the _chat/attachments/ write path, and t...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. Every model/mode/effort list this feature renders MUST be pulled live from the ACP ses...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This plan continues the Phase 31 (DDR-123) native ACP chat panel and builds directly o...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This is a multi-phase epic — execute one phase at a time, each phase is independently...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This is a dev-server change to the FigJam-style annotation system — the standing rule...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This phase again touches the most load-bearing dev-server file (apps/studio/annotation...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports — this plan touches the Phase-23 media-intake stack (use-canvas-media-drop.tsx + annota...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Validate the local test build (Task 5) BEFORE touching CI — the exact Tauri universal-binary bundle path is asserted, not 100% confirmed against this repo's Tauri version.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This is a build/packaging/distribution plan — no UI, no design-system surface.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Surfaced during /flow:done closeout of feature-docs-site-mdcc-skin on 2026-05-15. The parent feature shipped (commits 78d9d8f + 94b4e77) with 0 hard-blockers in scenario-runner but DS-guard + a11y-...

Validate canvas + fumadocs source before implementing. Token names, fumadocs --fd-* slots, and Berkeley/JetBrains fallback chain are authoritative — don't paraphrase them.

tracks on any node) is the cross-platform animation source; maude is its editor (/design:draw + motion utils). It extends the DDR-067 single-source invariant from static geometry to time. (alias /d...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This plan is grounded in a four-agent read of the studio editing subsystems (selection...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports — mirror release.md / release-guide.md exactly where the mechanism transfers, and don't...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports — this feature is a new layer on top of the shipped video-comp spine (DDR-148), not a r...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Give a display: grid container a first-class on-canvas track editor, matching what Figma auto-layout-grids and Webflow's Grid 2.0 give designers: define the column and row tracks, drag the track gu...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. *This touches the sync hot path (apps/studio/sync/) — the standing rule applies: inven...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports — mirror ai-banner.tsx, build-roadmap.mjs, and the HelpModal in client/app.jsx rather t...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This plan is grounded in a divergent debate (BUILDER/SHIPPER/BREAKER, reduce-tier) run...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This plan is grounded in three research passes (CSS-panel map, Photo-panel map, pro-to...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This plan spans flow + design plugins + cli + config schema + templates + docs — it is...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, spec cross-links, and the "pointer, not restatement" doc convention (canonical spec lives in _bootstrap.md...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports — most of this plan REUSES shipped infra (tour engine, readiness pattern, video-comp, f...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This is native-app + dev-server work (Tauri/Rust shell + Bun dev-server route + React...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This is plugin-internals work (markdown commands/agents/skills + JSON schema) — NOT a...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports — most of the machinery already exists; this is a surgical split + a three-file reconci...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, the binary-resolution path (DDR-009/045/084), the maude design <verb> dispatcher (DDR-062), npm files ship...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports — mirror probe-footage / transcribe for the helper, and footage-director for the skill.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This is a design-plugin spec (markdown) change — no runtime code, no tests, no build s...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. The git engine layer (apps/studio/git/service.ts) is dense and security-reviewed — mir...

Validate docs and codebase patterns before implementing. Pay attention to the canvas-origin split (DDR-054 — in-iframe overlays are untrusted; structural changes there carry the runtime-health "par...

Validate docs and codebase patterns before implementing. Pay attention to the canvas-origin split (DDR-054 — the in-iframe overlays are untrusted, treat them differently from the shell), the CSS la...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. Every behavioral claim in this plan was measured in the real WKWebView via the desktop...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This plan extends DDR-148 (the shipped video-comp foundation) — read it and the shippe...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This is FigJam v4 — it extends the v3 AI loop (DDR-100) and the brief-board ingest (DD...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. The FigJam-style draw layer lives in the SVG-annotation world — data model + serialize...

Keep oxc-parser. Work around a Bun 1.3.4+ regression in --compile NAPI native-binding embedding by setting NAPI_RS_NATIVE_LIBRARY_PATH from a Bun-embedded asset path before oxc-parser loads. Per-ta...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Validate design files and existing IDs before implementing. Every JS-referenced ID must be preserved verbatim.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This plan reskins + extends the EXISTING hub admin SPA — it does not build a new app....

Establish the contribution baseline: documented "how to contribute" path, GitHub repo hygiene (PR / issue templates, branch protection docs, Dependabot), basic CI quality gates beyond version parit...

Close the gap between flow and design plugins. Flow commands (/flow:plan, /flow:done) become aware of .design/ — /flow:plan automatically detects canvases relevant to a feature and pulls them into...

Three direct-manipulation capabilities on the already-shipped Inspector substrate, so small tweaks don't need a /design:edit "<feedback>" AI round-trip:

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This plan is the deferred phase-12.1 that DDR-103 spun off from Phase 12 ("Layers drag...

---

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports — the dev-server is Bun-authoritative (DDR-009), the canvas lib is single-source in plu...

Reshape the 29 /flow:* commands (26 existing + 3 Phase 3 additions: help, release-changelog, release-cut) so every command except daily-use ones carries a group prefix. Result:

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports in plugins/design/agents/, plugins/design/commands/, and .design/system/project/.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Produce two 1920×1080 H.264 MP4s — site/public/demo.mp4 (primary, ~60s, embedded in the docs landing) and site/public/demo-30s.mp4 (tight cut for the GitHub README, < 10 MB) — by:

Produce one MP4 at site/public/demo.mp4 (~90 s, single cut, < 16 MB post-loudnorm) by composing 16 scenes on top of phase-15.1 infrastructure (nested workspace, <TransitionSeries>, <TerminalFrame>...

---

Add a small library of diagram primitives to the docs site and insert them into the highest-traffic pages. Today the docs are text-heavy markdown tables — accurate but visually flat. Adding SKU-sta...

Validate the docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports — this plan refactors load-bearing bootstrap contracts (design-system skill ↔ templ...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Stand up a public documentation site under site/ using Fumadocs — a Next.js-based MDX docs framework chosen because its output is AI-readable (clean MDX in repo, indexable via crawlers + LLM tools)...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports (DDR-045 paths, DDR-013 module layout, DDR-048 input-router classify table).

Today the annotation toolkit ships pen / rect / ellipse / arrow / text (anchored only) / eraser. Real review workflows that the user keeps reaching FigJam for need three things we don't have:

Today a canvas is born from a text brief (/design:new "<name>" "<brief>"). There is no way to start from a blank surface, sketch intent with sticky notes / text / arrows, and then ask Claude to rea...

The user wants to drop images onto the canvas (drag a .png from Finder, or paste from clipboard) and paste links that render as a preview chip (favicon + title) — the FigJam move where reference ma...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This phase touches the most load-bearing dev-server file (annotations-layer.tsx, 2755...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. The load-bearing prior art for this whole feature already lives in the repo: plugins/d...

Validate docs and codebase patterns before implementing. Pay attention to the binary-resolution path (DDR-009/084), real-disk paths (DDR-045), canvas-origin split (DDR-063), and the canvas-origin g...

Validate docs and codebase patterns before implementing. Pay attention to canvas-create.ts security pattern, canvas-origin-gate.test.ts, DDR-045 disk paths, and the vocabulary map (Save version / P...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports — this is a wiring slice over machinery that already ships.

Validate docs and codebase patterns before implementing. Pay attention to the OAuth token never landing in _server.json or .design/, DDR-045 disk paths, and the canvas-create.ts security pattern fo...

Validate docs and codebase patterns before implementing. Aspiration bar applies — this is the first-impression surface; /design:new with --perfect is mandatory before Task 2.

Productize release-note + release-cut hygiene as a reusable flow capability. Add a new integrations.changelog block to .ai/workflows.config.json (provider + scope + releaseGuide path), implement th...

Refactor the dev-server's shell to a build-pipeline-driven, Bun-runtime-authoritative architecture targeting concrete performance budgets. Concretely: migrate server source to Bun.serve / Bun.file...

Two-part scope:

Replace the current canvas format — single-file HTML with inline <style> (~50 KB hand-rolled CSS) + <script type="text/babel"> JSX + React 18 UMD + Babel-standalone UMD, reference canvas weighing 7...

Make every TSX canvas — UI mock OR DS specimen — a fully self-contained, browser-loadable canvas backed by a small shared canvas-lib (@mdcc/canvas-lib, virtual-module-resolved at the dev-server lev...

Two interlocked workstreams, one phase, because the visual-sanity gate (workstream A) is the same screenshot pass that catches the motion regressions workstream B prevents — splitting them would re...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This is plugin-internal spec/prompt engineering (markdown skills + commands + template...

Read DDR-054, DDR-063, DDR-064, DDR-072, DDR-078, DDR-079 and .ai/docs/collab-model-design.md before touching any sync/collab code. The no-break exhaustive verify posture applies (per feedback-no-b...

Validate docs and codebase patterns before implementing. Read the existing phase-7 plan (.ai/plans/phase-7-acp-chat-sidebar.md) in full — this phase executes it largely as-written with the native-s...

Validate docs and codebase patterns before implementing. MAUDE_SKIP_RUNTIME_BUILD=1 discipline is load-bearing throughout this phase — never let a CI step regenerate the committed runtime bundles.

Today every .tsx canvas under .design/ renders inside its iframe as a static TSX flow — DCArtboard is a labeled card that participates in normal document flow. Phase 4 turns DesignCanvas into a tra...

Implements DDR-025. The current architecture (DDR-022) treats canvas-lib as project-owned source that gets scaffolded into <designRoot>/_lib/canvas-lib.tsx on first /design:setup-ds. That design ha...

Add a FigJam-equivalent input layer to canvas-lib's DesignCanvas as an opt-in inputMode prop:

Make artboards spatially editable on the infinite canvas:

Toolbar buttons in canvas chrome: pen, circle, arrow, eraser, color picker. Drawing happens on a transparent SVG layer sized to the canvas world (zoomable with viewport from Phase 4). On stroke com...

Rework annotations-layer.tsx from a self-contained pointer-claiming overlay into a portal-rendered layer that lives inside .dc-world (so the world's CSS zoom/translate moves the strokes natively, w...

Replace the current shell-bound BottomBar composer with a FigJam-grade in-place comment experience: the composer pops up at the click location on the canvas (not in a panel chrome at the bottom), p...

A first-class export feature surfaced from the canvas UI (not just CLI). One dialog covers seven formats × four scopes:

Embed a chat sidebar directly in the canvas chrome that speaks the Agent Client Protocol (ACP). The sidebar can connect to a locally-running Claude Code session (or any ACP-compatible agent) so the...

Lay down the Yjs runtime, Awareness protocol, and persistence layer that Phase 9 needs — and as a side-effect, enable multi-tab collab on a single machine: two browser tabs (or two Claude Code inst...

Make collaboration usable across the internet without exposing anyone's laptop, without requiring SaaS, without making contributors learn Yjs / PartyKit / Hocuspocus. Three pieces:

Three strategies were weighed for "make .tsx sync safe":

Linked-mode collaboration today keeps two separate Y.Doc instances per canvas in the dev-server and reconciles them through a side channel (disk files + wholesale-replace relays). That side-channel...

---

---

---

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This re-skins the live site/ Fumadocs app to match the approved maude-DS Studio Docs c...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. The four key decisions are baked in below — do not re-litigate them mid-execution.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports in plugins/flow/.

Add a user-facing "Is maude safe?" page to the docs site that explains the threat model honestly: what runs where, what's trusted vs untrusted, and the mechanisms that make each mode safe. Audience...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This is a spec/infrastructure change to the design plugin's bootstrap flow — pure mark...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This plan changes the design-plugin bootstrap spec (markdown skill + command docs + re...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. The 3-stage architecture below is load-bearing — do not collapse stages, do not reintr...

The moodboard direction gates catch a disliked direction before the scaffold. They do not catch a scaffold that ran but produced silently-broken output — empty files trusted as written, a transpile...

The master reference for the Maude Cloud arc: the complete path from zero infrastructure to a paid production release on maude.sh. Execution order = the numbered files cloud-phase-1-.md → cloud-pha...

Everything a human must do by hand — accounts, logins, tokens, tooling, MCP wiring — so the phase executions run smoothly and agent-driven. Companion to cloud-phase-0-economics-and-architecture.md....

Account: b5b596efe65abb732777c7171dc18145 (M.dovrtel@gmail.com) Live control plane: https://maude-cloud.maude1agh.workers.dev

RESERVED_IDS enforced at the UI too so the error arrives while typing). ids; live mode still throws — that stays). Metadata carries project id only. reconciler drives stepToward('active') → cell he...

Windows registry via tauri.conf); handler parses maude://join/<workspace>/<invite> and maude://open/<workspace>/<project>. clone/attach the remote project into a local folder → open in Studio. Reus...

comment text, presence JSON. Bytes it never interprets. cookieless for assets; the cell's boot-assert and CI grep gate stay green.

only. Installation token minting in the cell (short-lived, never stored raw). (the no-force assertion already exists; the live path must import, not copy). validated form), branch (default maude-wo...

sessions per Phase 13 T5), rename, share toggle (Phase 18), mirror settings (Phase 19, owner-only). reconciler's view of the world (never a second source of truth). (git bundle + assets manifest) →...

1. Phase 18 share view live and stable (containment proven in production). 2. Paying tenants exist (the pressure DDR-193 warned about is then real, and the decision is made deliberately rather than...

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, frontmatter, and closing-prompt conventions.

Validate docs and codebase patterns before implementing. Pay attention to existing naming, utils, and imports. This is the extracted Phase 5 of feature-ai-media-generation (closed at Phase 4, 2026-...