W3 Series S22 · Intended / Planned · AGI Future Foundation
Get.Delivery DAO
A planned DAO for delivery and logistics — getting things from where they are to where they are needed, named in the April 2026 internal W3 series list, and intended, not yet formed.
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 files reviewed, so this page does not claim tax-exempt status and does not claim that any donation is tax-deductible.
What this series is
Get.Delivery DAO is W3 Series S22, named in the April 2026 internal W3 series list. The name gives a clear planned focus in outline: delivery — the movement of goods from where they are to where they are needed — organised as a DAO. As with every series in this group, the name is the most the files reviewed say about it, and everything beyond the name on this page is a description of a planned focus implied by the name, marked as such.
The planned focus, as the name implies it, would be logistics in the broad sense: taking a request, finding the item, moving it, and confirming it arrived — with the record of each step kept in a way that the sender, the carrier, and the recipient can all check. Delivery is a chain of handoffs, and a chain is only as trustworthy as its weakest handoff. A DAO for delivery would, in principle, be a way of coordinating many independent carriers, vehicles, and drop points without putting all of the coordination in the hands of a single dispatcher — but that is a principle, not a system, and no system is claimed on this page.
What is not stated, and what a future mission statement would have to state, is almost everything that would make this a real operation: What is delivered — parcels, food, medicine, documents, something else? Over what distance — a neighbourhood, a city, a region? By what means — people, vehicles, drones, robots, or some combination? Who are the senders and recipients, and who are the carriers? What does the series charge, if anything, and who pays? None of those questions is answered in the files reviewed, and this page does not answer them by guessing. A delivery service with no stated cargo, range, or carrier is a name, not a service, and the page should read that way until the answers are written down.
The DAO element raises its own questions for a delivery operation, and they are worth stating early because they are the questions that decide whether the model can work at all. Who decides which deliveries are accepted and which are refused — for example, a delivery that is unsafe, illegal, or beyond the carriers' capacity? Who is responsible when a delivery is lost, damaged, or late — the carrier, the series, or nobody? Who holds the money between payment and delivery, and who releases it? In the intended programme-wide model, agents would operate day-to-day within human-set limits and humans would decide, sign, and move funds through a Steward Council. For delivery, the human decisions include the safety and liability rules, and they would need to be written down before a single parcel moves — not discovered after the first loss.
It is also worth saying what this series is not, on the evidence reviewed. It is not a courier company with vehicles on the road, it is not a food-delivery app with riders and restaurants, and it is not a drone programme. No vehicles, riders, restaurants, routes, or customers are named in the files reviewed for this series, and no delivery has been made by it. If any of those things ever exists, this page should be updated to name them, with dates and sources — and until then, the honest description is a planned focus, not an operating service.
Readers who have a delivery need should therefore not read this page as a place to place an order, and readers who have a delivery capability should not read it as a place to sign up as a carrier. Both should use the contact section below to say what they need or offer, so that a real mission statement, when it is written, can be written against real demand rather than imagined demand.
Metaverse connection
This series has no anchored metaverse fabric yet. That sentence is the whole of what can honestly be said about its metaverse connection today: no coordinates, no fabric JSON file, no hosted assets, and no RP1 attach are in the files reviewed for this series, and this page invents none of them.
Zero worlds are live on RP1. That is the position for the whole W3 programme as of the files reviewed, not a gap peculiar to this series, and it should not be read as a failure of this series in particular — it is simply where the programme stands. A series page that claimed a live world, a set of coordinates, or a fabric URL without a file to cite would be inventing a fact, and this page will not do that.
What would be needed for this series to gain a metaverse presence is concrete and checkable: a chosen location with published coordinates, a fabric JSON file describing the world, hosted assets (models, textures, and any interactive elements) that can actually be loaded, and an RP1 attach that can be opened and verified by a reviewer. Until all four exist and can be cited, the correct statement remains "no anchored metaverse fabric yet," and any future update to this section should name the coordinates, link the fabric file, and give the date the RP1 attach was verified — not merely assert that a world exists.
Whether this series even needs a metaverse presence is an open question, not a settled one. Some series are naturally spatial — a training ground, a clinic, a city, a delivery network — and some are naturally not. The decision should be made series by series, in writing, with a reason: either anchor a fabric because the work is better done in a shared spatial place, or record that the series works in documents, code, and human conversation and does not need a world. Either answer is defensible. What is not defensible is assuming a world exists because the programme talks about worlds in general.
For this series in particular, a metaverse presence would only make sense as a coordination layer — a shared map or dispatch space where requests, carriers, and routes could be seen together — and even that would be a complement to the physical work, not a substitute for it. A delivery DAO lives or dies on the physical movement of real things, and no virtual world can move a parcel. No coordinates, fabric, or RP1 attach are claimed here, and any future world for this series should be justified as a coordination tool for a real operation, with the operation described first.
What exists today vs. what is planned
What exists today
- A name and a series number (S22) in the April 2026 internal W3 series list.
- A planned focus implied by the name: delivery and logistics, governed as a DAO.
- The Foundation's filed nonprofit status and its intended W3 governance model, described on this page.
- No formed company, no designation, no bank account, no EIN, no vehicles, no carriers, no routes, no customers, and no deliveries for this series.
What is planned
- A written mission: what is delivered, over what distance, by what means, and for whom.
- Safety, liability, and payment rules, decided by humans and written down before any delivery moves.
- A Steward Council and named human stewards, with decision limits in writing.
- A carrier and recipient model: who carries, who receives, and what each is owed and owes.
- A metaverse decision: a coordination space with coordinates and a verifiable RP1 attach, or a written record that the work is physical and needs no world.
How it fits
This series sits in the W3 programme's logistics and physical-world group, and its closest neighbour is S30 Robotics DAO: if deliveries were ever made by robots or physical-AI agents, the boundary between a delivery DAO and a 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. Series S10 SmartCiti.X is the other natural neighbour, since a city-scale programme will always need to move things around a city, and a delivery series that never spoke to the city series would be planning in isolation.
Other related series include S8 Locator.X (finding things and places is the first half of delivering them), S12 ParkingSmart.X (vehicles need somewhere to stop), and S29 Metaverse DAO (if a coordination layer in a shared virtual space is ever wanted). None of those relationships is a partnership today. Each is a conversation and a written agreement for the future, if the series involved become active.
In tier terms, this series would belong to the commercial engine tier — the W3 Wyoming series network — under the Foundation's mission gate at the apex. The Foundation does not own the series in the way a parent company owns a subsidiary, and this page does not claim that it does. Any relationship would be set out in a written mission agreement, with the Foundation board remaining independent, as a California nonprofit board must.
Under the intended structure described in the Foundation's planning documents, a W3 series would be DAO-managed in its day-to-day operation: agents would operate routine work within limits set by humans, and a human Steward Council would decide, sign, and move funds. That is a plan, not a description of something operating today. No Steward Council for this series is named in the files reviewed, no operating agreement for this series is in the files reviewed, and no agent has authority to sign for, commit, or spend on behalf of this series or the Foundation.
The boundaries in that intended model are deliberately narrow. Agents would prepare work, draft documents, keep records, and coordinate — they would not enact doctrine or charters, hire or fire, offer securities, sign contracts, or move funds. Humans would execute every step that creates a legal or financial obligation. If this series ever moves from planned to active, those boundaries would need to be written down first, in the series' own governing documents, and approved by the Foundation board and by counsel — not assumed from this page.
Governance also means the Foundation's role stays a mission gate, not ownership in the ordinary commercial sense. The Foundation is a California nonprofit public benefit corporation, and its board must remain independent. Control over a series, if any is ever exercised, would be through written mission agreements, not through treating a nonprofit as a subsidiary of a for-profit head or a series as a pocket of the Foundation. That distinction matters, and it is why this page keeps saying "intended" and "planned" instead of describing a live reporting line.
What would need to happen next
The list below is the same honest checklist that applies to every planned W3 series: it is the work that would have to be done, in writing, before this series could be described as anything more than planned. It is not a roadmap with dates, and it is not a promise that any of it will happen.
- Confirm the series exists in law. A Wyoming SOS search for W3 LLC, and a written per-series designation for this series, would have to be produced. Until then, the series name is a name on an internal list, not a legal entity.
- Write the focus down. A one-page mission statement for this series, approved in writing by the Foundation board, stating what it will and will not do — so that later work can be checked against it instead of drifting.
- Name the humans. A Steward Council and a named human steward, with their roles, limits, and decision process written down. No series should operate on unnamed stewards.
- Settle the metaverse question. Either anchor a fabric with coordinates, a fabric JSON file, and hosted assets, and attach it to RP1 — or record in writing that this series has no metaverse presence and does not need one. Either answer is acceptable; an unexamined assumption is not.
- Separate money from the start. If the series ever holds funds, it would need its own bank account and ledger, its own EIN where required, and a written agreement with the Foundation. No pooling, no shared pot, no informal transfers.
- Publish the record. Designation, mission, stewards, and any metaverse anchor should be published or filed where a reviewer can check them, so that the next version of this page can replace "planned" with a dated, sourced fact.
None of those steps has a date on this page, because no date has been set in the files reviewed. A step with no date is a step still to be scheduled, not a step that is late — and this page will not invent a timeline to make the plan look further along than it is.
Proposed projects — for DAO review
These are proposals for the series DAO team to review. None is approved, funded, staffed, or scheduled.
The name gives a clear planned focus in outline: delivery, the movement of goods from where they are to where they are needed, organised as a DAO. The name is the most the files reviewed say about it. The proposals below are generic to that name-implied planned focus.
Scope paper
A one-page written statement of what delivery means for this DAO: which goods, which places, and which kinds of delivery are in scope, with boundaries stated. The paper would be approved by stewards before any delivery is planned. No such paper exists today.
What success would look like: A scope paper exists that the stewards have approved, stating what delivery covers here.
Reviewing team: the Get.Delivery DAO DAO
Status: PROPOSED — pending DAO team review
No funding, partner, or timeline yet.
Last-mile concept
A concept for getting goods the last distance to the person who needs them: how the final leg works, who carries it, and how a failed delivery is handled. The concept would be a design walkthrough, not a service. No delivery service is verified for this DAO.
What success would look like: A concept walkthrough exists showing how the last leg works, including how a failed delivery is handled.
Reviewing team: the Get.Delivery DAO DAO
Status: PROPOSED — pending DAO team review
No funding, partner, or timeline yet.
Courier fairness proposal
A proposal for fair treatment of couriers: pay, safety, rest, and respect, written before any courier is engaged. The proposal would set fairness as a requirement of any delivery work. No courier is verified for this DAO.
What success would look like: A fairness proposal exists covering pay, safety, rest, and respect for couriers, approved by stewards.
Reviewing team: the Get.Delivery DAO DAO
Status: PROPOSED — pending DAO team review
No funding, partner, or timeline yet.
Routing and reliability standard
A standard for reliable delivery: how routes are planned, how delays are communicated, and what happens when a delivery fails. The standard would be written before any delivery is promised. No such standard exists today.
What success would look like: A reliability standard exists covering routing, delay communication, and failed deliveries.
Reviewing team: the Get.Delivery DAO DAO
Status: PROPOSED — pending DAO team review
No funding, partner, or timeline yet.
Community delivery needs survey
A proposal to survey what a community needs delivered: which goods matter most, where they are needed, and what is missing today. The survey design would be written before any survey is run. No such survey is verified.
What success would look like: A survey design exists naming the questions, the audience, and how findings would be used.
Reviewing team: the Get.Delivery DAO DAO
Status: PROPOSED — pending DAO team review
No funding, partner, or timeline yet.
Code and repositories
No repository yet. The Foundation’s repo audit lists no repo coverage for Get.Delivery DAO, and this series has no project page in the Foundation site’s projects/ section. See the organisation on GitHub: AGIFutureFoundation.
Visit in VR
There is no playable world for this series yet, and no flagship fabric. What exists is a lobby entry in the Worlds-3D index: this series is listed there as s22-get-delivery-dao — a curated entry in the 544-world index, labelled in the lobby itself as “Lobby entry — not yet built as a playable world here” and “All 544 worlds are rp1:null (not live on RP1)”. Only seven flagship worlds are playable in the web 3D engine, and this series is not one of them.
- Foundation VR tour — the Foundation’s VR entry point.
- Worlds-3D lobby — 544-world index — search the index for
s22-get-delivery-daoto find this series’ lobby entry.
Do not read the lobby entry as a world you can walk: it is an index listing with the series’ real status, not a built space. A playable world for this series would need a chosen location with published coordinates, a fabric JSON, hosted assets, and a live render check — none of which exists yet.
Get involved / contact
To ask about this series, to correct something on this page, or to propose work that fits its planned focus, contact the Foundation at [email protected]. Please say who you are, who you represent if anyone, and what exactly you are proposing — a general expression of interest is welcome, but a specific proposal with a named human behind it can be answered far more usefully.
This page is not an investment solicitation, not an offering of any security, and not an invitation to invest. It states no terms, no price, no valuation, no return, and no deadline, and none should be read into it. If a future offering ever exists for this series or any related entity, it would be made only in separate written offering documents, prepared with counsel, and only to investors eligible under the applicable rules. Nothing on this page is legal, tax, or financial advice.
Corrections are welcome and will be treated as part of the record: if you hold a filing, a designation, a signed agreement, or a live metaverse anchor for this series, send it to the address above and this page can be updated to cite it, with its date and source. Until such a document is produced, the honest status on this page stands.