---
name: baucon-space-time
description: Design and prototype Baucon spatial layers, alternate projections, and state changes over time. Use when depth or timing conveys a relationship in a Baucon project.
---

# Compose space and time

Read the [Baucon Design Baseline](../../DESIGN-BASELINE.md) for the current projection, layer, annotation, and motion defaults before sketching a study.

Name the relationship first: for example, selection overlays evidence, which refers to a fixed context. Give each plane one role. Use overlap or measured separation to show the relationship and pair it with text or a keyed flat view. Keep controls and readable labels out of transformed planes unless the task requires otherwise. Never imply physical altitude or certainty through a purely visual offset.

Describe event time and interface time separately. Specify the trigger, immediate semantic change, optional visual phases, interruption, and final resting state. Treat 120/440/560 ms as one SOFO reference sequence; see [kit tokens](../../tokens.json). Use intentional playback, a pause control, and a deterministic scrub path when demonstrating time. Provide a still view or frame sequence for e-ink and print. Respect reduced motion and keep state reachable with a keyboard.

Prototype the smallest scene that proves the relationship. Verify the flat equivalent, reduced-motion end state, repeated input, and a narrow layout. Mark new timing or depth grammar as a proposal.