DELOS MERIDIAN CORP.

Mission

A base isn't hardened if its digital work stops the moment an outside connection is cut. We are building Super Intelligence (SI) for the U.S. military, under its sovereign control. Cyberspace is now a warfighting domain, and that fight is being waged today on our nation's networks, including the ones our bases depend on. On September 30, 2026, the Department of War established FORTRESS America, its program for defending the homeland, effective immediately. The program makes "installation hardening and cyber resilience" one of its five pillars. Its establishing memorandum directs all Military Departments, Defense Agencies, and Field Activities to support its execution "without reservation." Its Program Office is to deliver "results in weeks, not years." We're answering the call.

The threat comes in through connected systems. Chinese state actors have been found inside U.S. communications, energy, transportation, and water networks, including on Guam, home to major U.S. bases, positioned to disrupt them in a crisis, some for at least five years. In late August, freezers at at least six U.S. military commissaries, the grocery stores on our bases, failed in what is being investigated as a suspected cyberattack; at one, the freezer went into defrost and heated the food. What is at stake is a base's ability to communicate, analyze, and act on its information when the connected systems it depends on are cut off or turned against it.

That makes it essential for a base's digital work to run on the base. The people who protect a base need sign-in, email, files, maps, reports, and reference material every day, and most of all during an incident, whether or not the outside network is up. Wherever that work depends on SI and software reached over a connection, from someone else's data center and at someone else's price, cutting the connection stops it, whether the cause is an outage or an attack.

Running that work on the base is also inevitable. The more of a base's work runs on SI, the more that SI has to run on the base. FORTRESS sets the direction; how long a base must keep running cut off, and how that is tested, comes from each customer's own requirement.

Our answer is SI that runs a base, on the base; on its own equipment, its own data, by its own operators. SI that doesn't get cut off when the base does. What we deliver is the whole working system: the models, the agents that use them to carry out assigned work, and the hosting, services, and software around them. DMOS is the operating system built to run it on site. The Black Box is the desktop data center it arrives on: a 24-inch cube designed to hold four computers for DMOS and the base's services, four for SI models, two independent networks, and shared storage with its own backup. DMOS does not repair a hacked controller; it keeps the base able to communicate, analyze, and act while that is dealt with.

DMOS is not a backup system. A backup system sits idle until the attack comes, then has to be brought online in the middle of it. The attackers are already in place. DMOS is built to be what a base works on every day, so when the connection is cut or turned against it, nothing has to switch over and the work keeps running. The old way, everyday work reached over a connection to someone else's data center, collapses with the connection.

Defense, Our First Market

We know this market from the inside. Co-founder Thomas Owen built DMOS; his background is data center infrastructure for U.S. Indo-Pacific Command and drone infrastructure for Joint Special Operations Command. Co-founder Travis Willmann served as a U.S. Army Green Beret and in intelligence, and has worked in U.S. Air Force Special Warfare programs; he turns DMOS into uses for the fields he knows.

Defense comes first because the requirement is already written, and it reaches every Military Department. We are starting with Air Force Security Forces, the airmen who defend Air Force bases. Squadron leadership has seen DMOS demonstrated, and we are finalizing the first purchase order with Security Forces.

The first acceptance test is everyday work: one tool that tracks the squadron's assignments, who owns each one, when each is due, and what is overdue, then drafts the brief from approved updates. That tool is only the first test; the hardware is designed to carry the squadron's own services and the SI tools that follow. DMOS is built so that agents get only the permissions the base grants, actions that need a person's approval wait for one, and every action leaves a signed record.

Market Opportunity

The market is the everyday digital work of the military and the SI now being added to it. Today that work runs on licensed software and rented cloud services: the operating system on every desk, email and documents, meetings and chat, file sharing, sign-in, and the cloud behind them. The SI being added to those suites is priced per user, per month. The Department of War has asked for $46.0 billion in 2027 for sovereign SI infrastructure that the government owns, down to modular compute for tactical sites. The request is not yet enacted, but it shows where the Department means its SI to run.

We take that market one base at a time, with a business built so each base makes the next easier to win. A base buys the Black Box with DMOS, installation, and its first year of support and updates. We price by the box, not by the seat. DMOS can run on enterprise racks, Black Boxes, workstations, laptops, and edge devices, so a base can grow past one Black Box and take its work into the field. DMOS is built to package finished work as a .dapp, a file that carries an agent's know-how: its instructions, its references, and the history of the work. A tool one squadron proves is built to install at the next base with that base's own data and permissions, without being rebuilt. Each accepted base becomes the reference and the starting point for the next.

Then we take the everyday work itself. DMOS 1 is planned to ship with .dapps that replace the everyday programs a computer comes with, so a base can move its daily work, not only its SI, onto equipment it owns. We plan for developers to build .dapps for DMOS the way they build apps for a phone. Each one adds to what every Black Box can do.

Others sell platforms for running SI on site, so SI on site alone is not our edge. Our edge is one complete system for one defined job, delivered and supported, and work that moves from base to base. The sequence we plan to earn: the first purchase order, the first Black Box accepted on site, the first follow-on order, and a second customer.

End State

When we win, the everyday software the military licenses today, and the cloud behind it, runs on DMOS. The military owns its SI and uses it to expand its own operations: the applications, agents, and workflows it builds run without a vendor's permission and without another license fee for each one. That is sovereignty over its own operations.

The question is not whether the military will use SI. It is what that use looks like, and who controls it, in six months, in a year, and after that. FORTRESS points to bases that keep running on their own, and we are building DMOS to be what they run on every day. The ability to defend and fight should not depend on a vendor authorizing the next step.

Status and Next Milestones

In our lab, we have run SI models on our own equipment, completed an installation with no network connection, and tested identity, recovery, and approval controls in limited form. Our pilot uses hosted management services today; the Black Box is built to bring them on site. Still ahead: the complete Black Box as built, a full user workflow with no network, a tool built from a staff member's description, a signed record for every action, and renewal prices.

What we prove next:

1. Interim Authorization to Test: Agree with the IT office what the IATT requires for the first Black Box, and meet it.
2. First Black Box, Built and Accepted: Build it, install it for Security Forces, and pass the acceptance tests the customer agrees to. Payment follows acceptance, so we fund each build up front.
3. Work With the Network Off: Run a squadron workflow end to end with every outside connection off, and record how long it ran.
4. A .dapp Moved Between Bases: Install a tool from one base at a second base and show it working with that base's own data.

Black Box is the first form. DMOS is the continuing product.