How a Storyroom experience works
The interaction model
is one act. Watching.
A Storyroom experience does not need to stop and ask the audience which branch to choose. It can read the way the audience is already interacting and let that evidence shape what happens next.
A narrow signal layer.
A wide creative space.
Storyroom normalizes observations from the configured sensing provider. The story decides what those observations mean in context.
- 01
Attention
Where attention appears to stay, drift, or recover during an authored observation window.
- 02
Stillness
Movement and held posture as observable interaction signals, when the active sensing provider supports them.
- 03
Expression
Visible movement such as a smile or brow change. Evidence for the story to interpret, not an emotion diagnosis.
- 04
Avoidance
Looking away or leaving the frame at a moment the creative team has chosen to observe.
A story built as
a decision graph.
Each scene is a node. Selection policies connect the nodes. Audience state determines which eligible edge is taken next.
- PacingHow long a moment rests before the experience advances.
- EditsWhich authored or generated treatment fulfills the next narrative intent.
- DialogueWhich line, performance, or realtime exchange appears next.
- Scene pathsWhich node the experience moves to after the current state is evaluated.
- EndingsWhich consequences, returns, or withheld material close the experience.
The audience gets a film.
The creative team gets a builder.
Storyroom is also a storyboarding environment. A creative team can duplicate a graph, change selection policies, move observation windows, recast characters, compare variants, and preview the same story against synthetic audience traces.
Narrative roles stay stable while cast profiles can swap personas, voices, visual characters, and provider bindings without rewriting the graph.
Open the studio chassisKeep the story logic portable.
- 01We do not treat observable behavior as proof of internal emotion.
- 02We do not make the scene graph depend on one sensing or content provider.
- 03We do not make a character identical to a vendor-specific voice, avatar, or replica ID.
- 04We do not require a production backend, CDN, or generative provider to author and test the graph chassis.
- 05We do not hide material provider-processing differences behind generic privacy copy.
Consent should match
the active provider.
A Storyroom deployment may use local sensing or a configured third-party provider. The screening should disclose where material processing occurs, whether media leaves the device, and relevant retention behavior before permission is requested.
When the story supports it, declining sensing should lead to a non-reactive or alternative path rather than a broken experience.
Read the privacy notes