Knowledge Library – White Paper, legal analysis and engineering evidence
Зміст статті / On this page (15)
- The bilingual EDDIE UA White Paper
- Ukrainian regulatory research
- EU rule-to-test matrix
- Architecture and threat model
- Governance and economics
- Prototype evidence
- Publication and version policy
- Public-access limitation
- How to read legal, technical and research evidence responsibly
- A reading route for a non-specialist
- A route for legal and regulatory professionals
- A route for engineers
- The White Paper and its status
- Why public primary links matter
- Primary sources
The bilingual EDDIE UA White Paper
Read the full draft White Paper – the complete research v0.1 reader edition is available here, while independent legal and publication clearance remains pending.
The internal files EDDIE-UA-WHITE-PAPER-UK-v0.1 and EDDIE-UA-WHITE-PAPER-EN-v0.1 cover the research problem, Ukrainian law, European reference procedures, architecture, synthetic evidence, neutral governance, economic comparisons and the route toward a lawful pilot.
The principal argument is that Law No. 4834-IX has already established the broad legal access framework. Research should therefore focus on practical interoperability, legally established rights, transparent procedures, auditability and economic comparison – not on inventing a right that does not exist. Federation remains an option, not a predetermined outcome.
Ukrainian regulatory research
REG-006-UPLOADED-DRAFT-CLAUSE-REVIEW records the examination of the supplied 20-page November 2026 draft amendment to Commercial Metering Code No. 311. REG-006-TARGETED-AMENDMENTS-AFTER-PDF contains six possible procedural improvements, none represented as an adopted law or submitted official comment. UA-CLAUSE-LEVEL-VERIFICATION-2026 records exact clause locations, review status and unresolved gaps.
Every published statement should identify whether it describes an enacted obligation, a published draft, a Wesfin proposal or an unverified interpretation.
EU rule-to-test matrix
EU-2023-1162-CLAUSE-AND-TEST-TRACEABILITY maps Directive 2019/944 and Implementing Regulation 2023/1162 to the six reference procedures, proposed system functions and missing test evidence. Some results are still OPEN. Passing synthetic CI is not a conformity certificate.
Architecture and threat model
ARCH-001-federated-data-platform-technical-spec describes ten proposed logical services, data contracts, safety boundaries and required tests. ARCH-002-threat-model-verification addresses trust between organisations, replay attacks, stale authority, evidence integrity and failure recovery. openapi.synthetic.v0.2.json is an illustrative research contract, not an authorised DataHub interface.
Governance and economics
GOV-001-TRUST-AND-ACCREDITATION describes the proposed G0–G4 admission levels, non-discrimination, conflicts and incidents. ECON-001-RIA-AND-TCO-MODEL and the evidence-input CSV compare central API and federated technical providers without claiming fictional savings.
Prototype evidence
The repository contains Python in-memory and multi-process synthetic federation tests, a browser playground, a localhost integration bridge and CI evidence. It does not contain a certified public API, lawful customer credentials or production settlement authority.
Publication and version policy
Each document requires an identifier, language, owner, revision date, legal-source review date, status, independent reviewers where appropriate, test references, amendments and supersession history. Previous drafts must not silently appear as current law after an amendment.
Public-access limitation
The repository wesfin-group/wesfin-eddie is private. GitHub PR links will not work for most outside visitors. The portal therefore publishes reviewed narrative chapters; full downloadable research documents must be separately approved for release, screened for privacy/security and made available as public copies. We will not display download buttons for unavailable files.
How to read legal, technical and research evidence responsibly
An energy regulation portal has an unusual editorial risk: similar-looking statements can have different legal meanings. A regulator scheduling discussion of a draft, approving a draft, adopting an act and bringing that act into force are not the same event. Software that treats a proposed obligation as binding can harm real customers.
This library therefore distinguishes official enacted primary sources, draft regulatory material, Wesfin's own policy interpretation, proposed architecture and executable synthetic evidence. A successful test is evidence of particular software behaviour in a defined environment, not statutory authorisation.
A reading route for a non-specialist
Start with the EDDIE UA purpose to understand why verified interval readings matter to customers and competition. Read the European EDDIE history to understand the origin of the interoperable energy-data idea and the Ukrainian naming choice. Next read Ukrainian law, and only then the architecture and laboratory. Otherwise a technically appealing diagram may be confused with a legally permitted market arrangement.
A route for legal and regulatory professionals
Review the official Electricity Market Law, its 2026 amendments and Commercial Metering Code No. 311 as of a clearly stated date. Compare exact current clauses with the user-supplied November draft, then inspect the REG-006 analysis of what is already proposed and what procedural ambiguities remain. Each recommended change needs a legal competence check, consideration of existing AKO procedures, proportionality and independently reviewed drafting.
The research documents are not ready-to-enact regulatory instruments simply because their headings resemble official legislative texts.
A route for engineers
Read architecture specification ARCH-001 together with threat model ARCH-002 and the EU clause-to-test matrix. Research OpenAPI paths are hypothetical and do not establish real Ukrenergo DataHub endpoints. Synthetic grant/revoke tests are useful but cannot replace lawful entitlement, organisational identity, independently verified signatures, secure incident response or multi-host fault testing.
The White Paper and its status
The EDDIE UA White Paper is the common narrative of the project's purpose, regulatory context, technical hypotheses, governance, economic comparison and milestones. It is still a consultation draft. The portal chapters provide more detail and illustrative cases, while the White Paper keeps the whole argument together.
Why public primary links matter
External readers must be able to verify the core claims without opening private Wesfin GitHub pull requests. The European Commission's CORDIS record documents the original European project, and the Ukrainian regulator's Code No. 311 establishes a public reference point for domestic metering regulation. Claims without accessible confirmation should be marked as such rather than presented as settled facts.

