Open questions

Decisions the specification has not made yet, recorded so they're made deliberately.

This page records decisions still open in the v0 specification. Each will be resolved through a written design decision before v1.

Scope#

v1 intent set. Ship all ten intents in v1, or start with the core six (acknowledge, follow, release, reveal, conceal, navigate) and add the rest after real-world use?
Scroll as interaction vs. timeline. Is scroll-linked motion an interaction that owns values (consistent with the model) or a separate timeline concept (consistent with the platform)? The current draft treats scroll as an input family; the boundary needs testing.
Multi-pointer gestures. Pinch and rotate are listed as input families but their projection and resistance rules aren't yet specified.

Distance-aware tempo. The sub-linear rule is stated but not quantified. Calibrate against prototypes.
Exact token values. All tempo and character values are v0 defaults pending perceptual testing.
Haptics and sound. Apple pairs motion with haptics; the web's support is limited. Should intents define an optional non-visual feedback channel now, or later?
Theming character. Should an application be able to shift its whole character scale (a playful consumer app vs. a dense finance tool), and if so, within what bounds?

Validation. How will intent defaults be validated — user testing, side-by-side review against platform-native behavior, or both?
Governance. Process for proposing new intents and changing normative rules once the project has outside contributors.
Versioning the spec. Normative changes to principles should be rare and versioned independently of implementation releases.