Help Center

Protocol

Physical Asset Execution Engine (PAEE)

PAEE executes AirJIT logistics workflows as deterministic state transitions. It does not guess routes — ACE recommends; PAEE commits inspectable custody changes.

5 min read · English

The Physical Asset Execution Engine (PAEE) executes logistics workflows as a Logistics State Machine (LSM). Given the same inputs, it produces identical successor states. Determinism is a first-class property.

What PAEE does

  • Applies formally defined transitions for protocol actions
  • Refuses probabilistic outcomes inside the execution layer
  • Stays separate from ACE recommendations
  • Produces auditable progression of custody and obligation states

What PAEE does not do

PAEE does not “guess” the best traveler. Optimization belongs to ACE. Final commercial and custody effects belong to deterministic transitions participants can independently verify. J1USD movement is keyed off those transitions, not off a model score.

Implementation independence

A compliant Host portal, mobile app, or enterprise connector should agree on whether a collect event occurred. They may differ in UX. They must not differ in δ(s, e).

Related

Previous

Digital Logistics Assets (DLA)

Next

Logistics State Machine (LSM)