AirJIT assumes a heterogeneous network. Specialized node classes interoperate through standardized interfaces rather than a single platform account type.
Primary classes
- Validator — verify protocol execution, validate events, secure the network through JIT staking
- Carrier — airlines, trucking, shipping, rail capacity on the GLG (travelers are a peer-capacity special case)
- Warehouse — storage, fulfillment, consolidation, and inspection
- Host — localized pickup and decentralized last-mile density
- Oracle — bridge external data without mutating protocol state
- Enterprise — integrate ERP, WMS, TMS, and accounting
- Government — customs, regulatory approvals, sovereign participation
Oracles are not mutators
Oracles connect customs systems, IoT attestations, carrier schedules, and other off-protocol signals. They inform decisions. They do not unilaterally become the execution authority. Provenance and freshness should be inspectable; contested data can be rejected before PAEE commitment.
No monopolizing class
Interfaces are the product. Hosts do not replace travelers. Validators do not capture J1USD invoices. Enterprises do not rewrite identity. Competition and specialization stay possible because semantics are shared.