An Air Force Chief Scientist Says the Service Still Needs the AOC Tools Kessel Run Has Supposedly Been Building Since 2017

Continues to need

Kessel Run’s own headquarters published this on 4 August 2026, in a release celebrating the briefing it gave to the Air Force’s chief scientists. The speaker is Dr. Albert Lowas, Air Mobility Command chief scientist:

“The Air Force continues to need more responsive and robust air operation center tools, especially as the nature of war becomes faster and crosses more domains.”

Continues to need.

Kessel Run was approved at the Air Force Life Cycle Management Center in April 2017 to modernize the Air Operations Center weapon system. The plan it came out of, AOC Pathfinder, promised modernized AOC capability within one year. Nine years past that one-year promise, the Air Force sent its scientists to look at the work, and what they produced on the record is that the Air Force still needs the tools.

No critic said this. No former employee said it on Reddit. An Air Force chief scientist said it, by name, in a news release written by Kessel Run’s own headquarters public affairs office, under a headline celebrating Kessel Run’s push to modernize. They printed the verdict themselves because they did not recognize it as one.

Nine years of work, and the status report is the requirement.

Not a gripe from the cheap seats

Lowas was not a passing critic with a grudge. On 21 and 22 July 2026, lead scientists from across the Air Force met at Hanscom Air Force Base for the Air Force Technology Horizons, Engineering, and Advisory Panel, whose membership per the release draws chief scientists from ten organizations, Air Combat Command, Air Force Global Strike Command and Pacific Air Forces among them. The release is also explicit about what that community is for. It recognizes “high-priority problem sets” and it assesses “whether technology is efficiently and effectively solving those problems.”

So this was not a networking event. This was an assessment, by the people the Air Force employs to tell it whether its technology works. And the release bills Kessel Run’s slot as “a highlight of the panel.” Kessel Run walked into its own performance review and then wrote up the highlight reel itself.

Lowas said plainly why they came: “We wanted to learn where Kessel Run is in the process of providing these critical IT tools across the Air Force.”

Nine years in, the open question was where Kessel Run is in the process.

The one compliment was for giving up

Lowas did offer something warm. This is the whole of it: “Kessel Run has substantially changed its approach to providing those solutions.”

That is the compliment. Not that the tools arrived. Not that an air operations center runs better. Not that one operator anywhere is measurably better off. In 2026, the most positive observation an Air Force chief scientist could produce about Kessel Run is that it is going about it differently now.

He is factually correct, and that is the problem. The substantial change is a matter of record. In March 2025 Kessel Run announced it was ending mixed government-vendor coding teams for a model it branded government-led and vendor-managed. Col. Richard Lopez, then its senior materiel leader, stated the change without decoration: “the individuals that are coding are now going to be the vendors, rather than mixed government-vendor teams.”

The substantial change of approach was Kessel Run stopping writing the software.

The single development in nine years that registered with the Air Force’s scientific community was Kessel Run’s decision to hand the work to someone else.

Milliseconds

Lt. Col. Camdon Cady, materiel leader for Kessel Run’s Operational Command and Control branch, delivered the briefing. He sold automation, and this is the sentence he picked to sell it with:

“We are modernizing AOCs by bringing more automation into the cloud, ensuring our operators have the tools they need to make decisions in milliseconds rather than hours.”

Now read the unit he picked for the present tense. Hours. Nine years after Kessel Run arrived to fix the air operations center, the officer running its operational command and control branch characterizes today’s decision timeline as hours, and he does it inside the sales pitch, as the baseline he expects to be graded against.

Notice also where the precision lives. Kessel Run will quote you the operator’s future reaction time to the millisecond, on a system whose contract is not scheduled to be awarded until June 2027.

Cady is worth tracking across releases, because he adjusts. On 29 June 2026, selling automation to his own workforce, his pitch was: “These are tools that we can use to actually make our own lives easier.” Three weeks later, selling automation to the Air Force’s chief scientists, it decides the air war in milliseconds.

Inside the building, automation means less work for the staff. Outside it, automation means decision superiority at the speed of light. The technology does not change between those two rooms. Only the person being billed does.

Architects and acquires

Then there is the boilerplate at the bottom of the release, which is where documents like this keep their honesty. Nobody edits the boilerplate. Nobody reads it. It just quietly accumulates whatever the organization has actually become.

“Kessel Run architects and acquires the means to connect weapon systems with operators and decision makers to enable the joint force.”

Architects and acquires. Look at the verbs, and at the ones that are missing. Not writes. Not builds. Not ships. Not codes. Kessel Run was founded on the argument that the Air Force must build its own software rather than buy it, and its own official one-line description of itself has come to rest on drawing the diagram and purchasing the result.

The motto on the wall in Boston was Code. Deploy. Win. The verbs in the 2026 boilerplate are architect and acquire.

Lowas’s choice of noun deserves the same attention. He called them “critical IT tools.” Not weapons. Not combat capability. Not anything a pilot would recognize. IT tools. The organization that named itself after a smuggling run through hostile space is, in the working vocabulary of the Air Force’s own scientific community, an IT shop.

The release argues with itself and loses

The best thing in this document is that it contains its own rebuttal.

Paragraph nine, the standard description: “Kessel Run delivers resilient command and control and targeting software capabilities that provide warfighters with decision advantage.”

Delivers. Present tense. Already happening.

Paragraph three, the chief scientist: the Air Force “continues to need more responsive and robust air operation center tools.”

Those two sentences are in the same nine-paragraph press release. One is what Kessel Run says it is doing. The other is what the Air Force’s scientists say is still missing. Six paragraphs of separation was enough for both to clear the approval chain, because the approval chain is not reading for contradictions. It is reading for tone.

The verdict

Nothing went wrong here. That is the point. This was a good week by Kessel Run’s standards, written up by its own side. The Air Force convened its scientific advisory panel, billed Kessel Run as a highlight, sat through the briefing, and generated on the record the observation that the requirement is still open. Kessel Run’s headquarters then published that as an accomplishment, with photographs.

Nine years. The Air Force’s standing scientific advisory panel in one room. The takeaway quote is “continues to need.” The compliment is “changed its approach.” The self-description is “architects and acquires.” The promise is still in the future tense, and the vendor who might keep it does not get selected until next summer.

Every institution eventually writes its truest sentence by accident. Kessel Run’s came out on 4 August 2026, in its own press release, from a scientist who showed up to find out where it is in the process.

Nine years, and the answer is still: in the process.

Sources

The jokes are ours. These are not.

Disclaimer: Satire. Every fact above is cited and belongs to whoever reported it. The malice is original.