v0.2.2

Motion score:

The plan for motion, written before the code (motion-direction.md). Fill only the parts the scope needs: a single fix needs the gate and one life cycle.

Character

Action and flow ·
Why, from the subject
Tokensmotion_tokens.mjs --action <action> --flow <flow> →
Out of character

Layers in use

LayerIn this projectWhat it contains
Feedbackyes
Continuityyes / no
Arrivalyes / no
Signatureyes / no
Narrativeyes / no

The gate

Every candidate, including the ones rejected. What does not move is part of the design.

CandidateHow often seenKind (feedback, continuity, explanation, identity, narrative)Decision
animate / do not animate, because

Sequence:

One table per event that moves two or more things.

Trigger:

ElementRole (lead, support, decoration, still)StartsLastsMotionRelation (together, overlap, sequence, carry)

Cast as still, and why:

Life of one interaction:

StageDecision
Rest
Trigger
Response within 100 ms
Timing and easing<tokens, by job>
Origin
Continuity
Interruption
Reversal
Completion
Reduced motion
Touch, keyboard, assistive technology

Signature moment

Fact and device it comes from
How it is discovered
What the visitor understands afterwards
What it hands on to
Fallbacks: touch, keyboard, reduced motion, no script, a slow device

Seen

MomentCommandStripQuestions raised, and the answer
Entrancemotion_strip.mjs <url> --trigger load --reduced
motion_strip.mjs <url> --trigger "click:<selector>" --interrupt 120 --exit undo

Not checked by a person on a device: