YAEL AI
Netted air freight held at an airport cargo facility.
AI agents for freight desks

No release on a promise.
No answer without a receipt.

Yael has shipped two systems. Release Control governs the physical handoff. Import Operations keeps each shipment current, takes the next permitted action, and records the source and result.

See the systems ↓ State 01 / Freight held
Where it started

A stolen load made the first rule simple.

Release Control was built around the physical handoff. A request is not a release decision. The machine makes “trust me” impossible.

01 / IncidentCargo was stolen.
02 / System 01Release Control.
03 / System 02Import Operations.
01 / Release Control

It will not release freight until it has verified the driver — identity and location — at the airport.

Release Control reads the shipment, scores the cargo’s theft risk, vets the carrier and its paperwork, and verifies the driver. A human signs every release.

01
Read the shipment.

Establish what is being handed over.

02
Score the cargo’s theft risk.

Put the cargo’s theft risk into the release decision.

03
Vet the carrier and paperwork.

Review the carrier and the documents presented.

04
Verify the driver.

Confirm identity and location at the airport.

A netted air-cargo pallet held behind a closed custody gate inside an airport cargo facility.
State 02 / Release blocked

No verified driver. No handoff.

Identity and airport location are not yet verified. The gate stays closed. The cargo remains in custody.

One handoff became the operating model for the whole shipment.

02 / Import Operations

It knows the shipment. It makes the next move.

Yael maintains the current state of every shipment, understands what that state requires, and takes the next permitted action. It sends routine updates and acts inside the desk’s guardrails. Only designated actions stop for approval. Every action leaves a receipt.

A netted air-cargo pallet beneath three separated operating layers inside an airport cargo facility.
The operating stack / Truth → Understanding → Action

Records become truth. Truth becomes understanding. Understanding becomes action. The action returns to the record.

Companion / Through the stack

Ask through the full stack. Ask what happened, what Yael did, or what comes next. The answer comes from the same record Yael uses to act.

A speculative cutaway of one air-freight shipment moving from source records through operating state to action and action record. A vertical aperture gives the Companion access to the full stack.

Layer 01 / Truth

Maintains the shipment record.

Email, tracking, TMS, and operator input remain distinct. Yael resolves them into the current shipment state. Each fact keeps its source and time. Unknown and conflict stay visible.

  • Source
  • Time
  • Current state
Layer 02 / Understanding

Decides what the state requires.

Physical movement is not work state. Yael separates the two. It identifies what changed, what is blocked, who owns the next move, and what must happen now.

  • Guardrails
  • Owner
  • Next move
Layer 03 / Action

Does the work. Then records it.

Yael takes the next permitted step. Routine updates go out as soon as the evidence supports them. Designated actions stop for approval. For every action, Yael records the source, time, rule, and result.

  • Authority
  • Action record
  • Approval boundary
The operating standard

Every claim has a citation. Every action has a receipt.

Every failure becomes a written incident report and a real backtest.

The AI is held to the standard an officer holds a unit to.

Yael AI / Thesis

AI will do most operations work within a few years. Someone has to measure it and stand behind it.

Agents for freight desks.
Receipts for every claim.

Talk to Yael AI ↗