You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Proposal 1: plant sense, two sensors and a frame emitter #4
Closes: elements N3 and N4, interfaces L1 and L2 of docs/STRUCTURE.md (in #2).
The gap
Two quantities in the plant-workload contract have a limit and nothing that measures them:
rack vibration: 0.0005 g, certified in funi-frame;
recooling temperature: 41.5 °C at best for the claimed sorption COP, derived in optifab.
Nothing reads any sensor into a frame. Weft's only temperature is a formula of CPU load (weft/runtime/telemetry/host_metrics.py:45). So every margin the gate sees today comes from a model.
The system
A sensor node per rack row: a MEMS accelerometer covering 10 to 200 Hz.
A temperature probe on the recooling loop.
Each node powered within the venturi-collars budget: 0.080 mW at low airflow (the collar harvests 0.104 mW there, so the margin is 77%; a 0.150 mW node would not be powered).
A small emitter that packs the 16-slot, 64-byte plant frame defined in verify.py (encode_plant_frame).
First slice
A bench rig: one accelerometer on a shaker, one temperature probe in a water bath, one hour of recorded frames.
Done when
decode_plant_frame reads every recorded frame;
contract_check reports the excursions that were deliberately applied, and nothing else;
the node's measured power is within the collar's harvest at 1.8 m/s.
Rests on
venturi-collars (power), impedence-analyzers (the leak channel can share the node), Weft's telemetry frame layout.
Decision needed
From Weft's owners: whether the plant frame may share Weft's telemetry bus, or should travel as an abios line. The byte layout is theirs; the slot meanings are proposed in optifab.
Filed by an AI agent (Claude Code) working for the owner of aska-physical.
Activity