TLAY Product Architecture

12. Integration Paths

TLAY Deployment Modes Comparison of device-native, edge gateway, cloud application, HashAnchor-only, and BoAT MER-only deployment modes. TLAY INTEGRATION GUIDE TLAY Deployment Modes Five integration paths balance speed, hardware access, and strength of machine-origin trust. TLAY Deployment modeTrust lives atKey advantagePrimary limitationBest forDevice-nativeStrongestMachine / secure elementStrongest origin proofFirmware integrationNew connected hardwareEdge gatewayLegacy bridgeTrusted local gatewayWorks with legacy machinesGateway is trust boundaryIndustrial retrofitsCloud / appFastest pilotApplication backendFastest commercial pilotWeaker device originBusiness-model validationHashAnchor-onlyProof entryExisting app + prooflayerPortable audit trailNo machine authorityLogs, compliance, dataproofBoAT MER-onlyRuntime entryMachine runtimeIdentity + payment at edgeExternal proof requiredCustom trust stacksDECISION RULEStart where integration is practical; move signing and policy closer to the machine as assurance requirements increase. ECONOMIC INFRASTRUCTURE FOR AUTONOMOUS MACHINES
Figure 7. TLAY supports progressive deployment: teams can start with the fastest practical integration and move trust closer to the machine over time.

12.1 Device-First Integration#

Use this path when the machine hardware and firmware can be modified.

  1. Port or configure the BoAT MER platform abstraction layer.
  2. Provision a device identity and keys.
  3. Select buyer, seller, or full build profile.
  4. Add the required communication and payment adapter.
  5. Define local authorization rules.
  6. Sign operational events on the device.
  7. Submit event hashes to HashAnchor through a gateway or application.

This provides the strongest device-origin guarantee.

12.2 Gateway Integration#

Use this path for legacy machines that cannot run BoAT MER directly.

A trusted edge gateway can:

  • communicate with the existing machine protocol;
  • maintain a machine-scoped identity;
  • translate machine state into signed events;
  • enforce commercial policy;
  • initiate payment or proof workflows.

The trust boundary moves from the device to the gateway, which should be clearly represented in receipts and identity metadata.

12.3 Cloud/Application Integration#

Use this path to test a business model before embedded deployment.

The application can integrate HashAnchor, payment APIs, and simulated machine identities. Once commercial logic is validated, signing and policy enforcement can move progressively closer to the physical machine.

This staged model reduces initial integration cost while preserving a route to stronger machine-native trust.

12.4 HashAnchor-Only Integration#

Existing platforms can adopt HashAnchor without adopting the full TLAY stack. Common use cases include:

  • tamper-evident IoT logs;
  • supply-chain milestones;
  • AI-generated industrial decisions;
  • maintenance and calibration records;
  • energy and carbon data;
  • payment and service reconciliation.

HashAnchor becomes an entry point into the broader TLAY network.

12.5 BoAT MER-Only Integration#

Developers can use BoAT MER for machine identity, signing, or payment authorization while using their own proof infrastructure. Open interfaces reduce lock-in and make the runtime useful before the full TLAY network is adopted.