ϟ INSTANTMEGAWATT
TECHNICAL PAPER · MODEL 0.1

A coordination layer for the charging network before the charging network.

FE-OS converts permitted operating observations into explainable proposals, then holds execution behind human, site, equipment, commercial and safety authority.

PROBLEM

Mobile energy must behave like infrastructure.

Dispatchable charging is useful only when the network can discover demand, qualify sites and equipment, reserve capacity, support the asset, reconcile measured delivery and preserve an accountable record. FE-OS coordinates those responsibilities without pretending to own every vehicle, charger, site or provider.

MIDDLEWARE DECISION PIPELINE

Proposal before execution.

Each stage answers a different operational question. A stage may advance the proposal, request better information or stop the workflow with a reason. Passing one stage never bypasses the authority required by the next.

Normalize Create a trusted starting point. Convert consented fleet, vehicle, charger, site, timing and policy inputs into common units and a versioned snapshot. Record the source, freshness, permissions and quality of each input so later decisions can be reproduced.
Project Estimate what happens if nothing changes. Calculate expected energy depletion, remaining time and distance, arrival windows and shared demand. Stale, contradictory or insufficient telemetry stops the proposal instead of being silently guessed.
Match Find feasible capacity—not merely the nearest asset. Compare connector, power, energy reserve, operator availability, corridor and arrival time with site authority, circulation, bay and safety constraints. Incompatible options are rejected before eligible options are ranked.
Explain Show why an option was selected. Return a deterministic mission proposal with its assumptions, constraints, policy version, ranking reasons and expiration—or return a specific no-dispatch reason that identifies what must change.
Approve Turn a feasible proposal into authorized intent. Obtain the separate fleet, operator, site, equipment, commercial and safety approvals that apply. Approval is scoped to that proposal and expires when its time, telemetry or operating conditions materially change.
Record Preserve one accountable operating history. Store identifiers, input lineage, approvals, state changes, measured delivery, exceptions and outcomes. Corrections append linked records; they do not silently replace the evidence used for the original decision.
SAFETY BOUNDARY

The core does not directly command machinery.

The current architecture cannot issue governor, CAN/Modbus, charging, rerouting, reservation, billing or payment commands. Provider adapters remain separately authorized, scoped, revocable and observable.

DURABLE MODEL

One transaction identity across operations.

Every layer refers to the same request, proposed mission and resulting service transaction. Responsibility identifies the operating truth that layer owns. Action describes the controlled work performed with that truth. Evidence is the durable record required to explain, audit, reconcile or correct the result.

LayerResponsibilityActionEvidence
DemandFleet need and energy objectiveOpen and version the charging request; validate consent, timing and the requested energy outcome.Consented request + baseline telemetry
SupplyAsset capability and reserveQualify compatible mobile capacity and propose an allocation without overstating availability.Operator attestation + fresh equipment telemetry
PlaceAuthority, circulation and safetyValidate the site, bay, access path and proposed operating window before matching it to a mission.Site authority + verified-site policy
ExecutionMission and state transitionsAdvance an approved mission through authorized adapters and record every accepted, rejected or failed transition.Signed approvals + state-event audit
CommerceDelivery, tax and settlementReconcile metered energy, determine applicable tax and create balanced settlement entries.Meter evidence + tax determination + ledger
UptimeTechnician, parts and supportOpen the support case, diagnose and repair the asset, then document its authorized return to service.Repair order + service evidence + return-to-service approval