- explicit verification boundary;
- conformance tiers;
- threat-model framing;
- candidate flexible-load / curtailment-provenance extension;
- document stratification and semantic-versioning governance.
v0.0.2 / Specification-Hardening Update / Candidate Specification / Pre-TRL-7 Validation
A candidate specification for certified BESS operational evidence.
ONEDGE ENERGY v0.0.2 hardens the proposed open standard into a more precise public specification: verification boundaries, conformance tiers, threat-model framing, semantic-versioning governance, and a candidate extension for flexible-load and curtailment-provenance certification.
01 / Abstract
Certified coordination is the next bottleneck.
Renewable-heavy power systems are entering a battery-intensive phase where the bottleneck is no longer only generation, but certified coordination of flexibility assets under physical, financial, regulatory, operational, and warranty constraints.
ONEDGE ENERGY, powered by IKKUNA's ECME Kernel, is presented as a proposed open standard and candidate specification for BESS operational evidence. Its central object is the Golden Record: a cryptographically committed operational evidence object that classifies each certified event as Compliant, Breach, or Opacity.
Open standard at the interface. Sovereign proof authority at the core.
02 / v0.0.2 Delta
From public whitepaper to specification discipline.
Version v0.0.2 supersedes v0.0.1 and introduces stricter candidate-standard controls. The landing page should now foreground the document as a specification-hardening update, not merely a strategic introduction.
v0.0.2 remains pre-TRL-7. It does not claim industry adoption, financial guarantees, OEM acceptance, regulatory approval, CEN endorsement, EPRI endorsement, or final standard status.
03 / System Problem
System dispatch and asset warranties require a shared evidence object.
The CEN coordinates Chile's SEN according to system-level objectives such as security, continuity, economic dispatch, and open access. That mandate is not designed to become the warranty arbiter, lender diligence agent, telemetry-provenance authority, or asset-degradation certifier for every BESS.
A dispatch instruction can be systemically correct and still create asset-level warranty, degradation, lender-legibility, or telemetry-provenance ambiguity.
04 / Golden Record
Prove compliance, prove breach, or flag opacity.
The Golden Record turns operational behavior into certified evidence by binding asset state, dispatch context, telemetry provenance, operating-envelope constraints, state-transition logic, and verification artifacts into an auditable record.
Compliant
Approved telemetry is available and the asset respected its declared physical, operational, warranty, and contractual envelope.
Breach
Approved telemetry is available and the event operated outside the declared envelope, supporting attribution and warranty-defense logic.
Opacity
Telemetry provenance fails or the evidentiary substrate is incomplete, corrupted, delayed, inconsistent, manipulated, or physically unavailable.
ONEDGE does not manufacture certainty. It classifies the evidentiary state.
05 / Formal Logic
Event-indexed certification logic.
At the certification layer, BESS operation is observed as an endogenous sequence of operational events indexed by k ∈ N. The event index advances only when a new observable state transition occurs.
xₖ₊₁ = Tθ(xₖ, uₖ, yₖ, dₖ)
subject to: g(xₖ, uₖ; θ) ≤ 0
P(yₖ) = 1 if required telemetry is complete, authentic, sequenced,
and derived from approved asset-originated sources;
0 otherwise.
E(xₖ, uₖ; θ) = 1 if g(xₖ, uₖ; θ) ≤ 0;
0 otherwise.
σₖ =
Opacity if P(yₖ) = 0
Compliant if P(yₖ) = 1 and E(xₖ, uₖ; θ) = 1
Breach if P(yₖ) = 1 and E(xₖ, uₖ; θ) = 0
GRₖ = h(xₖ, uₖ, dₖ, yₖ, θ, P(yₖ), E(xₖ,uₖ;θ), σₖ, xₖ₊₁, πₖ, GRₖ₋₁)
A valid Golden Record must satisfy state consistency, constraint evaluation, telemetry provenance, truth classification, and cryptographic integrity.
06 / Boundary
What ONEDGE does — and what it does not do.
- ingest baselined telemetry;
- evaluate declared operating envelopes;
- classify events as Compliant, Breach, or Opacity;
- produce audit-supporting certificates;
- reduce evidentiary ambiguity;
- support lender, OEM, owner, operator, auditor, and regulatory diligence.
- replace CEN or any system operator's dispatch authority;
- replace BMS, SCADA, meters, inverters, sensors, or OEM monitoring hardware;
- create telemetry where hardware telemetry does not exist;
- certify compliance where telemetry provenance fails;
- auto-resolve legal disputes or replace lender diligence;
- guarantee WACC, LTSA, warranty, or degradation outcomes.
07 / Conformance
Incremental adoption through conformance tiers.
v0.0.2 introduces preliminary conformance tiers so an asset owner, OEM, lender, or operator can adopt the standard progressively rather than through a single disruptive integration event.
Observed
Telemetry observed, no certification.
Baselined
Approved asset-originated telemetry sources mapped to requirements.
Classified
Events classified as Compliant, Breach, or Opacity.
Reported
Lender, OEM, owner, and operator reporting formats generated.
Certified
Full Golden Record certification under StandardCo validation.
08 / Threat Model
Refuse to certify defective evidence.
The v0.0.2 threat model explicitly includes missing telemetry, corrupted telemetry, delayed or non-sequenced telemetry, sensor drift, manipulated sensor feeds, BMS / SCADA / meter inconsistencies, data replay, unauthorized schema modification, model drift, false curtailment claims, false compliance claims, false breach accusations, OEM data asymmetry, operator misreporting, dispatch-envelope mismatch, commercial misrepresentation, and attempts to treat opacity as compliance.
The three-state model reduces these threats by refusing to certify compliance where the evidentiary substrate is defective.
09 / Stack
Open interface. Sovereign proof core. Physical asset layer.
Open / Semi-Open Layer
Certificate schema, telemetry categories, provenance requirements, operating-envelope fields, audit interface, API-level submission logic, conformance terminology, governance principles, antitrust-safe access criteria, and reporting categories.
Sovereign IKKUNA Layer
ECME Kernel, deterministic optimization engine, physical state-transition verification, cryptographic proof architecture, Golden Record issuance authority, calibration methodology, certification methodology, reference validator, proof circuits, and StandardCo governance authority.
Physical Asset Layer
BESS asset, BMS, SCADA, inverters, sensors, meters, dispatch orders, operator actions, and asset-originated telemetry sources.
10 / Candidate Extension
Flexible-load and curtailment-provenance certification.
v0.0.2 introduces flexible-load and curtailment-provenance certification only as a Candidate Extension. It is not part of the initial validated BESS warranty-certification claim set.
A flexible load may claim that it operates exclusively, preferentially, or conditionally on curtailed or excess energy. ONEDGE treats that claim as evidentiary: it requires metered energy provenance, dispatch context, authorized system / settlement / metering records, and the same Compliant / Breach / Opacity classification discipline.
ONEDGE classifies evidence against declared inputs. It does not replace system operators, market settlement systems, or applicable regulatory records.
11 / Versioned Governance
Document stratification and semantic versioning.
v0.0.2 introduces specification-level version discipline to prevent silent schema drift during TRL-7 validation and future standard-formation processes.
Standard-facing
Sanitized abstract definitions, public schema language, and candidate-standard posture.
Validation-facing
Architecture, OEM strategy, legal mapping, validation artifacts, lender diligence materials, and certificate samples.
Proof-facing
Proof logic, patentable claims, implementation details, and trade-secret boundaries.
12 / TRL-7 Path
The public specification anchor for the future TRL-7 data room.
This whitepaper is not the Data Room itself. It functions as the public specification anchor. The proposed TRL-7 Data Room should contain private validation evidence, legal scoping materials, OEM / warranty mappings, lender diligence artifacts, telemetry summaries, and certificate samples linked to the applicable v0.0.2 schema.
- Define the certification object: dispatch compliance, warranty support, OEM defense, lender diligence, operator attribution, telemetry provenance, breach record, and opacity-event record.
- Reference deployment: TRL-7 shadow-mode validation on real assets under real conditions.
- Lender and OEM legibility: convert certified evidence into reusable diligence and warranty language.
- Governance file: document that the standard is open at the interface, merit-based, interoperable, non-coercive, and not a foreclosure tool.
- Institutional adoption: build referenceability across banks, OEMs, owners, operators, validators, and standard institutions.
13 / Claims Discipline
Bounded claims for a pre-TRL-7 candidate specification.
- ONEDGE ENERGY is a proposed open standard for certified BESS operational evidence.
- ONEDGE ENERGY is a candidate specification in pre-TRL-7 validation status.
- ONEDGE ENERGY requires baselined telemetry provenance.
- ONEDGE ENERGY can classify certified events as compliant, breached, or opaque.
- ONEDGE ENERGY is designed to reduce evidentiary ambiguity.
- It is not already an adopted industry standard.
- It has not completed TRL-7 validation.
- It does not guarantee lower WACC or LTSA costs.
- It does not guarantee warranty approval or prevent degradation.
- It does not replace CEN dispatch, OEM monitoring systems, or authorized curtailment records.
ONEDGE reduces the scope and ambiguity of disputes by producing verified operational evidence, breach evidence, or opacity evidence.
14 / Public Data Room
Document-first institutional interface.
The landing page should serve as the public specification index for ONEDGE ENERGY v0.0.2. Each artifact should be directly accessible, versioned, dated, and, where appropriate, hash-addressed.
| Document | Status | Version | Purpose |
|---|---|---|---|
| ONEDGE ENERGY Whitepaper | Current public anchor | v0.0.2 | Specification-hardening update and public candidate-standard narrative. |
| Golden Record State Model | Candidate specification | v0.0.2 | Compliant / Breach / Opacity formal classification logic. |
| Verification Boundary Note | Candidate specification | v0.0.2 | Precise statement of what ONEDGE does and does not do. |
| Conformance Tiers | New in v0.0.2 | v0.0.2 | Level 0 to Level 4 adoption path from observed telemetry to full Golden Record certification. |
| Threat Model | New in v0.0.2 | v0.0.2 | Adversarial, operational, and evidentiary failure modes. |
| Flexible-Load / Curtailment-Provenance Extension | Candidate extension | v0.0.2 | Non-core extension for curtailment-powered flexible-load evidence claims. |
| TRL-7 Data Room Index | Preparing | v0.0.2 | Private validation evidence, legal scoping, OEM mappings, lender materials, telemetry summaries, and certificate samples. |
Disclaimer: materials are provided for discussion and validation purposes only and do not constitute legal, financial, investment, regulatory, engineering, tax, or professional advice.