Docs / Telemetry

Telemetry

Milestone telemetry is local and minimal. Snapshots attach to experiments for context. They are never used to invent benchmark scores.

Collected

• Timestamp
• Process-visible CPU usage % (sysinfo)
• Memory used / total
• Coarse load hint (low / moderate / high)

0.2 also expands an environmental noise model so experiments can record context without fabricating sensors.

Not collected (explicitly unsupported)

• Package temperature
• Fan RPM
• Power draw (watts)
• GPU utilization / clocks
• Network identities

Design rules

1. If a sensor is unavailable portably, mark it unsupported — do not invent values.
2. Telemetry never substitutes for KraftBench wall-clock work.
3. Local-first: no cloud upload path in the current product.

Future milestones may add optional sensor backends behind the same honesty rules.