All guides

Explanations · 4 min

From the Lab to Wesfin Flex

Wesfin Lab is a separate environment for building and testing. Wesfin Flex is the energy flexibility platform. This page explains why the Lab is kept apart from it, and what the Lab does not prove.

Why isolation

In the Lab you experiment: you try profiles, break connections and send test commands. That is safe only if no action can reach a real site, the market or settlement.

So everything in the Lab lives in the . This boundary is built into the code, not only into settings.

The labels you see

A command's evidence manifest carries all four labels. Connections and command frames carry environment LAB and production_eligible false. A compatibility report also carries physical_qualification UNVERIFIED.

evidence manifest · lab-evidence-1
"environment": "LAB",
"production_eligible": false,
"physical_qualification": "UNVERIFIED",
"public_beta": "NOT_APPROVED"
LabelWhat it means
environment LABThe resource belongs to the Lab. A Lab command frame with another environment fails validation.
production_eligible falseThe resource cannot take part in production control. This value does not change in the Lab.
physical_qualification UNVERIFIEDWesfin has not tested the device on a physical bench. The evidence came from a simulator or a fixture.
SIMULATOR_ONLY, SIMULATED_REFERENCE_ONLYThe result applies to the reference model, not to your device.
public_beta NOT_APPROVEDA public beta of the Lab is not approved.

More: , .

How the boundary works

  1. Separate resources

    The Lab has its own MQTT broker, its own command worker and its own access rights. Lab credentials cannot write production topics.

  2. Separate roles

    Lab roles carry only Lab permissions. They never become production operator rights.

  3. Refusal on the production side

    Production command creation and publication, the registry and control-rights checks each reject Lab resources. Even if someone injects a production binding or mandate.

  4. No market

    Market activation in the Lab is always zero. The Lab shows physical flexibility availability, but there is no market in the Lab.

  5. No settlement

    The Lab runs no settlement. Lab telemetry is not a source of truth for settlement.

What a Lab report proves

A passed report proves that your profile is valid and that the reference model with your limits behaves safely in the standard tests. That is useful: profile mistakes show up early.

It does not prove that your real device behaves this way. Only reference firmware 1.0.0 is tested; other versions are UNKNOWN. MQTT and Home Assistant tests in the report run on in-process fixtures.

A VALIDATED status or a profile binding gives no production, market or physical-device eligibility.

What would be needed beyond the Lab

This section is about the future. It is not a promise, a dated plan or an offer. Wesfin holds an aggregator licence in Ukraine, but Wesfin Flex commercial services have not launched.

For a device to ever take part in Wesfin Flex, Lab evidence is not enough. At least the following would be needed:

  1. Physical qualification

    Testing the real device on real hardware, not on a simulator. A Lab evidence manifest is not such a qualification.

  2. Connector qualification

    Proof that the real connection survives failures and restores safely. Physical device failure recovery is not verified today.

  3. Separate production onboarding

    Production rejects Lab resources. So a separate onboarding would be needed, with its own control rights, the deploy gate and explicit owner approval.

  4. Commercial terms

    Market participation needs launched commercial services and agreements. They do not exist yet.

Your profile, report and evidence from the Lab can be a useful starting point. But none of them on its own opens a path to Wesfin Flex.