01
Capture
Signals are collected as they occur, with the identity of the source and the time they were observed. Nothing downstream should infer what was measured.
Overview
Observation as the current field, not last cycle’s log.
P1-Telemetry is the observation layer of the Intelligence OS. It collects signals as they occur, sequences them, and delivers them to the systems that reason over them. The result is a field that is always the current one, not a dump consulted after the decision has already been made.
CURRENT RESULTS ARE A BASELINE, NOT AN UPPER BOUND.
The field, not the archive.
Most instrumentation stores a log. Telemetry treats each observation as a live input to the next cycle. A measurement that arrives after the decision has been issued is an audit trail. A measurement that arrives in time is a field the rest of the stack can act on.
An institution is not one sensor problem. It is a composition of signals with different cadence, identity, and error. Telemetry is built around that structure. Where a logger ends, Telemetry begins.
In practice
In practice
02
Sequence
Observations are ordered and de-duplicated before they are consumed. The field Chaos and Tempo see is the field as sequenced, not the raw firehose.
03
Delivery
The current field is delivered to the systems that reason over it. Calibration, forecast, score, and control all consume the same observation layer.
Position in the Principia stack
Telemetry as an Intelligence OS application
Telemetry is how the Intelligence OS sees. Capture, sequence, and delivery are the Functions that turn instrumentation into a governed field. Chaos, Tempo, 314, and Maritimo consume observations that were collected here, ordered here, and issued under the same identity. Outputs are traceable to the signal, the sequence, and the cycle that delivered them.
Next
Talk to P1 Telemetry
Tell us which signals you already collect. We will come back on the observation layer they belong to.