Wall-clock timestamper. On each tick it reads the host wall clock and emits a nanosecond-precision UInt64 Unix timestamp alongside the forwarded t input, both locked to the same tick so the stamp and the value stay aligned downstream.
Typical backends
Detections are timestamped as they arrive so each event can be ordered and windowed downstream.
Transcript segments are stamped with arrival time before being serialized for log-style storage.
Caveats
- AccuracyThe reading is the host wall-clock at the moment this component processes the tick, not when upstream produced the message; network hops and back-pressure shift the value later than the true event time.
- Hard constraintWall-clock time can jump backwards on NTP corrections, so the stamp is not monotonic; consumers that need strictly increasing time must derive a monotonic clock themselves.
- I/O contractBoth outputs fire exactly once per input tick with their cadences locked; a consumer that drains only one side will stall the other through back-pressure.