Energy & Utilities · the same standard, extended
The accountability standard, read in energy & utilities.
Operational and compliance records for critical infrastructure that are tamper-evident by construction — provable to a regulator without trusting the operator's own logs. Instantiated for NERC CIP evidence. The eight axes never change; only what they mean here does.
Don't trust us — the integrity of this page is recomputable in your own browser
Patent-pending — U.S. Provisional 63/921,717
For energy & utilities
Who it's for, what it promises, how it's proven.
How it works
From a record to a proof, in four moves.
The mechanism is the same for every record and every access. Nothing here asks you to trust a vendor's word — the last step is something you do yourself.
The record is written
A record (or an edit to one) is committed and bound into an append-only chain — sensitive fields encrypted at the record.
Every access is stamped
Each read or change becomes a WORM event — who, what, when — that nobody can quietly remove or rewrite after the fact.
Access is gated
A person authenticates with a phishing-resistant passkey; access is least-privilege and the access itself is recorded.
You recompute the proof
Open the verifier and recompute the hash yourself. If the record changed, the hash changes — integrity resolves to math, in your browser.
One framework · eight axes
The eight axes — read in energy & utilities.
The canonical axis codes, names, and roles are frozen by the engine and shown unchanged. Only the gloss — what the axis means in energy & utilities — is specific to this domain. No axis is relabeled; no named entity is measured.
PO · Physical & Outdoor
Somatic foundation
Grid & infrastructure resilience — generation, transmission uptime, and the physical reliability of the system.
NM · Nutritional & Metabolic
Somatic foundation
Fuel, capital & resource intake — fuel, capital, and the resources that sustain reliable supply.
ER · Emotional & Relational
Resilience wing
Ratepayer & regulator trust — the relationship with customers and the public-utility commission.
SC · Social & Communal
Spirit term
Interconnection & sector coherence — coordination with the grid, ISOs / RTOs, and the wider sector.
RS · Religious & Spiritual
Resilience wing
Reliability & ethics adherence — fidelity to reliability standards and the duty to keep the system up.
ES · Environmental Stewardship
Environment term
Records & critical-resource stewardship — custody of CIP evidence and stewardship of critical resources.
TA · Technological & Adaptive
Technology term
OT / ICS modernization — control-system security, monitoring tooling, and adaptive infrastructure.
PV · Purposeful & Vocational
Purpose exponent
Authorization & vocational fitness — operating authority, NERC registration, and fitness to operate.
The composite is multiplicative — you can't paper over a missing pillar to lift the score — and the consistency exponent rewards steadiness across all eight. See the canonical eight axes →
Engineered for the rules, not badged against them
How the standard maps to the NERC CIP standards.
We don't ask you to take a certificate on faith — a logo on a page proves nothing you can check. Each obligation maps to a mechanism you can inspect or recompute — the difference between asserting compliance and demonstrating it.
| Obligation | How the standard satisfies it | Status |
|---|---|---|
NERC CIP-007Systems security — logging |
Every access is an append-only, chain-stamped WORM event — who, what, when — that no one can quietly remove. | Built |
NERC CIP-010Configuration change & monitoring |
End-to-end provenance — each step is a chained leaf, so chain-of-custody is reconstructable and tamper-evident from creation onward. | Built |
NERC CIP-011Information protection (BCSI) |
Field-level AES-256-GCM on stored sensitive fields — encrypted at the record, not just the disk. Key custody and rotation are part of the rollout. | Built |
NERC CIP-004 / 005Personnel & electronic access |
Least-privilege access, and every access recorded to the audit chain — enforced and observable, not just configured. | Built |
Integrity of evidenceAuthenticity of the record |
Records bind into a SHA3 hash-chain; any alteration changes the leaf and is detectable. You recompute the hash yourself. | Built |
Audit evidence packagingRegulator-ready CIP evidence set |
A verifiable export — a portable, independently-checkable record of provenance and access that an auditor can re-verify. | Roadmap |
Status is honest. Each row is Built (the mechanism exists in the gold stack) or Roadmap (the Energy / Utilities-specific instantiation is planned). Medicine is the one live, shipped domain today. This maps mechanism to obligation — it is not a claim of certification, because the standard is to prove integrity, not badge it.
Same engine · illustrative archetype
An illustrative energy & utilities archetype, scored by the same engine.
Illustrative profile: a utility with strong operational resilience and stewardship, hardening its OT security and tamper-evident compliance evidence.
These are illustrative inputs — not a measurement of any named entity. Feed them through the same public compute() on The Standard page, change any slider, and recompute it yourself.
What you get
The standard, in your hands.
- The accountability score — your eight axes scored by the public engine, recomputable by anyone.
- The tamper-evident record — records and access history on an append-only chain.
- The in-browser verifier — recompute any record's integrity yourself, no trust required.
- A verifiable export — a portable, independently-checkable account of who-saw-what, when.
- Encrypted data at rest — field-level AES-256-GCM on sensitive fields (rolling in).
- A standard, not a lock-in — the proof is open math you can run even if you leave.
Questions a CIP lead and an OT security officer ask first.
Can this produce regulator-ready NERC CIP audit evidence?
The tamper-evident logging, config-change provenance, and access records are built; packaging them into a CIP evidence set for an audit is roadmap work. Talk to us about your standards in scope.
How does this fit with my OT / ICS and SIEM?
It adds tamper-evident provenance over the evidence your OT/ICS and SIEM already generate, kept off the operational path. Tell us your environment.
If you go away, can we still verify our own evidence?
Yes. Integrity is open math over an append-only chain — independent re-verification does not depend on us.
What's live today versus on the roadmap?
Medicine is the live, shipped anchor. For energy the core mechanisms are Built; the CIP evidence-packaging is Roadmap.
Why one framework covers it
The same formula, the same chain, the same verifier.
Accountability has the same shape in energy & utilities as anywhere else: a foundation, the relationships built on it, the capability to adapt, and the consistency to sustain it. The proof is identical — and it resolves to math, not to our word.
One formula over eight axes
The composite is multiplicative and the consistency exponent rewards steadiness — so you can't fake a missing pillar to lift your standing. The same engine that scores every domain.
One append-only chain
The record — and every access to it — sits on a chain where nobody can quietly rewrite the past. Tamper-evident by construction, not by promise.
One verifier anyone can run
Don't trust us — recompute the chain in your own browser. Every domain runs the exact same proof. Open the verifier →
Looking for another regulated world? The same standard reads in all ten domains. Medicine is the one that is live and shipped today — see the live anchor →