Link wallet for agents
Install and connect the agent first, then request an itinerary change in chat, show the cost and move to phone confirmation. Repeat the cost and merchant name across interfaces to identify the same request.
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Link wallet for agents — Today, we’re launching the… · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#001c11}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>Motion and composition
Local motion · Composition rules
Explain the full authorization process for one payment
Install and connect the agent first, then request an itinerary change in chat, show the cost and move to phone confirmation. Repeat the cost and merchant name across interfaces to identify the same request.
Use deep green for processing and white cards for decisions
Keep commands and dialogue on a deep green fine-dot background; switch to narrow white cards for user decisions. Reserve green for links, notification marks, and final success feedback.
Show the notification before expanding approval
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Link wallet for agents — Today, we’re launching the… · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#001c11}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="15.5" data-end="21.5"><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>Lift the phone from the background and bring a notification into its lower half; expand it into payment authorization after clicking, then show completion with recognition and check icons. Do not skip confirmation before success.
Substitute a new task
Update task, amount, merchant, and payment method consistently throughout. Preserve agent request—human confirmation—completion receipt dependencies.
Sections and rhythm
Click a section to seek to it in the choreography example above.






Visual references · Discrete still frames
Creating other themes
- Adapt to other authorization tasks, keeping requested amount and confirmation information consistent.
Production constraints
Command line / authorization explanation card / expense summary / phone notification / payment confirmation / receipt
- Install and connect the agent first, then request an itinerary change in chat, show the cost and move to phone confirmation. Repeat the cost and merchant name across interfaces to identify the same request.
- Keep commands and dialogue on a deep green fine-dot background; switch to narrow white cards for user decisions. Reserve green for links, notification marks, and final success feedback.
- Lift the phone from the background and bring a notification into its lower half; expand it into payment authorization after clicking, then show completion with recognition and check icons. Do not skip confirmation before success.