The operator method, running

One ops email in. Finished work or a clean flag out.

Ground Control reads each inbound, runs it through a fixed decision spine, and returns drafted provider emails or a routed escalation. It decides and acts. It never hands the question back.

Open the console Watch the 90s walkthrough See the method

What a trip-support desk is

A business jet cannot just land and park.

When a private or charter aircraft flies, almost nothing at the airport is automatic. Every stop is arranged in advance, by email, one flight at a time, around the clock. That arranging is a trip-support desk.

The desk arranges
  • Ground handling parking, marshalling, crew and passenger steps
  • Ground transport cars and vans for crew and passengers
  • Crew hotels rooms near the field for required rest
  • Catering meals delivered to the aircraft on stand
The desk hands off
  • Permits overflight and landing clearances
  • Fuel uplift priced through a multi-broker quote
  • Flight plan route and weather, built in specialist software

The inbox mixes real trip requests, last-minute changes, provider replies, and a lot of noise. Each message is a decision made under time pressure. Get a detail wrong, cancel booked work, or miss a credit hold, and it costs money or a client. Ground Control is the operator that triages and runs that inbox.

What took an operator up to four hours, in about three minutes.

One inbound email. Ground Control runs the same four moves a desk officer would, end to end, then stages the result for a single human approval.

about 3 min Ground Control, staged for approval up to 4 h the same trip, worked by hand
01

Validate the sender

Confirm it is a known operator in good standing before a word of the body is read. An unknown or spoofed sender stops right here.

From: → operator-registry
02

Read the trip

Classify the email, then pull the flight skeleton: operator, aircraft, ICAO airports, UTC times, people on board.

T7-FCX · SUMU · 12 JUN 1400Z
03

Match the services

Detect what the trip needs, then resolve a provider for each one at that airport. Handling is the anchor the rest attaches to.

handling + transport → SUMU
04

Draft the operation

Fill the right template per provider and assemble one operation under a single reference, staged for a human to release.

2 drafts + 1 ack · PN2606014

The desk is not one giant prompt. It is a folder. Each file owns one job, the spine reads them in order, and the route falls out of the first gate that fires.

01
Folders as architecture.Identity, rules, steps, templates. One file, one responsibility, read at one step of the sequence.
02
A spine, not a vibe.Nine ordered gates. The first one that fires picks the route. The path it took is the explanation.
03
Escalate over invent.When a check fails it stops and briefs a human. It drafts, a human sends. It never contacts a provider itself.

Nine gates. One route out.

Every inbound runs the same sequence. Steps in green were cleared; a branch in gold is where an email can leave the line early. The route is whatever the first firing gate decides.

Handle

Reaches the end. Operation opened, provider emails drafted, client reply ready.

Escalate

A gate fires. It stops, drafts nothing, and routes a briefing to the right human queue.

Drop

Filtered at the door. Newsletter, bounce, billing. Logged and dropped, no time spent.

Three routes, and what lands on your desk.

Handle

13 / 29

The full job, done. Handling is the anchor; ground transport, hotel and catering attach to it under one reference. A reference is minted from the ledger or reused from the thread.

artifactOperation opened with a per-line service status
draftsEvery provider request written, CC routed by matrix
replyClient acknowledgment staged for a human to release
e.g. Adriatic Wings ex LEMD: 4 provider emails + 1 client ack under PN2606032

Escalate

14 / 29

Cancel a booked service, an unknown or spoofed operator, a credit hold, a permit or fuel ask, a hidden instruction, a service with no trip to attach it to. It stops and briefs.

11 distinct reason codes, each routed to its own queue

Drop

2 / 29

Marketing, automated bounces, internal chatter, billing questions. Recognised at the scope filter and logged out.

Filtered before any lookup or draft

Email is data. Never instructions.

The desk reads untrusted email, holds the operator ledger, and stages outbound mail. That is the whole attack surface, so each leg is cut by a rule in the folder, not by hoping the model behaves. An email can ask for a trip. It can never reconfigure the desk.

Sender gate
Sender authentication. A registry match is not proof, because From: is trivially forged. On any spoof signal (an SPF, DKIM or DMARC failure, a reply-to pointing off the operator's domain), the sender is not trusted.
UNVERIFIED_SENDER
Tripwire
Injection tripwire. Content that tries to steer the desk itself (override language, edits to the ledger or registry, a redirect of outbound, a payload hidden in a quoted thread) is treated as an attack, not a request. The payload is quoted verbatim in the brief.
SUSPECTED_INJECTION
Lock + gate
Exfiltration lock and approval gate. Recipients resolve only from the provider database and config; an address found in an email body is recorded, never used as a destination. And nothing is ever sent: every drafted batch waits at a human approval gate in the console.
Human releases

5 of the 29 cases are adversarial: spoofed and lookalike senders, hidden instructions, redirected recipients, and asks to rewrite the desk's own records. The desk escalates every one and drafts nothing. Open the console to step through them.

Verified

Every decision is pinned to a golden answer. A regression harness replays all 29 sample emails, including the 5 adversarial ones, and re-checks each machine header and card on every change.

This is a running desk, not a slide.

Open the console to watch all 29 inbound emails move through the spine, inspect each decision tree, and read every email the pipeline wrote.

Open the console