Draft · research

Governance, accreditation and trust in an EDDIE UA federation

Зміст статті / On this page (14)
  1. Why governance is a system requirement
  2. Division of responsibility
  3. Preventing conflicts of interest
  4. Proposed G0–G4 admission levels
  5. Accountability and disputes
  6. Open standards governance
  7. Open institutional questions
  8. Trust cannot be reduced to a software protocol
  9. A concrete conflict-of-interest scenario
  10. What the proposed G0–G4 process actually means
  11. How an incident would be investigated
  12. Neutrality where Wesfin is involved
  13. Useful public transparency
  14. Explore

Why governance is a system requirement

Metering and consumption patterns may reveal sensitive industrial activity. Technology cannot establish fair access by itself when the same organisation can define the rules, operate the gateway and favour one eligible party. EDDIE UA therefore separates statutory authority, technical services, independent evidence and competition safeguards.

Division of responsibility

The Ukrainian statutory commercial metering administrator (AKO) retains the responsibilities established by law. NCRECP supervises activities within its lawful mandate; the initiative cannot enlarge those powers. Metering service providers, network operators, suppliers and balance-responsible parties retain their existing obligations. Permission administration and independent data-access nodes are proposed functional roles, not automatically legally recognised organisations.

Wesfin Group may sponsor research or software development. It does not issue regulatory licences, certify market participants or authorise access to official customer data.

Preventing conflicts of interest

Wesfin Flex must obtain exactly the same onboarding rules, contract versions, legitimate data scope, access fees, denial reasons and operational service levels as a competing aggregator. A technology provider must not use confidential third-party consumption profiles for its own trading or commercial targeting without a valid basis. Proposed safeguards include disclosure of related parties, segregation of keys and accounts, independent auditing, appeal mechanisms and transparent funding.

Proposed G0–G4 admission levels

G0 – Organisational eligibility

Verify the legal entity and representative, understand its intended function, and declare conflicts of interest. No customer-data entitlement is conferred.

G1 – Synthetic conformance

Test standard schemas and six EU-reference journeys within the participant's role, including deny, revoke, correction, replay, audit and versioning. Successful tests establish software capability only.

G2 – Independent security evaluation

Cross-organisation mTLS/PKI, key lifecycle, authentication, authorisation, vulnerability testing, secure logs, privacy controls, recovery objectives, incidents and subcontractor responsibilities. Existing synthetic CI does not satisfy this level.

G3 – Limited lawful pilot

Contracts, defined scope, lawful basis, controlled access, a documented termination mechanism, incident reporting and independent observation. Any use of actual metering-point data requires specific permission or another lawful basis.

G4 – Production admission

Only under a procedure lawfully created or recognised by competent institutions. EDDIE UA has not achieved G4 and has no authority to grant it.

Accountability and disputes

An access denial should carry a traceable reason without disclosing a third party's private metering information. The review process must distinguish a legal dispute over entitlement from a software failure. Incorrect official readings remain subject to the relevant metering/settlement correction procedure, not silent rewriting by a federated copy.

If two technical nodes appear to hold the same authority, uncertain writes should be suspended, evidence preserved and a documented reconciliation undertaken. Incident transparency must balance accountability with confidentiality and security.

Open standards governance

Documented proposal → consultation → reasoned responses → security and legal review → reproducible conformance tests → versioned contract → migration period. Security emergencies need a controlled exception path, never an invisible privileged interface.

Open institutional questions

Who has legal competence to run the national trust directory? Is a separate permission operator permissible without new legislation? What is a valid appeals channel? What data can an independent inspector access? How should neutral infrastructure be funded? These are matters for legal and regulatory consultation.

Trust cannot be reduced to a software protocol

Imagine that a company both operates the gateway to consumption data and sells its own aggregation service. How can a competing aggregator verify that it has equal onboarding terms? Who ensures that confidential consumption patterns are not used for commercial targeting? Who investigates an access breach and under which lawful competence?

A distributed network does not solve these problems by itself. EDDIE UA studies how statutory metering functions, access providers, permission management, technical development and independent review might be separated while respecting Ukrainian law.

A concrete conflict-of-interest scenario

Suppose a gateway operator is affiliated with one aggregator. A competing service waits a month for access while the affiliated operator completes onboarding in two days. That difference is not automatically evidence of discrimination: cases may have different complexity and legal basis. But it is a reason to collect comparable data, publish standard processes and have an independent review of unexplained differences.

The operator should not make more private information available to its trading affiliate than the law authorises. Technical access rules, keys, support processes and incident investigations need appropriate separation and oversight.

What the proposed G0–G4 process actually means

G0 checks the organisation and representative. G1 validates synthetic protocol compliance, including denial, revocation, corrections, audit and proper scoping. G2 addresses independent security: organisational certificates, cryptographic key lifecycle, protected records, incident handling and resilience. G3 is a deliberately narrow, contractually lawful pilot with clearly defined sources and responsibilities. G4 could be production admission only under a procedure established by competent institutions.

These are proposed research admission gates, not legal accreditation levels currently granted by EDDIE UA. A passing GitHub test is not G2, and a private pilot is not G4.

How an incident would be investigated

A service claims that it received a superseded reading. The explanation could be a valid historical version, an upstream correction, a wrong time zone, an adapter bug or a misidentified metering point. Evidence should establish the initial request, permission status, timestamp, data source, quality flag, published version and any correction chain.

An EDDIE access node may need to repair its own cache or protocol implementation, but it must not silently replace officially validated records with its own settlement decisions. Complaints about legal entitlement require a different route from technical troubleshooting.

Neutrality where Wesfin is involved

Wesfin Group may sponsor research and develop technology. Wesfin Flex may eventually act as an eligible customer-facing aggregator. These interests must not create private API shortcuts, preferential access to competitor profiles, hidden fee schedules or weaker audit requirements. Proposed safeguards include declared related parties, separate technical privileges, open specifications, externally reproducible tests and a reasoned appeal route.

Useful public transparency

Citizens should not receive unrestricted access to other people's consumption logs. Appropriate aggregated evidence could include onboarding request categories, contract versions, denials by reason, incident frequency, service quality and announced interface changes. Independent oversight and confidentiality must coexist through carefully defined legal access and statistics.

Explore