CLAUDE.md

1# RuView harness — agent operating notes
2 
3You are operating **RuView** (WiFi-DensePose), a camera-free WiFi-CSI sensing system.
4 
5## The one rule: prove everything
6 
7This project was accused of AI-slop; the fix is hard discipline. Before you quote ANY
8accuracy number:
9 
101. It must be tagged **MEASURED** (with a reproducer named), **CLAIMED**, or **SYNTHETIC**.
112. Pose PCK is quoted only as a **delta over the mean-pose baseline** on a leakage-free
12   held-out split; that baseline can otherwise make an unusable model look strong.
133. Run `ruview_claim_check` on any report/PR/model-card. It flags untagged numbers and
14   the project's retracted perfect-accuracy framing.
154. Firmware is "hardware-validated" only with a captured **boot log on real silicon** —
16   never on a build-passes signal.
17 
18## Tools
19 
20`ruview_onboard`, `ruview_claim_check`, `ruview_verify`, `ruview_node_monitor`,
21`ruview_calibrate`, `ruview_node_flash`, `ruview_guidance`,
22`ruview_memory_search`. Start unfamiliar work with `ruview_guidance`; its
23capability status, source paths, validation commands, and limitations are
24navigation evidence, not authority. All tools fail closed. Mutating/hardware
25tools (`node_flash`) require explicit confirmation and are Windows/ESP-IDF
26gated.
27 
28## Skills
29 
30`onboard` · `provision-node` · `calibrate-room` · `train-pose` · `verify`
31(`npx @ruvnet/ruview skill <name>`).
32 
33## Don'ts
34 
35- Don't present WiFi sensing as camera-grade.
36- Don't echo or commit WiFi passwords / secrets.
37- Don't merge or release firmware without a real boot log.
38- Don't report a PCK without its mean-pose baseline.
39