Spine Doctor

Mission

Build this

An OLED and semaphore that track expected publication intervals from selected devices.

Bill of materials

Parts

Disconnect USB before rewiring. Motors, the relay, and the servo need appropriate power and a shared ground. Never drive an actuator from the ESP32 3V3 pin.

Assembly

Build in evidence-producing steps

1. Prove the connection first. Flash the unmodified first-message example with this charter’s zone, device type, and device ID.

   done when: sd-01 is alive on the developer view.

2. Bench-test one input. Read the sensor or control in Serial Monitor before publishing or moving an actuator.

   done when: repeated physical conditions produce repeatable raw readings.

3. Publish one registered measurement. Use the exact measurement and unit below.

   done when: the reading appears without a reject.

4. Add the physical response. Keep spine.loop() running and avoid blocking delays.

   done when: repeated movement does not interrupt publishing or reset the board.

5. Run the investigation. Collect the planned trials before tuning the final logic.

   done when: the build log contains observations, method, and a limitation.

Contract

Your topics

Read another team

Physical behaviour

Alive

Raise the flag only when a device misses its own expected interval.

Your call: Model different expected intervals rather than using one arbitrary timeout.

Engineering evidence

Evaluate false alarms, detection delay, and recovery through controlled disconnects.

1. Define expected intervals for a small monitored set.
2. Run planned short and long outages.
3. Report detection delay and false positives.

If you are fast: Compare the physical monitor with `/api/health` and explain disagreements.

Acceptance

Ready when all six are true

• The registered device is alive and publishing its required topics.
• The reject feed is clear after the final firmware starts.
• The device reads at least one declared cross-team topic.
• A physical output responds to real data without blocking MQTT.
• The build log contains method, evidence, uncertainty, and a known limitation.
• The enclosure exposes no unsafe wiring and the device ID can be scanned.