TLAY Product Architecture

13. Reference Pattern: Streaming Energy Commerce

Consider an autonomous delivery vehicle that needs energy from an independently operated charging robot.

Participants#

  • Vehicle owner — funds the fleet and defines purchasing policy.
  • Buyer machine — the autonomous vehicle running BoAT MER.
  • Seller machine — the charger running BoAT MER or a trusted gateway.
  • Commerce application — manages discovery, pricing, and fleet operations.
  • Settlement provider — submits or settles signed value authorizations.
  • HashAnchor — anchors the service and payment evidence.
eCandle End-to-End Commerce Flow eCandle end-to-end flow in which a stablecoin payment unlocks energy, the device signs delivery events, HashAnchor issues proof, and revenue is split programmatically. TLAY REFERENCE IMPLEMENTATION eCandle End-to-End Commerce Flow A real-world machine commerce example: stablecoin payment unlocks energy and creates verifiable delivery evidence. TLAY eCandleSolar + battery + meter + control BoAT identity Signed events 1 User / Energy BuyerRequest powerReceive price quote 2 Stablecoin PaymentUSDC / USDTSmall prepaid amount 4 HashAnchorAnchor delivery proofIssue portable receipt 5 Programmable SplitOperator · ownerservice partners 3 price + sessionpayment authorizationmetered delivery proofverified settlementunlock energyPAY → UNLOCK → DELIVER → PROVE → SPLITA physical energy service becomes digitally executable and independently verifiable. ECONOMIC INFRASTRUCTURE FOR AUTONOMOUS MACHINES
Figure 8. eCandle demonstrates how a physical energy service can become digitally executable, payable, and independently verifiable.

Policy#

The vehicle is allowed to:

  • buy electricity only from approved or sufficiently reputable providers;
  • pay no more than a defined price per kWh;
  • spend no more than a session limit;
  • use an approved stablecoin and network;
  • require a verifiable delivery receipt.

Transaction#

  1. The charger publishes a signed price and availability offer.
  2. The vehicle checks its energy need, route, offer, and policy.
  3. Both machines establish a session and exchange identifiers.
  4. The charger delivers a small energy slice.
  5. The vehicle verifies the meter update and signs a corresponding payment authorization.
  6. Delivery and authorization repeat until the target state is reached.
  7. The settlement actor submits or aggregates the authorizations.
  8. HashAnchor anchors the offer, session, meter events, and settlement link.
  9. Both operators receive a portable receipt.

Result#

The vehicle received energy without a human checkout flow. The charger received payment with bounded delivery risk. Neither operator had to trust only the other party’s private database. The business process was digitally represented, economically executable, and independently verifiable.

This pattern can be adapted to bandwidth, compute, physical access, robot labor, mobility, and machine-generated data.