Layout

Aria layout comes from the stream. The main shape is not a decorative card grid, but a line that moves through rail, node, run state, result, and recall.

• Page sections are not floating cards.
• Do not put cards inside cards.
• Radius stays restrained unless a platform shell requires more.
• Dense but readable beats decorative spaciousness for product surfaces.
• Motion should explain state transition, not decorate the page.
• One row carries one job. Context, status, and action can share a row only when they belong to the same line.

[workspace/status]
[input line]
[3 next actions]
[current stream]

Mobile keeps one primary job per page.

[brand/status]
[one-line input]
[recent 3]
[sync/agent state]

Desktop quick capture is an entry point, not a miniature web app.

[shell navigation]
[stream date/group view]
[active line editor]
[contextual inspector or agent result]

Web can carry density, but the active line owns attention.

Allowed motion:

• Quick capture open and close.
• Modal, drawer, popover, tooltip entrance.
• Active line focus.
• queued -> running -> needs_review -> done transition.
• Public publish confirmation.

Avoid:

• Animation while typing in the editor.
• Ambient decorative motion.
• Page-wide motion that hides the current job.
• Motion that ignores prefers-reduced-motion.