Autonomy Builders
← Back to dashboard

Founder briefs

Establish the command. Keep the human.

There is an official path. It is not finished. This is the public map of what has to exist by 1 October 2027, plus a civilian Quantum proposal for the continuity seat. Unofficial. Not a contract. Not a second flight computer.

01 · The branch

Secretary of War Pete Hegseth announced it on 30 September 2026 at Marine Corps Base Quantico, in the State of the Force address. The name is Autonomous Warfare Command, also AutoWarCom. It is planned as a four-star functional combatant command with service-like authorities, to scale autonomous and robotic systems across the joint force. The Department’s public target for full establishment is 1 October 2027. The last new combatant command before this was U.S. Space Command in 2019.

Status
Directed. Not yet raised.
Bridge
Project Agincourt
Clock
1 Oct 2027

02 · Who holds the bridge

The secretary directed the uncrewed-systems direct reporting program to lead Project Agincourt for the year of standup. Two public names. No portraits, no invented ranks beyond what was said.

Owen West

Director, Defense Innovation Unit

Public lead on the CEO side of the Agincourt pair. DIU already sits between the building and the companies that actually ship hardware.

Max Strasiser

Navy SEAL Senior Chief

First enlisted SEAL to graduate Navy Test Pilot School. Public COO side of the pair — operator, not a slide.

A four-star to raise the flag has been promised in public and not named. This board will not name one.

03 · What the team needs

0 of 10 marked on this device

Check a line when you understand it. That is a study mark, not a status from the Pentagon.

Technology by ⚛️ Quantum

04 · The Quantum layer

This is a proposal from QUANTUM ⚛️ GENIUS, not an appointment and not a subsystem inside AutoWarCom. The rule is the same one the checklist already uses: one place commits state, a human assigns signal versus threat, and no box on the edge gets to become a second command.

  • Kraken · sole ingest

    The only place state is committed. Robots, suits, factories, and this website do not get a second flight computer.

  • Quantum Bot · operator face

    Shows the picture. The human assigns signal versus threat. The machine does not self-authorize.

  • Phoenix · continuity

    A node can be killed. A SoulForge commit already ingested by Kraken is what gets raised. Hardware is mortal. The commit is the record.

  • SoulForge · identity first

    Identity is written before a door opens. Rejects stay with the operator: false origin, missed epoch, too-clean log, door still open, wrong core.

  • Quantum Bank · receipts

    Identity and value security. Not a treasury and not spending authority. Appropriations stay law.

  • PEGASUS · transit

    Carries a seed from one place to another. Transit is not command. It does not fly the fight.

Genius Genetics, if it shows up at all, is a sensing tile — not a weapon. Nothing in this stack is connected to this board. The board is public information on a phone.

Concept mark reading Autonomous Warfare Command. Not an official insignia.

05 · What this board will not do

  • It will not pretend to be the Department of War, AutoWarCom, or US Tech Force.
  • It will not take applications, clearances, or personal data.
  • It will not draw targets, release weapons, or touch nuclear or strategic command.
  • The mark on the left is concept art. It is not an official seal.

Public sources