01 · Positioning
How the product takes on the work
WanMoTai combines model chat, a node canvas, tasks, and generated assets in one local creative space.
The relationship between prompts, model choices, and outputs stays visible, editable, and reusable.
02 · Context
The problem and the people
Why it needs to exist
Multi-model creation scatters conversations, parameters, generated assets, and their relationships across separate tools.
Who it is for
Creators comparing models, organizing prompts, generating assets, and mapping how ideas connect.
03 · Core flow
Core workflow
Four key views trace the complete path from entering the product to handling the work and confirming the outcome.
- 01
Conversation workspace
Switch capabilities, organize context, and keep generation history in one place.
- 02
Infinite canvas
Use nodes and links to express relationships between prompts, analysis, pages, and outputs.
- 03
Assets and tasks
Return generated results to their task so files do not drift away from the discussion.
- 04
Models and providers
Separate local and cloud capabilities while showing simulated connection state only.
04 · Product views
Four views of how the product works
All four views stay visible in a masonry gallery. Open any card for a larger view and continue with the arrow keys.
Conversation workspace
Switch capabilities, organize context, and keep generation history in one place.
Infinite canvas
Use nodes and links to express relationships between prompts, analysis, pages, and outputs.
Assets and tasks
Return generated results to their task so files do not drift away from the discussion.
Models and providers
Separate local and cloud capabilities while showing simulated connection state only.
05 · Decisions
Three product decisions
- 01
Models are replaceable nodes
Conversations and plans do not belong to one provider; model choice is part of the workflow, not the product center.
- 02
Inputs and outputs stay visible
Prompts, parameters, sources, and assets keep their relationships so results can be understood later.
- 03
Connection state is never guessed
Only verified provider state is shown, and unknown failures never trigger silent switching or retries.
06 · Current state
What is complete—and what is not
The local studio is implemented; live connectivity for each provider still requires separate validation.
What the product changes
The relationship between prompts, model choices, and outputs stays visible, editable, and reusable.
Source and implementation
Source code is not public
Portfolio boundary
This site shows redacted interfaces and product logic only. It never connects to source databases or performs real publishing, applications, sending, or payments.
Next