ııı motion.mdVideo style specification
Parallel Web Systems / V198

Parallel Decisions API

Start with a business question, break it into queryable facts, then assemble facts into an actionable table. Orange marks only the question focus and final priority.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 35.30 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>Parallel Decisions API · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#ecece7}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 elementsQuestion barDotted mapFact cardSource labelTablePriority markBrand
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

State the decision question before breaking down queries

State the decision question before breaking down queriesRule example
0.00 / 8.00 seconds
3–11 seconds · Motion 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>Parallel Decisions API · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#ecece7}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="3" data-end="11"><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>

Center a white question bar on a pale gray grid and dotted map. Break the question into company size, product changes, and related information, adding fact cards with source areas one by one.

02

Answers become comparable columns, not scattered prose

Answers become comparable columns, not scattered proseRule example
0.00 / 7.00 seconds
18–25 seconds · Motion 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>Parallel Decisions API · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#ecece7}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="18" data-end="25"><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>

Show accounts and owners first, then add headcount, recent events, and relevance columns left to right. Keep row identities fixed and choose an action target through priority marks at the end.

03

Return to the original business question at the end

Return the full table beneath the question bar to explain how queries support selection. Rewrite decisions, dimensions, and output actions, not just company names; match sources and states to example data.

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 6.00 seconds
6.00s
Composition reference at 12.00 seconds
12.00s
Composition reference at 15.00 seconds
15.00s
Composition reference at 24.00 seconds
24.00s
Composition reference at 30.00 seconds
30.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Replace decision question, fact dimensions, sources, and action output; preserve the question-to-table loop.

Production constraints

Question bar / dotted map / fact card / source label / table / priority mark / brand

  • Center a white question bar on a pale gray grid and dotted map. Break the question into company size, product changes, and related information, adding fact cards with source areas one by one.
  • Show accounts and owners first, then add headcount, recent events, and relevance columns left to right. Keep row identities fixed and choose an action target through priority marks at the end.
  • Return the full table beneath the question bar to explain how queries support selection. Rewrite decisions, dimensions, and output actions, not just company names; match sources and states to example data.