Skip to research
Vraelis Research
All researchVraelis Imprint / Reference note and proposed protocol

Replay and live input

Separate reproducible recorded inputs from interactions with a changing external system.

Research note · November 14, 2026

Research question

Which conclusions survive when a recorded trace is substituted for a live device?

Method

  1. Record a bounded input trace with timestamps, units and source identity. Replay it into a deterministic fixture while preserving the original timing policy.
  2. Compare the replay with a live-input run and list what the replay omits, such as feedback from commands to the device or changes in the surrounding environment.
  3. Label the source mode in every run. A replayed sensor trace should not be presented as a newly observed device response, even when the user interface looks identical.

Records to retain

  • Trace source and capture interval
  • Replay timing policy
  • Live versus replay mode
  • Feedback paths excluded by replay

Source basis

W3C PROV provides a vocabulary for derivation, and ROS clock design describes simulated time behavior. Both support keeping a replay artifact distinct from the original activity that produced its measurements.

Interpretation & limits

Open-loop replay cannot establish closed-loop behavior when the tested controller would change the future inputs. This is a proposed experiment design, not a connected-device capability claim.

Next experiments

  • Identify one feedback path that replay removes.
  • Keep separate result tables for live and replayed cases.

References

  1. W3C PROV overview
  2. ROS clock and time design

Technical reference

Implementation details supporting this note, drawn directly from the maintained documentation. These are technical references, not additional papers or new experimental results. Expand a topic to inspect its method, fields and limits.

Related notes