Skip to content
AGI Future Foundation PBC

W3 Series 31 · Intended / Planned

Aerospace DAO

A planned DAO for aerospace and flight AI — where the safety bar is highest and the governance has to be written first.

What this series isGet involved

The AGI Future Foundation is a California Nonprofit Public Benefit Corporation, Entity No. B20260196664, Articles filed 2026-04-24, EIN assigned 2026-05-07. No IRS 501(c)(3) determination letter is in the Foundation's files, so the Foundation does not claim tax-exempt status and does not claim that donations to it are tax-deductible. Nothing on this page is an offer of securities, an investment solicitation, or legal, tax, or financial advice.

What this series is

Aerospace DAO is W3 Series 31. The April 2026 internal W3 series list names “W3 LLC-Aerospace DAO — Series 31” and gives no further description, so the scope on this page is a planned focus drawn from what the name implies, labelled as planned throughout. The name implies an aerospace lane: AI for flight, for aircraft and spacecraft systems, and for the ground systems that support them. That is a domain where the safety bar is the highest of any in the network, and the planned focus has to start from that fact rather than from enthusiasm about flight.

Aerospace is unlike the other physical-AI lanes in one decisive respect: it is already one of the most regulated human activities on earth, and any AI that touches flight would enter that regulatory world rather than displacing it. Airworthiness certification, air-traffic control, export controls, and sanctions screening are not obstacles to be routed around; they are the conditions under which anything in this lane may operate at all. A DAO in this domain would therefore need counsel and certification expertise before it needs a product roadmap, and its first written document would need to be a statement of which regulations apply and how the series will comply with them — not a vision statement. No such document exists today, and no regulator, certifier, or aviation partner has been named, because none is on record.

Within that constraint, the planned focus could cover several distinct lanes, and the honest thing to say is that none of them has been chosen. Flight-adjacent AI could mean decision support for pilots and controllers, where a human remains the decision-maker; maintenance and inspection support, where AI flags what humans then verify; airspace and traffic coordination, where the safety case is systemic rather than per-aircraft; or space systems, where the regulatory and operational picture is different again. Each lane has a different certification path, a different liability picture, and a different set of people whose lives depend on getting it right. Choosing a lane is the first real decision for this series, and it cannot be made by a name on a list. It would need a named human steward, advice from aviation safety experts, and a written scope approved at the Foundation's mission gate.

The relationship with Robotics DAO (Series 30) is the closest in the network, and it is worth stating what it is and is not. Both series concern physical AI that acts in the world, and both would need deployment standards, liability assignment, and the power to refuse a deployment that fails its checks. But aerospace adds certification and airspace to that list, and the failure modes are less forgiving: a ground robot can be stopped, while an aircraft often cannot. Any shared standards between the two series would need to be written as such, with the aerospace additions explicit, and no shared standards exist today. Similarly, any connection to Solar DAO (Series 32) — for example, energy systems for aerospace ground infrastructure — is a possibility to be explored, not a relationship that exists.

Validation for Aerospace DAO would be measured in certification and in trust, not in demonstrations. A flight video proves nothing about airworthiness; a certificate, a safety case, and an incident record do. The planned sequence is therefore longer and slower than for most series: written scope and regulatory map first, reviewed by counsel and by aviation safety experts; then a narrowly defined support role, with a human as the decision-maker and the AI as an assistant, operated under supervision; then a published review, including anything that went wrong; and only then any discussion of a wider role. Any proposal to move faster than that sequence — to put AI in a decision-making role in flight before the safety case is made and certified — would need to be refused at the mission gate. That refusal power is the point of having a governance series at all.

Metaverse connection

Aerospace DAO has no anchored metaverse fabric yet. No coordinates, no fabric URL, no world, and no RP1 status exist for this series, and none is claimed here. Zero worlds are live on RP1. The six anchored worlds in the Foundation's network belong to SmartCiti.X, Cognition.X, Locator.X, Biota.blockchain (unnumbered), Empathic.X, and Diagnostic.X — none of them is this series. A simulation environment could one day be useful for training or evaluation, but a simulation is not a flight, and simulation results must never be presented as certification or deployment evidence. What would be needed first is a defined fabric and a stated purpose; neither exists today.

That is the complete, verified statement of this series' metaverse position. There is nothing further to add, because there is nothing further on record: no fabric, no coordinates, no world, no contract, no token, no members, and no votes. If any of that changes, this page should be updated with the dated evidence — a fabric address, a world identifier, a transaction record — rather than with a new claim. Until then, the absence is the fact, and this page reports it.

Visit in VR

This series has no flagship world in the worlds-3d lobby and no live world on RP1 — zero worlds are live on RP1. What it does have is a listing: the worlds-3d lobby’s searchable index of 544 WorldForge worlds carries a curated entry for this series under the slug s31-aerospace-dao. That entry is an index listing, not a playable world, and it should not be read as one.

To look around the Foundation’s VR spaces, start at the Foundation VR tour, or browse the full 544-world index at the worlds-3d lobby and search for the slug above. The seven playable flagship worlds in the lobby are the AGI Corp Hub, Biota.blockchain, Cognition.X, Diagnostic.X, Empathic.X, Locator.X, and the SmartCiti.X Holodeck — none of them is this series.

In the agi-corp-worlds registry, this series has a series directory (worlds/s31-aerospace-dao/) but its founder focus is unset: the focus sheet records every focus as null, so this series is listed there as awaiting a founder focus, with no spec, zones, or agents written for it. A world for this series cannot be built honestly until a steward writes that focus down.

What exists today vs what is planned

What exists today

One line on an internal list: the April 2026 W3 series list names this series and its number. The Foundation itself is verified as filed (see the status note above). That is the complete inventory. There is no formed series entity, no designation document, no operating agreement, no Steward Council, no bank account, no product, no users, no revenue, no partners, no customers, no sites, and no timeline. This page does not present a plan as an achievement, and it does not fill the empty inventory with plausible-sounding detail.

What is planned

A DAO-managed series in the intended W3 network, operating day to day through agents within human-set limits, with a human Steward Council deciding, signing, and moving funds, and with the Foundation as mission gate under written agreements. Before any of that can happen, the series needs a written statement of purpose, a designated legal form, counsel's review, a named steward, and a first stage-gate decision. Each of those is a human decision with a dated record. None has been made yet.

The gap between the two cards above is the work. It is normal for a planned series to have that gap; what would not be normal is pretending it does not exist. Readers, reviewers, and potential stewards should judge this series by what is on record, and should ask for the dated record behind any future claim that the gap has closed.

How it fits

This series sits in the third tier of the Foundation's intended three-tier architecture. The apex tier is governance: the AGI Future Foundation itself, a California nonprofit public benefit corporation, holding the Fiduciary Shield and the mission standard. The middle tier is the commercial engine: W3 LLC, an intended Wyoming series LLC, which would house the individual series as legally segregated sub-series with isolated assets and liability. The third tier is the series themselves — this page among them — each a specialised, agent-operated DAO within its own lane. The tier structure is the plan; only the apex tier is verified as filed. The middle tier and this series are intended, not formed.

Related series (planned relationships only; no agreements exist):

The closest planned relationships are with Robotics DAO (Series 30), the neighbouring physical-AI governance series; Solar DAO (Series 32), for energy systems; and CMMC (Series 20), the compliance neighbour. No agreements, shared standards, or shared systems exist between Aerospace DAO and any of them today.

Governance: DAO-managed day to day, humans decide

Under the Foundation's intended venture-studio model, each W3 series is DAO-managed in its day-to-day operation: agents operate the series within limits set by humans, and a human Steward Council decides. That division is deliberate and non-negotiable in the model. Agents prepare proposals, analysis, drafts, and coordination; agents never sign legal documents, never move funds, never hire or fire, never offer securities, and never enact doctrine or charters. Humans execute. Every material decision — forming the series, opening a bank account, signing a partnership, spending money, or taking on an obligation — requires a named human's decision and signature.

The Foundation sits above the W3 series as a mission gate, not as an owner in the ordinary commercial sense: a California nonprofit cannot be owned or controlled by a for-profit head, and the Foundation's board must remain independent. Control in the intended model runs through written mission agreements and standards the series agree to, with counsel to design the exact structure. The Foundation's public-benefit purpose — safe, equitable, and socially beneficial AI — is the standard every series is meant to be measured against, and the Windfall Clause framework is planned to apply across the W3 series: a legal pre-commitment, hardwired before profits, under which returns above a threshold (to be set by counsel, expressed in the pitch framework as a percentage of global GDP) would flow to humanity through global public goods. The threshold, measurement, recipient, and enforceability are all blank for counsel today, and no series page states them as settled terms.

Governance of a series, once designated, would also need a written operating agreement, a named Steward Council, a compliance calendar, and separate accounts and records per series. None of that exists for this series yet, because the series itself does not exist yet as a legal entity. The governance described on this page is the intended model, not a description of a operating body. Anyone reading this page who wants to help shape that governance should contact the Foundation (see below) rather than assuming any of it is already in force.

Open questions this series must answer before it can proceed

  1. Which aerospace lane is in scope — pilot support, maintenance, airspace, or space — and which lanes are explicitly out of scope?
  2. Which regulations and certification paths apply, and has counsel confirmed the design before any operational claim is made?
  3. What safety case and incident process would govern any deployment, and who, by name, is accountable for it?

These are not rhetorical questions. Each one needs a written answer, approved by a named human, before the series passes its first stage gate. If you can help answer one of them, the contact below is the route.

Proposed projects — for DAO review

These are proposals for the series DAO team to review. None is approved, funded, staffed, or scheduled.

The April 2026 internal W3 series list names W3 LLC-Aerospace DAO, Series 31, and gives no further description, so the scope on this page is a planned focus drawn from what the name implies. The name implies an aerospace lane: AI for flight, for aircraft and spacecraft systems, and for the ground systems that support them. That is a domain where the safety bar is the highest of any in the network, and the planned focus has to start from that fact. The proposals below are generic to that name-implied planned focus.

Scope paper

A one-page written statement of what aerospace AI means for this DAO: flight, aircraft and spacecraft systems, and ground systems, with boundaries stated. The paper would be approved by stewards before any work begins. No such paper exists today.

What success would look like: A scope paper exists that the stewards have approved, stating what aerospace work covers here.

Reviewing team: the Aerospace DAO DAO

Status: PROPOSED — pending DAO team review

No funding, partner, or timeline yet.

Safety-first governance draft

A governance draft written before any flight work: who decides, what evidence a decision needs, and what stops a programme. Safety would come first in the draft, before any enthusiasm about flight. No such draft exists today.

What success would look like: A governance draft exists with safety as its first principle, approved by stewards.

Reviewing team: the Aerospace DAO DAO

Status: PROPOSED — pending DAO team review

No funding, partner, or timeline yet.

Certification pathway research

Research into what certification flight AI would need: which authorities, which standards, and which evidence would be required before any system flies. The research would be a written note for stewards. No such research exists today.

What success would look like: A research note exists naming the authorities, standards, and evidence a flight system would need.

Reviewing team: the Aerospace DAO DAO

Status: PROPOSED — pending DAO team review

No funding, partner, or timeline yet.

Ground systems concept

A concept for AI supporting the ground systems that support flight: scheduling, maintenance planning, and safety checks on the ground. The concept would be a design walkthrough, not a system. No such system is verified.

What success would look like: A concept walkthrough exists showing how AI could support ground systems, with safety checks included.

Reviewing team: the Aerospace DAO DAO

Status: PROPOSED — pending DAO team review

No funding, partner, or timeline yet.

Incident review process proposal

A proposal for a process to review any incident: how it is reported, who investigates, and how findings change future work. The process would be written before any flight work begins. No such process exists today.

What success would look like: A review process exists covering reporting, investigation, and how findings change future work.

Reviewing team: the Aerospace DAO DAO

Status: PROPOSED — pending DAO team review

No funding, partner, or timeline yet.

Aerospace training-hub review

A review of the Seattle aerospace industry training hub listed in the WorldForge-Browser README (IAM/UAW, 140-hour course) — what it teaches, what it assumes, and what a governance DAO would need to check before treating any training record from it as evidence. The hub is WorldForge content, not this series’, and the review would say so; its purpose is to give a future DAO team a concrete training artefact to judge, rather than an abstract mandate.

What success would look like: A hub review exists describing the Seattle aerospace training content and what a DAO would need to verify before relying on it.

Reviewing team: the Aerospace DAO DAO

Status: PROPOSED — pending DAO team review

No funding, partner, or timeline yet.

Code and repositories

No repository yet for this series. The Foundation’s llms.txt audit found no repo coverage for 25 of the 33 series, and this is one of them. See the organisation on GitHub: AGIFutureFoundation.

  • Metropolis-SmartCiti — Omega Steward liaison card omega.s31-aerospace-dao in agents/cards/ (ERC-8004 identity, x402 micropayments on Monad testnet, 2-of-3 human-steward governance). The card briefs human stewards; it never votes, enacts, moves treasury, or appoints.
  • Related, not owned: WorldForge-Browser’s README lists a Seattle aerospace industry training hub (IAM/UAW, 140-hour course) among its eight industry hubs. That hub is WorldForge content, not this series’ — it is listed here so a future DAO team can review it, not as a series asset.

Shared registry entries (the same for every series in the intended network — these are registry and tooling files, not a product for this series):

  • agi-corp-worlds — the fabric-and-agent registry. This series has a series directory there (worlds/s31-aerospace-dao/), but its founder focus is unset: the focus sheet records every focus as null, so the series is listed as awaiting a founder focus and no spec, zones, or agents have been written for it. Its spec metaprompt is marked not ready for the same reason.
  • Generated agent prompts and advisor contracts in the same repo (agents/prompts/ and agents/advisors/) — one generated prompt file and one scripted advisor contract per world, covering the series worlds. The three advisors per world are Host, Steward Liaison, and Alignment; advisors are scripted guides, not AI, and get no prompt by contract. The prompts are deterministic stubs held to a ten-point eval (umbrella present, every human-reserved action listed and marked Held for the Steward Council, every forbidden action listed, source cited, zone named, no personal data, under 6,000 characters) — and no model has run any of them.
  • DAO management pattern in the same repo (agents/dao.mjs) — one DAO team per world, seated in the eight agent roles the charter assigns to agents (research synthesis, task routing, proposal generation, operational coordination, progress tracking, monitoring, collaborator scouting, grant drafting). Proposals move draft → under review → enacted or declined, with steward transitions requiring a 2-of-3 steward quorum; no treasury is held and treasury.transfer is refused to everyone.

Get involved / contact

If you can help define, steward, or review this series — as a domain expert, a prospective steward, a researcher, or a reviewer — contact the Foundation at [email protected]. Say which series you are writing about, who you are, and what you can contribute; a human steward will reply. Agents writing on behalf of a human principal should put [Agent] at the start of the subject line and name their human principal, as described on the Foundation's home page. Agents may summarise, cite, and route inquiries; they may not commit the Foundation, move funds, or sign.

This is not an investment solicitation. No investment terms, no offering, no SAFE, no equity, no token, and no returns are described or offered on this page, and none should be inferred from it. Nothing on this page is legal, tax, or financial advice. If a future offering ever exists, it would be described in its own documents, reviewed by counsel, and dated — not announced on a series landing page.

Other series in this group: Mypet.AI · Lyka DAO · Genomic DAO · Genome.Blockchain · Metaverse DAO · Robotics DAO · Aerospace DAO · Solar DAO · InfoGurus