Interaction and motion: installation happens before the boundary

Motion should reveal causality, not create fake execution.

Five-stage timeline

Project: source and target identity are visible. Prepare: acquisition and installation appear only on the preparation side. Ready: source and materialized environment are two separate assets. Deliver: both cross the task boundary independently. Work: activation has completed and the native project task begins.

Interaction rules

Scroll drives the story forward and backward. Pausing the page pauses the visual state. Reduced-motion users still receive every piece of information. Hover and focus may reveal detail but must not trigger installation or cloud provisioning.

Truthful status

Downloaded is not materialized. Materialized is not activated. Activated is not task success. The interface should never collapse those states into one green check.