ııı motion.mdVideo style specification
Manus / V234

Branch | Branching conversations

Open a second line of thought from the same conversation. Before the branch appears, make its inherited context clear; afterward, show the different ways to continue.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 16.43 seconds
Motion and composition example Open separately ↗
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Branch|Branched conversations · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#f7f8f6}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="sequence"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>
Visual elementsOriginal conversationBranch nodeCopied conversationContinue typing
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Show the original conversation fully first

Keep the task, completed output, and branch entry visible in the original conversation. Use clear sans-serif text, a light background, and low-contrast message blocks; reserve accents for the new branch or reply.

02

Preserve shared content when branching

After clicking branch, leave the original on one side and open the new conversation on the other. Shared text and order remain identical; new requests and results then appear gradually.

Column widths may change, but do not rearrange all content on both sides at once. Establish the source with a short connection or shared title, then make the new branch the reading focus.

03

Replace with two genuinely different directions

For example, adapt one brand video into landscape and square formats, or one proposal into two styles. Keep shared content unchanged and match new requests and outputs to each branch; do not merely rename two windows.

SEQUENCE

Sections and rhythm

Click a section to seek to it in the choreography example above.

Composition reference at 0.00 seconds
0.00s
Composition reference at 3.00 seconds
3.00s
Composition reference at 5.00 seconds
5.00s
Composition reference at 9.50 seconds
9.50s
Composition reference at 11.00 seconds
11.00s
Composition reference at 13.57 seconds
13.57s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Adapt to branching design proposals, preserving the shared starting point and later differences
  • Replace branch content and clearly distinguish the original from the new branch

Production constraints

Original conversation / Branch node / Copied conversation / Continued input

  • Show the historical point that can be branched before copying the shared context
  • briefly compare two conversations side by side, then select one and push in to continue
  • repeat the heading to echo the content branching rather than adding unrelated decoration