Skip to content
LumenFlow

EMIT Energy Telemetry

EMIT is LumenFlow’s energy-to-the-metal telemetry surface. It gives cloud one shared event contract for energy facts:

  • measured device or node energy from connected compute,
  • modeled token energy when managed inference exposes no physical meter, and
  • facility-window energy from the Campus Pack.

Cloud receives these facts and owns attribution, carbon conversion, proof composition, billing, margin, and COGS. LumenFlow .dev only observes and emits energy provenance.

Event Contract

Section titled “Event Contract”

The shared event kind is emit:energy_meter_recorded on the emit channel. The unit is always joules, and every event carries explicit provenance:

{
  kind: 'emit:energy_meter_recorded',
  channel_id: 'emit',
  unit: 'joules',
  quantity: 151.2,
  event_ts: '2026-06-13T16:00:00.000Z',
  workspace_id: 'ws_123',
  compute_assignment_run_id: 'run_123',
  tags: {
    energy_provenance: 'measured',
    energy_source: 'dcgm',
    component: 'gpu',
    phase: 'total',
    sampling_hz: 1,
    measurement_window_ms: 1000,
    accuracy_class: 'device-counter',
    capability_tier: 'gpu-runner',
    provider_family: 'operator-owned',
    pue_applied: false,
  },
}

The closed source vocabulary names measurement interfaces and models, not compute providers: nvml, dcgm, rapl, ipmi, redfish, pdu, ups, smart_meter, token_model, and facility_proration.

Provenance Tiers

Section titled “Provenance Tiers”
TierMeaning
measuredEnergy is integrated from physical sensor data observed during the run or facility window.
modeledEnergy is calculated from a cited coefficient model because physical sensors are unavailable.
estimatedEnergy is coarsely inferred, for example from aggregate facility power prorated by compute share.

Modeled and estimated values are useful, but they never masquerade as measured values. That is what lets cloud rank proof strength and expose caveats.

Measured Connected Compute

Section titled “Measured Connected Compute”

Connected compute meters run beside the assignment, so they can correlate raw IT-load energy to compute_assignment_run_id.

  1. The runner starts an assignment with a run id. 2. The node power meter samples all available counters before the work. 3. The assignment work runs. 4. The meter samples again, computes deltas, and emits one event per matched sensor/component. 5. Missing or privilege-blocked sensors produce diagnostics, not fabricated measurements.

Supported sensor interfaces include GPU energy through NVML/DCGM, CPU/DRAM energy through Linux powercap/RAPL, and optional node/chassis sources through IPMI or Redfish. RAPL exposes both energy monitoring and powercap constraint attributes; EMIT readers use the monitoring side only.

Modeled Managed Inference

Section titled “Modeled Managed Inference”

When a managed or BYOK-proxy assignment exposes token counts but no physical energy meter, EMIT may emit energy_provenance: "modeled" and energy_source: "token_model".

Modeled coefficients must carry:

  • source title and URL,
  • publication or benchmark date,
  • access date and source version,
  • measurement boundary (accelerator, system, or facility),
  • confidence (low, medium, or high), and
  • notes explaining the coefficient’s intended use.

The current coefficient table is deliberately provider-neutral. It uses opaque profile ids such as managed-balanced-v1 and opaque family/tier labels rather than provider brand names.

Campus Facility Energy

Section titled “Campus Facility Energy”

Facility windows belong to the Campus Pack, not a new Energy Pack. campus:facility_energy normalizes operator-provided PDU, IPMI, Redfish, and smart-meter windows into the same emit:energy_meter_recorded event.

Facility-grain events carry:

  • facility_id,
  • valid_from and valid_to,
  • region or grid_region,
  • operator-owned source,
  • optional PUE,
  • optional grid carbon intensity,
  • optional electricity price, and
  • optional curtailment-window metadata.

pue_applied prevents double counting. false means raw IT-load joules and allows cloud to apply a matching facility PUE overlay. true means the energy quantity already includes facility overhead and must not receive another PUE multiplier downstream.

Why There Is No Energy Pack

Section titled “Why There Is No Energy Pack”

Run-Grain Energy

Node and device meters live in connected compute because they follow assignment execution and correlate by compute_assignment_run_id.

Facility Energy

Facility windows live in Campus Pack because they are location-pinned, operator-owned telemetry with facility_id and validity windows.

Cloud Meaning

Attribution, carbon, proof, billing, margin, and COGS remain in LumenFlow Cloud.

A future BYOC-installable energy bundle could be packaging, but it must not change the event shape, transport, source vocabulary, or trust boundary.

Conformance Guidance

Section titled “Conformance Guidance”

Before shipping an EMIT change:

pnpm exec vitest run packages/@lumenflow/cli/src/__tests__/emit-energy-invariants.test.ts
pnpm events:validate
pnpm --filter @lumenflow/docs build

The invariant suite checks that live builders, SDK contracts, fixtures, and public examples stay observation-only and provider-brand-free. The conformance fixtures cover measured GPU, modeled token, and facility energy rows.

References

Section titled “References”