Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.
Visual Evolution Round 29 — Motion Governor
Date: 2026-07-20 Status: research recommendation for the next bounded viewer slice
Executive decision
Build a Motion Governor before adding another chapter transition effect.
Archify now has enough good motion primitives. Its next visual-quality problem is that they do not yet have one conductor. A normal artifact can run a header pulse, Signal Flow scan, authored trace edges and nodes, and a reader-triggered story or route signal at the same time. Guided Story playback owns its own timer, but it does not own the rest of the page's motion budget. The result can look busy at the exact moment a chapter is supposed to become clear.
The next slice should therefore add:
- one visible
Live/Stillcontrol near the top of the artifact; - one viewer-level motion mode, initialized before first paint;
- one replaceable motion owner at a time;
- automatic suppression of ambient motion while a chapter, focus, route, lens, or bounded preview owns the reader's attention;
- complete static fallbacks that preserve every semantic state;
- a dynamic reduced-motion and page-visibility response;
- no schema, renderer geometry, graph copy, dependency, or export-state change.
This is not an accessibility-only cleanup. It improves the product's visual hierarchy: when Story Trail moves, only the story moves; when the reader asks a route question, only the route answers; when the reader chooses Still, the same beautiful artifact remains completely readable.
The promising shared-anchor Chapter Handoff belongs immediately after this foundation. Adding it first would introduce another transition into a viewer that still has ungoverned infinite motion.
Scope and method
This recommendation is based on:
- the current
codex/archify-visual-evolutionworktree, not an older package; - the complete visual-evolution trail: the initial Fireworks review plus Rounds 2–28;
- current viewer CSS and runtime ownership paths;
- fixed open-source commits and official standards/product documentation;
- the existing Archify boundary: one deterministic self-contained HTML artifact, one canonical SVG, zero runtime dependencies, stable semantic IDs, and no layout mutation in viewer interactions.
No source, schema, fixture, generated artifact, or test was changed during this research. This document is the only Round 29 file.
What Rounds 1–28 already cover
The existing research is unusually complete. The next slice must not rename or duplicate one of these layers.
| Rounds | Existing product surface |
|---|---|
| Initial review, 2 | Fireworks comparison; stable IDs; focus; gallery; bounded guided views |
| 3 | timed Play/Pause over existing views |
| 4–5 | question-first recipes and one generated proof per recipe |
| 6 | Classic / Signal Flow / Blueprint identities and wide-mobile containment |
| 7 | Presentation Stage over the live artifact |
| 8 | Semantic Node Finder |
| 9 | proof-first landing stage |
| 10–11 | Relationship Lens and exact-edge preview |
| 12 | Semantic Camera with bounded desktop fitting and contained-mobile scroll |
| 13 | path-aware Story Trail |
| 14–16 | one-shot share playback, Share Chapter Cue, and Semantic Story Beats |
| 17 | Semantic Passport |
| 18 | Semantic Radar |
| 19 | finite Intent Trace |
| 20–21 | Route Probe and searchable endpoints |
| 22 | Diagram Guide |
| 23 | Reading Depth / semantic zoom |
| 24 | Semantic Lens |
| 25 | finite selection-triggered Semantic Flow and finite Intent Trace |
| 26 | finite exact-edge Relationship Pulse |
| 27 | selective Semantic Legend Bridge |
| 28 | Named Chapter Rail |
The pattern across the later rounds is already clear: motion should answer an explicit question, have one owner, be finite where possible, and leave the canonical graph untouched. That discipline exists inside several individual features, but not yet at the whole-viewer level.
Current Archify evidence
The viewer has several independent animation clocks
The shared template currently declares these visible moving surfaces:
| Surface | Current trigger | Current lifetime | Semantic role |
|---|---|---|---|
.pulse-dot |
every normal artifact | 2s infinite |
decorative live status |
| Signal Flow scan | every Signal Flow artifact | 6s infinite |
decorative preset atmosphere |
| Semantic Radar live dot | Radar open | 2.4s infinite |
orientation-panel status |
| Route Probe flow | a route result | 1.45s infinite |
exact directed path |
| Story Trail flow | active Story playback | 0.78s infinite, bounded by the story timer |
current authored chapter |
| authored trace edges | meta.animation = "trace" |
2.4s infinite |
ambient whole-graph direction |
| authored trace nodes | meta.animation = "trace" |
3.6s infinite |
ambient active-node signal |
| Lens / Intent / Relationship pulses | explicit selection or preview | one finite pass | bounded reader question |
The declarations are visible in the current template's header and preset styling, Radar styling, and motion rules.
Ten of the eleven proof fixtures currently opt into trace motion, and five of those also use Signal Flow. The simultaneous-motion case is therefore a primary product path, not an exotic combination.
Guided Story does not own the ambient layer
The one-shot share path deliberately pauses authored trace through the
data-share-playback selector. Manual Story playback does the opposite: its
startPlayback() removes data-share-playback, activates the Story layer, and
starts the 3.2-second chapter timer. Authored trace can therefore continue under
Story Trail, while Signal Flow scan and the header pulse also keep running.
Relevant current paths:
This does not corrupt state, but it weakens direction. The reader sees more than one moving explanation and must infer which motion belongs to the selected chapter.
Reduced motion is strong locally but incomplete globally
The current media query correctly disables Signal Flow scan, authored trace,
Story, Radar, route, Lens, preview, and camera/detail transitions. It does not
include .pulse-dot. Several runtime modules also call matchMedia()
independently, and only some listen for a live preference change.
The result is a collection of good per-feature fallbacks rather than one inspectable effective policy. A user without an OS-level reduced-motion setting also has no visible way to stop automatic motion.
See the current reduced-motion block and the feature-specific media-query reads around Guided Views, Intent Trace, Relationship Pulse, and Semantic Camera.
Hidden-page and embed ownership are partial
Guided playback already pauses on visibilitychange, which is correct. Ambient
CSS trace and decorative preset motion have no shared hidden-page state. Browsers
may throttle them, but Archify has not expressed an application invariant.
Embed mode hides most chrome and pauses authored trace, yet the Signal Flow
container scan is not governed by the embed trace selector. The normal embed
should be still; ?embed=1&play=1#view=... should permit exactly the requested
bounded Story and nothing else.
The existing Archify.motion name is already taken
Archify.motion is the public WebM recording surface with canRecord() and
recordWebm(). A governor must not replace or silently change this API. Use a
distinct owner such as Archify.motionGovernor and keep explicit motion export
separate from live-viewer preference.
See the current recording implementation and animation contract tests.
Primary-source findings
1. WCAG requires a visible stop mechanism for long automatic motion
WCAG 2.2 Success Criterion 2.2.2 applies when moving or blinking content starts automatically, lasts longer than five seconds, and appears alongside other content. It requires a pause, stop, or hide mechanism unless the motion is essential (SC 2.2.2, Understanding 2.2.2).
WAI Technique G186 is unusually direct for Archify: the control must be keyboard-accessible, named, and near the top or adjacent to the motion, and one control may stop all moving or blinking content on the page (G186).
WCAG 2.3.3 also says non-essential motion triggered by interaction can be disabled (Animation from Interactions). It is Level AAA, but it matches Archify's stated quality target and existing reduced-motion behavior.
Borrow: one obvious top-level control; all automatic movement must obey it; interaction-triggered camera/pulse motion must have a static alternative.
Do not borrow narrowly: a Story Play/Pause button controls only Story. It is not a sufficient whole-page stop mechanism for trace, scan, status pulse, Radar, and route motion.
2. Media Queries and CSS Animations distinguish preference, pause, and stop
Media Queries Level 5 defines prefers-reduced-motion: reduce as a request to
remove or replace non-essential motion that can cause vestibular discomfort or
attention distraction
(Media Queries Level 5).
CSS Animations Level 1 defines animation-play-state: paused as retaining the
animation's current progress and resuming from that point later
(CSS Animations Level 1).
That is appropriate for a reader-paused semantic timeline. It is not always the
best treatment for atmosphere: a frozen half-invisible pulse or partial packet
can look broken. Ambient decoration should return to its complete static base;
finite runtime overlays should clean up; an intentionally paused Story should
retain its explicit semantic beat state.
Borrow: initialize from the OS preference before paint; centralize the live media-query listener; distinguish stopping ambient decoration from freezing a reader-owned semantic story.
Skip: a blanket * { animation-play-state: paused } as the whole contract.
It leaves stale overlay DOM and arbitrary partial visual phases.
3. Fireworks proves that motion is strongest when the changing area is small
The comparison remains pinned to
fireworks-tech-graph@50c819d.
Its reviewed motion contract keeps nodes, labels, containers, markers, and camera
fixed while routes draw and carry direction; the measured reference loops change
only a small percentage of the canvas
(motion contract).
That same artifact is an infinitely looping GIF, while its interactive HTML viewer is a separate small pan/zoom/export surface. The viewer removes transitions for reduced motion but exposes no page-level motion controller (interactive viewer).
Borrow: fixed geometry, semantic direction, small moving area, validated motion roles, and a clean viewer/export boundary.
Skip: treating an infinite showcase loop as the default live reading mode. Archify's interactive artifact can offer reader control that a GIF cannot.
4. Mapbox shows that a new camera owner replaces the old one and motion is optional
The comparison is pinned to
mapbox-gl-js@e3dec292.
Its animation options include animate: false, duration/easing, and an explicit
essential escape hatch. easeTo() stops the preceding ease before starting a
new one and reduces duration to zero when the preference requires it; flyTo()
falls through to an immediate jump
(camera options and implementation,
ease replacement,
reduced-motion fallback).
Borrow: replacement instead of stacking; zero-duration semantic completion; camera motion must never be marked essential for a technical diagram.
Skip: dramatic fly arcs, prolonged zoom-out, inertial scene travel, or a second persistent camera model. Archify's current 480ms bounded fit is enough.
5. reveal.js demonstrates stable matching and mandatory cleanup between transitions
The comparison is pinned to
reveal.js@a3b9406.
Auto-Animate only connects compatible slide pairs, uses stable matching, can
explicitly restart rather than imply continuity, and calls reset() before a
new run. Reset removes target attributes and the injected transition stylesheet
(AutoAnimate source,
official Auto-Animate guide).
This is valuable evidence for the deferred Chapter Handoff: only stable shared semantic IDs can justify continuity, and every transition needs atomic cleanup. It also supports the governor itself: a new owner must clean the prior owner's runtime layer before beginning.
Borrow now: reset-before-run and owner-token cleanup.
Borrow later: shared stable IDs as chapter anchors.
Skip: FLIP-transforming graph nodes, SVG morphing, full unmatched-element fades, or reveal.js's slide/runtime dependency.
6. LikeC4 has a compelling chapter handoff, but it should follow the governor
The comparison is pinned to
likec4@f0ce898.
Its navigation state reads the current viewport, preserves the screen position
of a node that exists in both views, and only then settles the target viewport;
when no corresponding node exists it uses a bounded fallback rather than
pretending there is a shared anchor
(navigation state).
Its embed and export pages deliberately disable or fix interactive viewer state
(EmbedPage,
ExportPage).
Borrow later: choose a stable shared node as an anchor, preserve its screen position for the first transition phase, cap duration, and cut when continuity cannot be proved.
Skip now: adding this extra movement before Archify can guarantee that ambient trace, scan, pulse, route, and Story do not compete with it. Also skip LikeC4's graph replacement, state-machine/framework stack, and viewport history.
7. Hidden documents need an explicit lifecycle decision
The HTML Living Standard exposes Document.visibilityState and the bubbling
visibilitychange event for visible/hidden transitions
(HTML page visibility).
Borrow: hidden means no active viewer motion and no CPU-only animation ownership. Existing Story pause behavior should become the system rule.
Do not automatically restart: returning to visible may restore ambient Live only when the reader has not selected Still. A paused Story, route pulse, or one-shot preview never restarts without a new explicit action.
Candidate matrix
Scores use 1 (weak) to 5 (strong). Risk is inverted: 5 means low product
risk / a good fit for the current architecture.
| Candidate | Immediate reader value | Direction / continuity | Visual restraint | Accessibility closure | Mobile / embed fit | Architecture risk | Decision |
|---|---|---|---|---|---|---|---|
| Motion Governor: Live/Still + one owner | 5 | 5 | 5 | 5 | 5 | 4 | Build now |
| Shared-anchor Chapter Handoff | 4 | 5 | 3 before governance | 2 before governance | 3 | 3 | Later, directly after Governor |
| Chapter Compass in Rail/Radar | 3 | 4 | 3 | 4 | 2 | 4 | Later only with reader evidence |
| Longer fly-to / overview waypoint transition | 3 | 4 | 2 | 2 | 2 | 3 | Skip |
| Scroll-driven chapter activation | 2 | 3 | 2 | 2 | 1 | 2 | Skip |
| Layout morphing or moving shared nodes | 2 | 2 | 1 | 1 | 1 | 1 | Skip |
Why the Governor wins this round
The Named Chapter Rail already solves discovery. Semantic Camera already supplies a bounded transition. Story Trail and Story Beats already provide truthful direction. The next visual gain does not come from another animation shape; it comes from guaranteeing that the right existing shape is the only thing moving.
The Governor also unlocks the best later candidate safely. Once a Story chapter can be the sole owner, a shared-anchor camera handoff can be added without competing with trace, scan, node pulse, Route Probe, or preview motion.
Recommended runtime contract
1. State vocabulary
Use viewer-only HTML state, never SVG authoring state:
html[data-motion="live"]: motion is permitted;html[data-motion="still"]: no visible viewer motion is permitted;html[data-motion-owner="ambient|story|focus|route|lens|intent|relationship|legend|radar|none"]: the one semantic surface allowed to spend the motion budget;- an internal monotonically increasing owner token prevents a stale
animationend, timer, or cleanup callback from releasing a newer owner.
Expose a distinct runtime object:
Archify.motionGovernor = {
mode(),
owner(),
setMode("live" | "still", options),
claim(name, cleanup),
release(token),
suspend(reason)
}
Keep the existing Archify.motion.canRecord() and
Archify.motion.recordWebm() export surface untouched.
2. Initialization before first paint
The existing early <head> bootstrap should set effective motion before the
body becomes visible:
prefers-reduced-motion: reduce→still;- normal
?embed=1→still; - otherwise →
live; ?embed=1&play=1#view=...may enterlive/storyonly after the explicit one-shot contract is resolved, and every ambient selector remains off;- a media-query change to
reduceforces Still immediately; - a later change back to
no-preferencedoes not automatically restart a Story or one-shot effect.
Do not add a JSON field, URL hash field, or required storage dependency. A
best-effort Still preference may be remembered under one namespaced browser key
only if access is exception-safe. An OS reduced-motion preference initializes
Still; a reader may explicitly choose Live for the current document, but that
override is never persisted across reload and a new system change to reduce
forces Still again.
3. Visible control
Add one native button to the top toolbar, adjacent to Theme / Present rather than inside Guided Views:
- visible copy is
LiveorStillplus a non-color icon; - while Live, its accessible action name is
Turn diagram motion off; - while Still, its accessible action name is
Turn diagram motion on; - the action is reachable before moving diagram content;
- the status is understandable without color, hover, tooltip, or animation;
- it is at least 44 by 44 CSS pixels on a 390px or 320px viewport;
- it remains visible in Presentation Stage;
- it is hidden in embed and print because those surfaces have their own fixed contract;
- it creates no second pause button inside Story, Route, Radar, or a row.
The existing Story Play/Pause remains the control for progression. The Governor controls permission to move.
4. Owner replacement
claim(name, cleanup) must:
- stop and clean the previous transient owner before publishing the new owner;
- increment the token;
- call the old cleanup at most once;
- never let an old timer/event clear a newer owner;
- pause all ambient motion whenever the owner is not
ambient; - deny visible animation when the effective mode is Still while still allowing the semantic operation to complete instantly.
release(token) returns to ambient only when:
- the token still matches;
- the document is visible;
- effective mode is Live;
- no durable reader state such as active Story/focus/route/lens still owns the scene.
Otherwise it resolves to none with a complete static diagram state.
5. Motion classification
| Current surface | Governor treatment |
|---|---|
header .pulse-dot |
ambient only; static visible dot in Still |
| Signal Flow scan | ambient only; absent in Still and under every reader owner |
| authored trace edge/node | ambient only; complete authored graph remains visible when stopped |
| Radar live dot | Radar owner only; static status mark in Still |
| Story progress, beats, flow, share cue | Story owner only; existing pause freezes semantic beat, not a meaningless partial overlay |
| Semantic Camera | subordinate to the current semantic owner; zero duration in Still |
| Route Probe flow | Route owner; change the signal to one finite pass, then preserve the static exact route |
| Intent Trace | finite Intent owner; release on animation end/cancel/exit |
| Semantic Flow | finite Lens owner; density guard unchanged |
| Relationship Pulse | finite Relationship owner; existing cleanup unchanged |
| Legend preview | Legend owner only while preview is active; no moving flow until explicit Lens activation |
| panel entrance transitions / smooth scroll | allowed only in Live; instant in Still |
No original edge, marker, label, node, route, or camera coordinate is hidden or mutated when motion stops.
6. Guided Views and chapter switching
The active Guided View should own the scene even while its playback is paused:
- selecting a chapter claims
storybefore focus/camera/trail updates; - ambient trace, Signal Flow scan, header pulse, and unrelated preview motion stop before the chapter becomes current;
- the current Semantic Camera transition is subordinate to
story, not a competing owner; - Story Trail and all selected nodes/relationships remain statically readable in Still;
- Play animates only Story progress, beats, and exact Story flow;
- focusing the Named Chapter Rail pauses progression but keeps the Story owner and static selected chapter;
- changing chapters replaces the Story instance atomically; the old beat timer, progress animation, and overlay cannot survive;
- Show all or Escape releases Story. Ambient motion may return only if the reader's effective mode is Live;
- switching Still during playback pauses at the exact current semantic beat and never auto-resumes when Live is restored;
- switching Live while a chapter is selected does not start Play. It only makes the explicit Play action available again.
This makes chapter direction easier to read without adding a new transition: only the current authored Story can move.
7. Reduced motion and lifecycle
- Keep the CSS
@media (prefers-reduced-motion: reduce)block as a no-JS safety net. - Add
.pulse-dotand every missing ambient/entrance selector to that fallback. - Centralize one live
matchMedialistener in the Governor. - A change to
reducecancels camera easing, smooth scroll, Story timers, finite overlays, route flow, ambient trace, scan, and status pulses atomically. - The selected nodes, exact route, Lens receipt, current Story beat, rail state, Passport, labels, and accessible names remain.
document.hiddensuspends all motion and pauses Story.- Returning visible never replays a completed/cancelled one-shot and never restarts a reader-paused Story. Ambient may return only in Live with no stronger owner.
- A Still state must never be implemented by making content
display:nonewhen that content carries semantic meaning.
8. Mobile and touch
- The toolbar may wrap, but no control may overlap the Named Chapter Rail, diagram navigation, or horizontal reading surface.
- The Live/Still hit target is at least 44 by 44 CSS pixels.
- Still uses
behavior: "auto"for chapter centering, Radar recentering, and contained wide-diagram reveal. - Touch chapter activation remains one tap. It does not require hover preview or a second tap to stop motion.
- Motion state does not change page width, SVG width, mobile 720px reading surface, or scroll position.
- A manual swipe, pan, pinch, or zoom cancels the current camera motion and pauses Story as today; it must not restart ambient over the reader's gesture.
9. Embed, print, and export
Embed
- Ordinary
?embed=1is still by default. - The control is absent because the host owns surrounding interaction.
?embed=1&play=1#view=<id>permits only the bounded Story owner; trace, scan, pulse, Radar, route, and preview motion remain off.- Reduced motion turns that one-shot into the current complete static chapter
and
StillShare Chapter Cue state. - Embed introduces no global keyboard shortcut and cannot capture a parent page's keys.
- Print always shows the full, undimmed, complete diagram.
- No Live/Still control, root motion state, owner state, runtime overlay, transition, or animation appears.
Canonical SVG and raster
data-motionanddata-motion-ownerstay on HTML, never on canonical SVG.- SVG serialization strips any transient owner/overlay state exactly as today.
- The exported SVG retains authored
meta.animation="trace"semantics; a viewer-only Still preference does not silently rewrite source intent. - PNG/JPEG/WebP/copy remain canonical full-diagram exports and contain no viewer control or state.
- Export during a Story, owner replacement, Still transition, or cancelled overlay must keep the canonical-state receipt true.
WebM
- Preserve the existing explicit
Download WebM — 6s motionaction andArchify.motionAPI. - Recording is an explicit export request, not ambient viewer playback; the Governor must not rename, corrupt, or serialize itself into the recording.
- A reader in Still does not need to watch live canvas motion in order to produce the offscreen explicit export.
Borrow now / later / skip
Borrow now
- WAI's single top-of-page control for all automatic movement.
- One effective Live/Still state initialized before paint.
- One tokenized owner with reset-before-run cleanup.
- Story as the sole motion owner while any named chapter is active.
- Ambient trace/scan/pulse only when no reader question owns the scene.
- A finite Route Probe signal followed by a complete static result.
- Dynamic reduced-motion and visibility response.
- Static semantic completion for every operation.
- Existing stable geometry, bounded camera, embed, print, and export boundaries.
Borrow later, after this slice is verified
- Shared-anchor Chapter Handoff. Choose the closest stable ID in
previous.focus ∩ next.focus, preserve its initial screen position, then settle through the existing Semantic Camera. If no shared ID or truthful boundary exists, cut directly; never invent a connector. - A compact
02 → 03 · via Gatewaytransition receipt derived from existing chapter and node labels, not a persistent new panel. - Live Semantic Radar viewport feedback during a chapter handoff only when the reader already opened Radar; never auto-open it, especially on mobile.
- A 180–360ms distance-capped transition once the Governor can make it the only moving surface.
Deliberately skip
- No new animation DSL, keyframe schema, motion field, or chapter-transition IR.
- No Web Animations library, React, XState, graph runtime, Mapbox, reveal.js, or LikeC4 dependency.
- No moving/re-laying out graph nodes, edges, labels, lanes, containers, or boundaries.
- No dramatic fly arc, parallax, spring physics, zoom tunnel, cross-canvas wipe, or full-diagram blur.
- No automatic chapter activation from scroll position.
- No infinite reader-triggered Route, Intent, Lens, Relationship, or chapter handoff loop.
- No per-feature collection of Pause buttons.
- No hidden preference that only honors OS reduced motion; ordinary readers also get the visible Still control.
- No mutation of canonical SVG to reflect transient viewer preference.
- No automatic restart of a paused Story or one-shot when visibility or motion preference changes.
Concrete acceptance criteria
State and control
- Every generated HTML artifact contains exactly one native Live/Still button in the top toolbar.
- Live and Still use both visible text and a non-color visual cue.
- The button's accessible name describes the action that activation will take.
- Keyboard Enter and Space produce the same single toggle as pointer/touch.
- The control is available before the moving diagram content in document order.
- No renderer, guided panel, route row, Radar, or preview adds a duplicate motion toggle.
- The root exposes exactly one effective
data-motionvalue and at most onedata-motion-ownervalue. Archify.motionGovernorexists without replacing or renamingArchify.motionWebM methods.
Owner arbitration and cleanup
- At most one owner token is current at any instant.
- Claiming a new owner invokes the preceding transient cleanup at most once.
- A stale timeout,
animationend,animationcancel, promise, orrequestAnimationFramecallback cannot release a newer owner. - Ambient header pulse, Signal Flow scan, trace edges, and trace nodes run only
in Live with
ambientownership. - Any Story/focus/route/lens/intent/relationship/legend owner suppresses all ambient motion before its own visible effect begins.
- Releasing the final reader owner restores ambient only in visible Live mode.
- Still mode resolves every claim to a complete static semantic state without starting visible motion.
- Repeated owner replacement leaves zero duplicate runtime overlays, timers, progress animations, or moving classes.
Guided Views and direction
- Selecting any Named Chapter Rail item claims Story before camera/focus/trail state updates.
- A selected but paused chapter keeps ambient trace, scan, and header pulse still.
- Story Play animates only the current Story progress, beat nodes, reached relationships, and exact Story flow.
- Manual chapter change clears the old beat timer, progress state, and Story overlay before the new chapter becomes current.
- Focusing the chapter rail pauses playback but keeps the selected chapter's complete static semantic state.
- Switching to Still during playback freezes the truthful current beat and accessible status, and does not jump to Show all or another chapter.
- Switching back to Live never auto-resumes playback; Play remains explicit.
- Show all and Escape release Story; ambient returns only when Live.
- Existing Prev/Next,
[,], hash restoration, Share Cue, Presentation, Story Trail, and Named Chapter Rail behavior stay functional.
Motion inventory
.pulse-dotis static under OS reduced motion and reader-selected Still.- Signal Flow scan, authored trace edges, and authored trace nodes are absent or reset to their complete static base in Still.
- Route Probe motion completes one finite pass under five seconds and leaves the exact directed route readable without an infinite animation.
- Intent Trace, Semantic Flow, and Relationship Pulse retain their existing finite direction, density, and cleanup contracts.
- Camera transforms and smooth scroll resolve immediately in Still while final framing/scroll position remains correct.
- Panel entrance transitions add no motion in Still.
- No Still treatment hides semantic nodes, edges, labels, route receipts, Passport facts, Story stops, or Lens counts.
Preference and lifecycle
- Initial OS
prefers-reduced-motion: reducereaches Still before the first visible animated frame. - A live media-query change to
reduceatomically stops ambient motion, pauses Story, cancels camera motion, and cleans finite overlays. - Returning to
no-preferencedoes not restart a paused Story or completed one-shot automatically. document.hiddensuspends every viewer motion source, not only Story timers.- Returning visible restores only permitted ambient Live state; deliberate effects require a new reader action.
- The no-JS CSS reduced-motion fallback still produces a complete static artifact.
Mobile, embed, print, and export
- At 390px and 320px, the control target is at least 44 by 44 CSS pixels and does not overlap the rail, nav, diagram, or export control.
- Still chapter centering and contained-wide reveal use immediate scroll and preserve zero page-level horizontal overflow.
- Touch activation has full parity and never requires hover or a second tap.
- Ordinary embed starts still, shows no Governor control, and has zero ambient trace/scan/pulse motion.
embed=1&play=1permits only the bounded Story owner; reduced motion produces the truthful complete static chapter.- Print contains the complete graph and no Governor control, owner attribute, moving overlay, or dimmed viewer state.
- SVG export during every mode/owner transition keeps the canonical-state receipt true and contains no Governor state.
- PNG, JPEG, WebP, copied PNG, and standalone SVG remain non-empty and deterministic under Live and Still.
- Explicit WebM recording remains available for trace artifacts through the
existing
Archify.motionAPI and contains no Governor UI/state. - Embed, print, canonical SVG, raster output, schema, validators, renderer geometry, stable IDs, and package dependencies are unchanged in meaning.
Verification surface
- Focused tests enumerate every moving selector so a new
infiniteanimation cannot bypass the Governor silently. - Contract tests cover owner token replacement, stale callback rejection, Story takeover, Still mid-play, no auto-resume, visibility, live media-query changes, embed, print, and canonical export.
- In-app browser validation covers a Signal Flow + trace Workflow artifact, a non-Signal-Flow trace artifact, and one Architecture or Lifecycle artifact.
- Browser validation covers desktop, 390px, 320px, dark/light, Live/Still, Story playback, chapter switch, route result, Presentation Stage, embed, export during motion, and zero console errors.
- A final screenshot shows one active named Story chapter with its exact flow as the only moving explanation and a visible Live/Still status.
- The complete unit suite, Proof Lab, ZIP doctor/demo/check, generation
freshness, and
git diff --checkremain green.
Decision
Round 29 should implement Motion Governor: Live/Still + one motion owner.
The project has already earned rich interaction: named chapters, semantic camera, Story Trail, Story Beats, route signals, relationship pulses, ambient trace, multiple presets, and exportable motion. The highest-value next step is not to add another independently attractive effect. It is to make the whole artifact behave like one designed instrument.
The success test is simple: a reader should always know why something is moving. If a Story is playing, only the Story moves. If a route is answering, only the route moves. If the reader selects Still, nothing moves and nothing meaningful is lost.
After that invariant is proven, the shared-anchor Chapter Handoff becomes a strong Round 30 candidate rather than another source of visual competition.