The proof object

A Power Event Record, shown — and verifiable

Every page on this site talks about the Power Event Record. Here is a real, sanitized one. See the four questions it answers, the measured power deltas, and the hash-chain entry — then recompute the chain yourself, in your browser, with no key and nothing to trust.

One action · one record

It answers four questions about a single power action

Device gpu-node-07:b200:3 · SET_POWER_LIMIT · committed 2026-06-14T09:14:02Z.

Approved
Authorized by policy pol-fac-curtail-007 under FACILITY_DR_WINDOW, tied to the originating utility DR signal — not an ad-hoc change.
Safe
Requested 350W, enforced 300W, hardware readback 300W — drift 0W. The limit the hardware actually applied matches what was authorized.
Auditable
Sequence 14820 on an append-only, SHA-256 hash-chained ledger (ARIV). Its position is fixed by the chain; any edit is detectable — see below.
Financially real
Measured at the meter, not estimated: 949W → 581W per GPU. The number a CFO would book is the number the chain holds.
38.8%
Measured power delta
93.9%
Utilization before
95.7%
Utilization after
SHA-256
Chain integrity
Before
949 W
After
581 W
↓ 38.8% measured power delta · utilization 93.9% → 95.7% held

These deltas are validation evidence from a single short A/B run — not a guaranteed savings figure. How we measured this →

Verify it yourself

Don't trust us — recompute the chain

The chain entry is entry_hash = SHA-256( canonical_json(record) ‖ prev_hash ). Pick a scenario, hit verify, and your browser recomputes the hash with the Web Crypto API. It runs entirely on your machine — no key, no server.



      
prev_hash

      
entry_hash (claimed)

      
SHA-256 (recomputed)— press verify —


      

        
        
        Download raw JSON ↓
      

      

      
Canonical JSON = object keys sorted ascending, no whitespace, UTF-8. The same five lines work offline:

      
$ node -e '
  const c=require("crypto"), p=require("./per-sample.json");
  const rec=JSON.stringify(p.record, Object.keys(p.record).sort());
  const h=c.createHash("sha256").update(rec+p.prev_hash).digest("hex");
  console.log(h===p.entry_hash ? "VERIFIED" : "BROKEN");'

    


    

    
Build your own

    
Make a record from your own numbers

    
Enter a power action — or paste a telemetry export — and your browser seals it into a Power Event Record and recomputes the chain, live. Nothing is sent anywhere.


    

      

        
        
        
        
        
        
      

      

        …or paste a telemetry JSON export
        
        
      


      

        
        
      


      
      
      


      
Constructed in your browser from the numbers you entered. This demonstrates the PER format and the SHA-256 chain — it is not a Spark-XC measurement. A real PER carries telemetry Spark-XC captured and validated on hardware.

    


    

      
Want one of these built from your environment?

      Request a Power Event Replay →