2026-03-15 - Sensor Payloads Do Not Use Location

Date: 2026-03-15
Decision: Hardware sensor payloads (sensors.fans, sensors.power, sensors.temperatures, sensors.other) must not include location. Sensor identity is limited to (sensor_type, name).
Context: In Reanimator, location / slot is meaningful for component installation state and movement checks. Sensor ingest is a last-known-value projection and does not participate in installation tracking, so a location field creates false semantics and encourages integrators to send misleading coordinates.
Consequences: The external hardware ingest contract must remove location from all sensor sections and examples. Integrators should send only the sensor name plus measured values/status. Any future need to relate a reading to a component must be modeled explicitly, not via free-form sensor location strings.
Supersedes: Implicit optional location in sensor sections of bible-local/docs/hardware-ingest-contract.md.