Verifiable BESS evidence across specification, implementation, proof, and governance.

From whitepaper to active specification stack.

Renewable-heavy power systems are entering a battery-intensive phase where the bottleneck is no longer only generation, but evidence-governed coordination of flexibility assets under physical, financial, regulatory, operational, and warranty constraints.

ONEDGE ENERGY remains a proposed open standard and candidate specification. The public surface now reflects the active four-axis version vector rather than only the original whitepaper: the Standard axis defines the Golden Record, the Implementation axis defines SDK/runtime behavior, the Proof axis registers cryptographic primitives, and the Governance axis binds public claims and commercial regimes.

UVS-2 separates four maturity tracks.

As of 2026-07-14, the manifest active vector is UVS-2 / S-0.0.4 / I-1.1.0-rc3 / P-1.0.0 / G-1.4.0. The axes are linked by compatibility rules, but they are not the same artifact.

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.

The Golden Record has one canonical definition.

S-0.0.4 reconciles the prior whitepaper, oracle, SDK, bridge, and governance descriptions into one object: GR := (Commitment, Classification, Provenance, Binding). The Sovereign Operational Certificate is the contractual alias of the same object.

Bit-identical commitments across runtimes.

GRSCHEMA-1.0.0 defines the byte-level canonical schema for event commitments, period aggregation, and verifier-side public inputs. Under P-1.0.0, the canonical commitment hash is Keccak-256 over the canonical byte sequence and transcript label.

S-0.0.4 publishes deterministic GRSCHEMA vectors for Compliant, Breach, and Opacity cases. Module-operator fixtures for phi, psi, and delta remain open in Move 2.

Scope boundary: the current vectors establish canonical encoding and structural equality. Real proof-validity, witness-binding, and adversarial proof vectors remain open under CUR-0014; deterministic hashes alone do not establish those properties.

What ONEDGE does — and what it does not do.

Evidence quality is tiered, not assumed.

The active manifest carries five provenance tiers, τ0 through τ4, aligning observed telemetry, soft signatures, hardware attestation, BMS-TEE silicon roots, and ZK-continuity into explicit minimum evidence thresholds.

Conformance Levels 0 through 4 describe statement maturity, while provenance tiers describe evidence origin and assurance. A Level ℓ claim requires at least provenance tier τ ≥ ℓ; the two scales are aligned but not interchangeable.

TEEATTEST-1.0.0 is normative for telemetry claiming τ ≥ 3. It defines the StandardCo Root → OEM Root → Device Key chain, freshness anchors, revocation, and tier binding.

Withhold compliant classification when evidence is defective.

THREATMTX-1.0.0 maps the original seventeen threats plus two derived threats, opacity-as-compliance and commercial misrepresentation, to concrete mitigation surfaces across provenance tiers, Golden Record schema rules, TEE verification, operator controls, SDK invariants, and governance controls.

rc3 adds deterministic module extensions.

I-1.1.0-rc3 introduces the Module Extension Standard for OEM-specific thermodynamic models without a full Runtime upgrade for each asset variant. Modules remain deterministic RISC-V no_std state-transition units subject to universal Physics Firewall invariants.

Open architecture around a protected proof core.

Governance is now part of the version vector.

S-0.0.4 extends the versioning scheme to UVS-2 by adding the Governance axis. Golden Record events embed a governance binding so the technical record can be attributed to the frozen commercial regime under which it was issued, without changing the ternary classification outcome.

rc3 is active; root release remains ahead.

The next root release target is S-0.1.0 / I-1.1.0. The landing page reflects Move 1 completion while keeping Moves 2 through 4 open.

Bounded claims for a pre-stable candidate stack.

Document-first institutional interface.

This static page indexes the active public-facing specification surfaces. S-0.0.2 remains the base whitepaper and historical standalone anchor; the active S-axis must be read cumulatively through S-0.0.3 and S-0.0.4, with later amendments governing where applicable.

Disclaimer: materials are provided for discussion and validation purposes only and do not constitute legal, financial, investment, regulatory, engineering, tax, or professional advice.