Skip to content

Build the end-to-end Product Design workbench - #68

Draft
Ankit6149 wants to merge 31 commits into
masterfrom
feature/product-design-editor
Draft

Build the end-to-end Product Design workbench#68
Ankit6149 wants to merge 31 commits into
masterfrom
feature/product-design-editor

Conversation

@Ankit6149

Copy link
Copy Markdown
Owner

Status

Draft implementation for #67. Keep this PR draft until the complete Product Design acceptance journey, CI, preview, persistence recovery, and production verification pass.

Product outcome

This PR replaces the previous assumption that Product Architecture was Product Design. It introduces a dedicated Product Design workbench inside the unified Studio while preserving Requirements and Architecture as separate connected views.

The intended complete path is:

Document → layers → objects/references → dimensions/notes → concept part → lightweight 3D → checkpoint → reload → export/import

Implemented so far

  • official open-source research and simplification decisions;
  • renderer-independent Product Design document/object contracts;
  • native IndexedDB repository with documents, Blob assets, and checkpoints;
  • memory repository for deterministic tests;
  • command-based Zustand editor session with autosave, bounded undo/redo, grouping, alignment, z-order, checkpoints, and export/import;
  • interactive SVG canvas with grid, zoom/pan, drawing, selection, marquee, drag, resize, keyboard movement, and missing-asset states;
  • clean editor workbench with compact toolbar, layer/object tree, contextual inspector, history/checkpoints, local save status, and responsive panel collapse;
  • same-ID concept-part handoff into an event-driven low-power Three.js preview;
  • Product navigation now distinguishes Product Design, Requirements, Architecture, and System Blueprint.

Trust boundary

Product Design owns visual/product intent and concept dimensions. It does not claim exact B-Rep/STEP CAD, tolerances, interference, mass, tooling, or manufacturing authority.

Remaining before review

  • model/repository/store and interaction contract tests;
  • resolve lint and TypeScript findings;
  • verify IndexedDB reload and export/import identity;
  • asset failure/relink acceptance;
  • responsive manual review;
  • exact-head Vercel preview and /studio verification;
  • issue completion evidence and merged production deployment.

Closes #67 only after the full production acceptance gate passes.

@vercel

vercel Bot commented Aug 4, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
hardware-studio Error Error Aug 4, 2026 4:20pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[P0][Product Design] Build the first complete design editor with durable project persistence

1 participant