Power Forensics documentation

• Session-based measurement

  Measurements belong to a session with a defined scope and conditions, so results are tied to the experiment that produced them rather than floating free.

• Controlled comparisons

  Compare sessions against each other on shared terms to separate a real change in behaviour from noise in the conditions.

• Power attribution

  Relate observed power behaviour to the system activity that accompanied it, so consumption can be traced back to causes.

• Telemetry capture

  Collect the underlying telemetry a session depends on, and keep it associated with the session rather than discarding it after a live view.

• Experimental workflows

  Structure investigation as repeatable experiments, including the configuration and conditions a run was carried out under.

• Measurement provenance

  Keep track of how a value was produced, so measured, derived and estimated values are never presented as interchangeable.

• Analysis and reports

  Turn a set of sessions into an analysable and shareable result that carries its own context and provenance.

• Power Forensics performs local analysis. Telemetry captured by a session stays on the machine; data leaves the machine only when you explicitly export a session or report.
• Attribution relates observed power behaviour to concurrent system activity. It is an analysis aid, not proof of causation; attributed results should be treated as hypotheses to test.
• It is a measurement and investigation tool. It does not promise a fixed improvement or a specific battery-life outcome.
• Because it is pre-alpha, sessions, file formats and workflows may change between builds without migration support.

• Pre-alpha: expect bugs, incomplete behaviour and breaking changes.
• No public binary has been published yet; the source is available.

Local analysis. Telemetry captured by a session stays on the machine unless an export is explicitly produced. See the privacy page for the website and product summary.

Bugs and security reports are handled through the reporting page.

Installation, first-run and troubleshooting documentation will ship with the first public release.