ııı motion.mdVideo style specification
Glean / V379

Glean Agents launch

Expand one input into cross-department workflows. Connect task cards, people and data sources with lines, then return results to a readable interface.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 61.00 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>Glean Agents launch · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#f3f1e6}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 elementsGeometric markAgent task cardDepartment labelPrompt barWorkflow nodeAnswer cardGovernance lock
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Provide one unified entry first

Surround a short heading with blue spheres and fluorescent geometry on cream. After the directory appears, distribute small agent-task cards around the frame, retaining a central proposition or input.

02

Expand requirements into sequential nodes

Expand requirements into sequential nodesRule example
0.00 / 7.00 seconds
25–32 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>Glean Agents launch · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#f3f1e6}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="25" data-end="32"><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>

After prompt input, cut to a vertical flow with trigger above, followed by search and synthesis below. Connect cards with arrows, introducing each step after its predecessor.

03

Explain departmental scale separately from knowledge reach

Use people and departments to explain who uses it, and data-source connections to explain where information comes from; do not cram both networks into one diagram. Gather into an agent matrix and brand last.

04

Prepare a complete workflow for replacements

Prepare at least one real request, three processing steps, and a result. Replace departments and tool icons if needed, but keep trigger conditions, execution order, and result formats consistent.

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 8.00 seconds
8.00s
Composition reference at 18.00 seconds
18.00s
Composition reference at 32.00 seconds
32.00s
Composition reference at 46.00 seconds
46.00s
Composition reference at 56.00 seconds
56.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Suitable for enterprise assistants and automation platforms; preserve entry, workflow, result, and scale.

Production constraints

Geometric mark / agent task card / department label / prompt bar / workflow node / answer card / governance lock

  • Surround a short heading with blue spheres and fluorescent geometry on cream. After the directory appears, distribute small agent-task cards around the frame, retaining a central proposition or input.
  • After prompt input, cut to a vertical flow with trigger above, followed by search and synthesis below. Connect cards with arrows, introducing each step after its predecessor.
  • Use people and departments to explain who uses it, and data-source connections to explain where information comes from; do not cram both networks into one diagram. Gather into an agent matrix and brand last.
  • Prepare at least one real request, three processing steps, and a result. Replace departments and tool icons if needed, but keep trigger conditions, execution order, and result formats consistent.