Testing and Verification Methodology

What was reviewed and how future measurements should be documented.

Current status

Developer and processor documentation were reviewed on 2026-10-05. No hands-on Windows test, performance benchmark, digital-signature verification, malware scan or hash verification of the FileDrop payload was carried out for this edition. Earlier statements that procedures were tested on Windows 10 and Windows 11 lacked supplied evidence and have been corrected.

Protocol for future measurements

1. Record the CPU and system model, Windows build, software version and package source.
2. Verify package provenance, signature where present and the appropriate independently sourced hash. Keep the results.
3. Record cooling configuration, ambient conditions when measured, power mode, sensor label, units and sample interval.
4. Define the ordinary workload and session length before collecting observations.
5. Keep original logs, gaps, screenshots, completed work and symptoms.
6. Repeat matched sessions and report changed conditions and uncertainty.
7. Publish actual results only after testing. Never present a worksheet or illustrative example as a measured result.

Stop a task if abnormal operation suggests a fault. Do not defeat operating-system security or thermal protections to complete a demonstration.