The Interface Delta
Doesn't Own
A thesis on the structural wall between airline systems and the frontline vendors that keep them moving.
Every Delta flight touches three separate companies before it leaves the gate. None of them have Delta logins. The dashed blue line is the corporate boundary.
A real coordination flow, pulled from the agent's thread. Every line crosses the third-party boundary.
The Provisioning Wall
Catering, fueling, and cleaning vendors are non-employees. They cannot be given Delta logins. They cannot be provisioned into internal software stacks - route optimization tools, crew scheduling platforms, operations dashboards. The corporate identity boundary is absolute.
SMS/iMessage is the only interface that reaches across the corporate boundary.
This agent layer sits upstream of traditional systems. It captures the reality of the ramp - delays, ETAs, sequencing conflicts - and feeds it back into the optimization engines, rather than replacing them. The Ops Review DB gets a structured log without anyone filling out a form.
Delta owns the systems inside the blue line. The agent operates on the line itself - a coordination layer that spans the divide without closing it. It doesn't replace the vendors. It connects them.
Where does this break?
A thesis is only as strong as its honest accounting of failure modes. Here are the ones that keep me up at night.
Who owns the coordination data? If the agent logs every vendor delay and feeds it into Delta's ops review, does that data become leverage in contract negotiations? Vendors may demand that the agent logs only aggregate metrics, not per-incident records. The value of the system depends on granularity; the contracts may forbid it.
When the agent reprioritizes the catering sequence and a catering truck misses its window, who is at fault? The agent? Delta Operations? The vendor's dispatcher who accepted the automated instruction? The liability chain for agent-directed actions across corporate boundaries is untested.
The vendor's shift supervisor has been coordinating turn times by phone for fifteen years. An agent that texts instructions directly to their crews bypasses their authority. If middle-management sees the agent as a threat to their role, they will undermine it. Adoption requires their buy-in, and buy-in may require giving them visibility and control they don't have today.
The interface Delta doesn't own is the one that keeps its planes moving. The wall isn't going anywhere. The question is whether you build a layer that works across it.