Computer for Counsel — Perplexity for lawyers
Connect tools, sources, and three output types through one professional workflow: establish the problem first, then show how each deliverable serves its purpose.
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Computer for Counsel — Perplexity for lawyers · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#fafaf7}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
Professional positioning and tool connections
Open with the professional scenario, then tool connections. Let icons serve the task without overpowering its heading; maintain professional readability with pale warm color, teal accents, and fine rules. Use serif main headings if appropriate and sans serif tasks and file content.
Connect task, execution, and sources
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Computer for Counsel — Perplexity for lawyers · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#fafaf7}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="12" data-end="34"><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 task input, show execution steps before expanding the source sidebar. Give sidebar and body the same task heading, placing the highlighted source near the current content so they remain related.
Give three outputs three layouts
Emphasize status and categories in regulation dashboards, clause structure in agreements, and conclusions and citations in research reports. Follow actual work order, retaining shared page margins and file-heading areas during transitions.
| Output | Main visual structure |
|---|---|
| Tracking dashboard | Category columns, states, and items |
| Agreement document | Heading, sections, and key clauses |
| Research report | Summary, conclusions, and sources |
Close with a deliverable recap
Show all three output types before gathering them into output columns, without new actions at the end. Connect to the brand ending through a short summary heading, retaining workflow continuity.
Rewrite the workflow for another profession
Adapt to finance, procurement, or engineering reviews, replacing tasks, source types, and outputs together. Preserve connect tools→execute task→cite evidence→deliver.
Sections and rhythm
Click a section to seek to it in the choreography example above.






Visual references · Discrete still frames
Creating other themes
- For other professions, replace source categories, professional tasks, and output forms.
Production constraints
Tool ecosystem / task box / source list / regulation dashboard / agreement document / research report
- Establish the domain, show input and sources, then provide three specific business outputs.
- Match outputs to legal work stages instead of repeatedly showing one interface.