Article Category 4 · AGI Future Foundation
Robotics & Physical AI
Physical AI is AI that acts in the world: it moves, lifts, drives, handles materials, and works alongside people. When it fails, the failure is physical, not just informational. This category is about the three series that would govern that failure mode — and about the standards they would have to write before a single machine moves.
What this category is
This category gathers the three articles about the physical world: Get.Delivery DAO (S22), Robotics DAO (S30), and Aerospace DAO (S31). All three are W3 series, named in the April 2026 internal W3 series list, and all three are intended and planned, not formed, funded, or offered. They belong together because they share a failure mode that the rest of the programme does not: a wrong answer in software is a wrong answer, but a wrong action by a machine is a broken object, a damaged workplace, or an injured person. That difference changes everything about how the series must be governed — the standards come first, the pilot is small, the review is published, and the power to refuse or halt a deployment is the core of the mandate.
The three series sit at different points on the same spectrum, and the spectrum is worth naming. Get.Delivery DAO is the thinnest: only the name and number are verified, and what is delivered, over what distance, by what means, and for whom are all unwritten. Its questions are the logistics questions — acceptance, liability, payment, and the record of each handoff. Robotics DAO is the fullest series in this group, chosen by Mike, and the Foundation’s site describes it, as site copy, as governing commercial deployment of robotic and physical-AI agents — but even it has no deployed robot, no customer, no site, and no pilot on record. Aerospace DAO is thin like the first, and the most constrained of the three: flight is already one of the most regulated human activities on earth, and any AI that touches it enters that regulatory world rather than displacing it. The category therefore reads as a progression from the most open question to the most constrained one, with the same governance discipline applied to each.
The second theme is the boundary between series. The three do not live in separate worlds; they overlap, and the overlaps would need written agreements. If deliveries were ever made by robots, the boundary between Get.Delivery DAO and Robotics DAO would need to be written down first — which series owns the vehicle, which owns the route, and who is liable when something goes wrong. Robotics DAO and Aerospace DAO both govern physical AI, but aerospace adds certification and airspace, and its failure modes are less forgiving: a ground robot can be stopped, while an aircraft often cannot. SmartCiti.X (Series 10) is the neighbour that touches all three, since a city-scale programme needs to move things, train people, and site machines — but its proposed corporation plans are a separate proposed corporation, not any of these series, and no part of them has been formed, funded, or offered. None of these relationships is a partnership today. Each is a conversation and a written agreement for the future, if the series involved become active.
The third theme is labour. Machines that act in the world act in workplaces, and the people whose workplaces gain robots deserve a say in how deployment happens. Any claim about training or jobs would need a signed agreement with a real workforce body before it is stated, and every deployment would need a human accountable on site, by name, because a DAO cannot be present when a machine fails. That is not a footnote to the governance model; it is part of the model. The Steward Council design — three seats, two-of-three signed votes, named consenting humans holding real keys — exists precisely so that accountability has a name attached to it when the machine, and not just the document, is at stake.
The articles in this category
Three articles, each 2,000–2,500 words, each built only from its landing page and the Foundation’s governance and operations material. Read them in order, or start with the one whose question is yours.
- Article 19 · Get.Delivery DAO (S22) — moving things to people — a chain of handoffs whose acceptance, liability, and payment rules would have to be written before a single parcel moves.
- Article 20 · Robotics DAO (S30) — governing commercial deployment of robotic and physical-AI agents — the fullest series in this set, chosen by Mike, still with no deployment on record.
- Article 21 · Aerospace DAO (S31) — flight AI where the safety bar is highest — certification and airspace before any product roadmap, and a lane that has not yet been chosen.
How the category fits the mission
The intended structure has three tiers. At the top sits the Foundation itself, a filed California nonprofit public benefit corporation (Entity No. B20260196664, Articles filed 2026-04-24, EIN assigned 2026-05-07), holding the public-benefit purpose — safe, equitable, and socially beneficial AI — and acting as mission gate. In the middle, in the intended plan, sits W3 LLC, a Wyoming series LLC that would house the series as legally segregated sub-series. At the bottom sit the 33 series themselves, each intended to be DAO-managed day to day, with a human Steward Council deciding, signing, and moving funds. Only the top tier is verified as filed. The Foundation as filed is a nonprofit: it cannot offer equity, a SAFE, or a profit share, and it cannot be owned or controlled by a for-profit head. Control, if it ever exists, runs only through written mission agreements, with the Foundation’s board remaining independent.
Three mechanisms are meant to interlock across that structure. The Fiduciary Shield is an expanded business-judgment protection for benefit-considering decisions, under California Corporations Code sections 14620–14621, with an annual benefit report under section 14630 — not immunity, and not a wall around a company. Open Global Investment is the proposed framework that decouples economics from control, expressed in three share classes for the proposed for-profit track only: Class A, one vote per share with full economic participation, for the global public; Class B, ten votes per share, restricted to aligned partners and sovereigns screened for sanctions, export controls, and CFIUS review; and Class C, one thousand votes per share, control only with no economic participation, held exclusively by the Foundation. The Windfall Clause is the legal pre-commitment, hardwired before profits, under which returns above a threshold — a percentage of global GDP, with the percentage, the measure, and the scope all still blank for counsel — would flow to humanity through global public goods, healthcare access, energy infrastructure, and technological self-determination. For this category, the mission test is the refusal power: a deployment governor that refused an unsafe deployment, even when the deployment was profitable, would be doing exactly what the Shield is designed to protect. A governor that waved deployments through would be doing the opposite, whatever its charter said.
The Foundation’s fundraising is donation and grant only. No article in this category is an offering, and none promises a price, terms, or a return. Suggested valuations appear only where a landing page already states them, and none is added here. The stewardship rule applies to every article in the category alike: agents operate day-to-day work within human-set limits, and humans decide, sign, and move funds. Agents never sign, move funds, hire or fire, offer securities, or enact doctrine. No Steward Council for any series is verified as seated. None of the three series has an anchored metaverse fabric yet, and zero worlds are live on RP1.
How to read this hub
Read the status banner first, on every article. It is the same sentence for all three series in this category — named in the April 2026 internal W3 series list, with W3 LLC formation and per-series designation not verified in filings. “Commercial deployment” is a planned mandate for Robotics DAO, not a track record: no deployment, customer, site, order, or pilot is verified for any series in this category. Simulation results, if a training world is ever built, must never be presented as real-world deployment evidence — and in aerospace, simulation results must never be presented as certification evidence either.
If you hold a document that changes something stated here — a filing, a designation, a signed agreement, a deployment standard, a pilot review, or a safety case with a date and an issuing authority — send it to [email protected] and the relevant article can be updated to cite it. Until such a document is produced, the honest status on these pages stands. The preceding article in the sequence is Article 18 (RP1 Ecosystem), which closes the previous category, and the following article is Article 22 (Blockchain), built by another builder and linked from Article 21.
Contact
To ask about this topic, correct something on this page, or propose work that fits it, write to [email protected]. Say who you are, who you represent if anyone, and what exactly you are proposing, and include “Robotics & Physical AI (Category 4)” in the subject line. A reply, if one comes, will come from a human.
What this page is not. This page is not an offer to sell securities, not an invitation to invest, and not a solicitation of funds. There is no price, no terms, and no return promised here, because there is nothing offered here. The Foundation as filed is a nonprofit public benefit corporation: its fundraising is donation and grant only, and no donation is presented as tax-deductible, because no IRS 501(c)(3) determination letter is in the files. If a future offering ever exists for a related entity, it would be made only in separate written offering documents, prepared with counsel. Nothing on this page is legal, tax, or financial advice.