Patterns

Morph

One surface, many representations.

A Work Object is one surface, as in the Systead film. It rests as a status pill in its row. When the work needs the person it grows out of that pill into a card; it changes shape as the work moves; when the scope is verified it folds back into the row as a lit badge that comes to rest after a breath. Position, size, radius and chrome spring together; content crossfades inside behind a 4px blur, and exits are faster than entrances. Springs keep their velocity, so a new shape requested mid-morph turns the surface smoothly instead of restarting.

Why one surface

A person who opens three cards has done three things. A person who watched one object change has done one thing, and understands it as the same work. That is the experiential claim Lyotic tests: because the first and last forms are recognised as the same Work Object, the person feels they understood and resolved one job, not that they moved through several cards or apps.

What morphs and what does not

MorphsNever morphs
Position, size and radius of the surface (spring 0.55 / 0.12)The row the object lives in: it never leaves the table
Chrome: chip, card, good, warn, judgment (crossfade 0.28s)The identity head across card states
Content (exit 0.2s to blur 4px, enter 0.34s from 4px)The position of the primary control (MOT-07)
Rows entering (50ms apart)Focus, when the change came from the system (MOT-05)

Motion is not loading

Morphing that hides loading, or containers that move to suggest “the AI is working”, have nothing to do with Lyotic. If the system is waiting, it says what it is waiting for, per target, and stays still.

Interruptible

A leaving representation stops being operable the moment it starts leaving, even while it still fades, so a stale control can never be clicked on its way out (INV-09).