ııı motion.mdVideo style specification
Prime Intellect / V203

Introducing Prime Agent: A self-improving RLM harness for coding and long-running …

Introduce product mechanisms through code and states, then conclude with task results and summary figures.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 44.44 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>Introducing Prime Agent: A self-improving RLM harness for coding and long-running … · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#080807}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 elementsGranular terrainTerminal panelSubtask stateGrid gameResult scoreCurve chart
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Keep granular backgrounds behind a readable terminal

Use dark particle terrain for depth and an opaque near-black terminal. Set headings, code, and logs in monospace, limiting blue-orange syntax colors to code and keeping backgrounds dimmer than text.

02

Explain one relationship per mechanism page

Explain one relationship per mechanism pageRule example
0.00 / 10.00 seconds
10–20 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>Introducing Prime Agent: A self-improving RLM harness for coding and long-running … · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#080807}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="10" data-end="20"><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>

Progress through tool calls, memory improvement, and agent communication. Match upper code with lower status structure, retaining subtask names across positions.

03

Expand from one task to overall results

Show grid-task changes before gathering multiple results into a mosaic and enlarging the score, then move to summary curves. Hold numbers, task counts, and axis labels clearly.

04

Replace code and results together with tasks

Adapt to coding, reasoning, or automation. Replace requests, code, task visuals, and scores together to explain one capability; give installation commands their own screen before the ending.

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 5.00 seconds
5.00s
Composition reference at 16.00 seconds
16.00s
Composition reference at 25.00 seconds
25.00s
Composition reference at 35.00 seconds
35.00s
Composition reference at 43.00 seconds
43.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Adapt to coding, reasoning, or automation. Replace requests, code, task visuals, and scores together to explain one capability; give installation commands their own screen before the ending.

Production constraints

Granular terrain / terminal panel / subtask state / grid game / result score / curve chart

  • Introduce product mechanisms through code and states, then conclude with task results and summary figures.
  • Use dark particle terrain for depth and an opaque near-black terminal. Set headings, code, and logs in monospace, limiting blue-orange syntax colors to code and keeping backgrounds dimmer than text.
  • Progress through tool calls, memory improvement, and agent communication. Match upper code with lower status structure, retaining subtask names across positions.