# Project roadmap, evidence and outstanding decisions

> Research status updated 20 November 2026. Future regulatory events are not pre-reported as decisions.

## What has been prepared

The research repository includes Ukrainian law and EU reference matrices, the correction required after Law No. 4834-IX, an examination of the supplied 20-page draft amendment to Commercial Metering Code No. 311 and six targeted suggestions. A ten-component architecture specification, bilingual White Paper, governance admission stages G0–G4 and an economic A/B/C comparison have been drafted.

The synthetic prototype demonstrates a permission registry and data-access journey, separate localhost node processes, correction, directory-coordinated authority epochs and selected recovery cases. The landing site uses the owner-selected EDDIE image and the Schema design profile, with previous passing Chromium and automated accessibility checks.

## What remains unverified or incomplete

- The outcome of the NCRECP meeting scheduled for 24 November 2026 and the final text/effective date of any amendment.
- An independent legal opinion on separate access service providers and data rights for an independent aggregator with a third-party BRP.
- A verified public production interface or authorised access to official AKO data.
- Cross-organisation PKI/mTLS, signed evidence, independently operated nodes, partition handling and security audit.
- Measured costs and benefits for a five-year alternatives comparison.
- Legal clearance of the EDDIE UA name/mark vis-à-vis the unrelated EU EDDIE consortium.
- Public consultation intake, data protection notice, published source documents and approval to deploy.

## R0 – Legal and technical research baseline

Reconcile exact clauses, identify real procedural gaps and preserve source timestamps. Exit condition: independently reviewed statement of enacted law, pending drafts and proposals, with no contradictory obsolete versions.

## R1 – Common contracts and external conformance

Describe the six reference journeys P1–P6, independently implement data and permission schemas, publish synthetic fixtures and verify reproducibility by an external engineer without hidden exceptions.

## R2 – Operational safety and independent security

Independent nodes, key ownership, certificate lifecycle, mTLS, replay protection, partition and crash injection, documented recovery, external vulnerability testing and a threat model accepted by qualified reviewers.

## R3 – Lawful, limited pilot

Agreements and rights confirmed by relevant organisations, limited metering points, specified allowed purpose, audit and termination, data protection and incident escalation. No real customer data before this gate.

## R4 – Economic and regulatory impact decision

Collect observed CAPEX/OPEX, integration costs, availability and harm, and model alternatives A/B/C with conservative/base/optimistic sensitivity. The outcome may favour a central API over federation.

## R5 – Production and institutional readiness

Complete applicable statutory procedures, oversight, qualified audit, service neutrality and operational acceptance. Green CI alone cannot authorise a market system.

## Editorial status policy

Every progress item should disclose the actual event date, publication date, source, responsible reviewer and one of: enacted, proposed, tested, pending, blocked. An anticipated decision never appears as adopted law; a failed test never appears as delivered functionality.


## Why unfinished steps belong in the public record

A research portal becomes marketing when it publishes only achievements. For EDDIE UA the distinctions between a draft document, a passing test, a prototype, a lawful pilot and a production service are essential. Each requires different evidence.

As of 21 November 2026, eddie.wesfin.energy is a publicly accessible research website. That does not make it an official metering administrator, a production DataHub interface or an operating nationwide federation using customer records.

## How the roadmap developed

The work began with interoperability of electricity data access, followed by a legal matrix, an EIC-inspired directory hypothesis, permission workflows, synthetic testing and independently executing localhost node processes. The legal review required an important correction: Law No. 4834-IX already establishes the broad access principle in Ukraine, so implementation procedures rather than duplicated declarations are the immediate policy focus.

The next stages require lawful identity and entitlement evidence, external security testing, independent organisational trust, fault injection, measured economics and an explicit decision about a limited pilot.

## 24 November 2026: a future regulator event

The official NCRECP agenda includes item 29 concerning a proposed amendment to Commercial Metering Code No. 311 under Law No. 4834-IX. **As of 21 November 2026 this meeting has not happened.** Subsequent editorial work must inspect the actual decision, published text, consultation timetable and whether any adopted act has entered into force. Approval of a draft must never be silently relabelled as enacted regulation.

## Evidence required to close a milestone

Legal progress needs current primary texts and independent clause-level verification. Technical progress needs reproducible commits and negative-case tests. Security progress needs a qualified external assessment against a documented threat model. Pilot progress requires agreements, lawful access and incident responsibilities. Economic progress requires observed inputs and equivalent comparisons across alternatives.

A successful GitHub job does not create a legal certificate, and publishing a White Paper does not enact a regulator's decision.

## Learning from Europe without claiming affiliation

We are studying the original European EDDIE project, its open architecture and data-access concept. Its grant, consortium, name and software rights are not automatically transferred to the Ukrainian initiative. Our [European EDDIE history and naming explanation](?page=european-eddie) documents the distinction and the need for separate brand clearance.


## Related material

- [Legal detail](?page=regulatory)
- [Knowledge library](?page=library)
- [Participation](?page=participate)
