Skip to content
Spacetime
← HCI Explorations

HCI / 08 / Initial protocol

Storyboard Experiments.

Can failure-mode storyboards expose missing interaction states before implementation?

Registered 11 September 2026Spacetime Research / version 1

Interactive prototype / synthetic state

Inspect the uncertainty.

Illustrative · not navigation
Synthetic route uncertainty envelopeThe shaded ellipse shows an assumed 95 percent positional radius, against a plus or minus 20 meter illustrative corridor. Adjust the controls below.SYNTHETIC / LOCAL FRAME / METERSTOP-DOWN · ±20 m LATERAL CORRIDOR
Illustrative envelope within corridor95% radius · 7.3 m
Accuracy
Not measured
Integrity
Not evaluated
Confidence
95% assumed model
Latency / age
0 s simulated age
Model, provenance, and limits

This is a deterministic interface test bench, not a sensor feed. For an isotropic 2D Gaussian, the assumed radial coverage is r95 = √(−2 ln 0.05) × σ. The toy scenario uses σ = base uncertainty + age × an illustrative source coefficient. Coefficients are authored test controls, not measured GNSS, visual, or inertial performance. A ±20 m corridor is illustrative. A positional confidence envelope is not an integrity protection level. No safety authority or hardware actuation is granted.

Research record

From question
to evidence.

01 / Question
Can failure-mode storyboards expose missing interaction states before implementation?
02 / Hypothesis
Parallel human, agent, and machine storyboards may reveal authority gaps and misunderstood handoffs earlier.
03 / Method & prototype
Trace nominal operation, anticipation, loss, fallback, recovery, and explanation. Identify who observes, decides, and acts at every transition. The shared synthetic test bench is an interaction prototype; completing the proposed study requires task design, participant recruitment where relevant, and recorded evaluation.
04 / Observation
Evaluation pending. No participant-study results or field-performance findings are reported in this initial protocol.
05 / Measures
Missing transitions, authority ambiguities, inconsistent state, and defects found before coding.
06 / Systems implication
Candidate: use a shared scenario contract before turning a storyboard into a product interaction. Promotion depends on evidence of improvement against the baseline, with failure cases and limitations recorded.