W3 Series S21 · Intended / Planned · AGI Future Foundation
Incubator DAO
A planned DAO for incubating early ventures and builders — 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
Incubator DAO is W3 Series S21, named in the April 2026 internal W3 series list. The name gives a clearer planned focus than most in this group: an incubator is a place and a programme that helps early ventures and builders get started — with space, training, mentorship, and time — and a DAO is the intended governance shape for running it. 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 the earliest stage of building: people with an idea and the beginnings of a team, who need a structured period of work — weeks or months, not days — in which to test the idea, build a first version, learn from users, and decide whether to continue. An incubator, in the ordinary sense, provides some combination of a place to work, a curriculum or training programme, experienced people to learn from, and a cohort of other builders going through the same process at the same time. Which of those this series would provide, to whom, and on what terms, is not stated in the files reviewed, and this page does not invent an answer.
It is worth distinguishing, carefully, what an incubator is from what it is not. An incubator is not a funder, not an employer, and not a school. It does not own the ventures it hosts, it does not guarantee them customers or investment, and it does not confer a credential simply for having taken part. Any future mission statement for this series would need to say that in writing, so that nobody joins expecting a guarantee the series cannot give.
The DAO element adds a second question that a future governing document would have to answer: who decides who gets in, what support they receive, and when a venture graduates, pauses, or leaves? In the intended programme-wide model, agents would operate the day-to-day work within human-set limits, and humans would decide, sign, and move funds through a Steward Council. Admissions, in particular, are a human decision — who is let in, on what criteria, and with what commitments on both sides — and no agent should be making that call alone. No admissions criteria, cohort, resident, or graduate is claimed for this series anywhere on this page, because none exists in the files reviewed.
Two neighbouring ideas in the Foundation's wider plans are worth naming, without claiming a relationship that has not been written down. The SmartCiti.X plans describe incubator housing — places for founders, builders, trainees, and instructors connected to a facility to live for a defined residency, under a residency agreement and a board-set fee, with zoning and safety in place before anyone moves in. The BuilderSpace tour is a separate programme of hackathon and onboarding events. Incubator DAO, if it ever becomes active, would need a written agreement saying how it relates to each of those — whether it runs a programme inside SmartCiti.X housing, whether it is separate from BuilderSpace, or whether it is something else entirely. Until such an agreement exists, the three should be treated as separate ideas that happen to use the word "incubator," not as parts of one programme.
Readers should therefore treat this page as a direction with a name, not a programme with a start date. It says: here is what an incubator DAO would be for, here is what is not yet decided, and here is what would have to be written down before anyone could apply, join, or be housed. That is the most honesty allows at this stage.
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 is easy to imagine and still does not exist: a shared virtual space where a cohort could meet, present work, and learn together, especially if its members were spread across different places. Imagining it is not the same as having it, and no coordinates, fabric, or RP1 attach are claimed here. If a virtual cohort space were ever wanted, it would need the same four things as any other series world — coordinates, a fabric JSON, hosted assets, and a verifiable RP1 attach — and it would need to be built for the cohort's actual use, with the people it serves named, rather than as a demonstration.
What exists today vs. what is planned
What exists today
- A name and a series number (S21) in the April 2026 internal W3 series list.
- A planned focus implied by the name: incubating early ventures and builders, 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 cohort, no residents, no admissions criteria, and no programme dates for this series.
What is planned
- A written mission: who the incubator serves, what support it provides, and what it explicitly does not promise.
- Admissions criteria, cohort structure, and graduation or exit rules, decided by humans and written down.
- A Steward Council and named human stewards, with decision limits in writing.
- Written agreements with SmartCiti.X housing and with BuilderSpace, if any relationship is intended — or a written record that there is none.
- A metaverse decision: a cohort space with coordinates and a verifiable RP1 attach, or a written record that the programme works in person and in documents and needs no world.
How it fits
This series sits in the W3 programme's venture-building group, and its most important relationship to settle is with SmartCiti.X, Series S10. The SmartCiti.X plans include incubator housing and training facilities, and an Incubator DAO that ran a programme without any agreement with the series that holds the housing would be planning in a vacuum The two ideas belong together in planning, and apart in law, until a written agreement joins them.
Other related series include S29 Metaverse DAO (if a cohort ever meets in a shared virtual space), S1 Cognition.X and S2 Empathic.X (whose work a cohort venture might build on), and the Delaware cohort series, which are a separate, later structure for cohorts and must not be confused with this W3 series. The Foundation site’s feature page The Cohort Machine describes both Incubator DAO (Series S21) and the Delaware cohort series model; it states the Delaware cohort master LLC is intended, not verified as filed, and that no criteria, programme, or date is verified for Incubator DAO. The BuilderSpace tour, though not a W3 series, is the other programme that uses the incubator word, and its relationship to this series — if any — would also need to be written down. None of those relationships is a partnership today.
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 clearer planned focus than most: an incubator is a place and a programme that helps early ventures and builders get started, with space, training, mentorship, and time, and a DAO is the intended governance shape for running it. The name is the most the files reviewed say about it. The proposals below are generic to that name-implied planned focus.
Incubator model paper
A paper stating what incubation means here: space, training, mentorship, and time, and how the DAO would provide each. The paper would be approved by stewards before any venture is accepted. No such paper exists today.
What success would look like: A model paper exists that the stewards have approved, stating what incubation means here.
Reviewing team: the Incubator DAO DAO
Status: PROPOSED — pending DAO team review
No funding, partner, or timeline yet.
First cohort design
A design for a first small cohort of builders: how many, for how long, what they receive, and what is expected of them. The design would be written for the DAO team to review before any cohort opens. No cohort is verified for this DAO.
What success would look like: A cohort design exists naming size, length, support offered, and expectations, approved by stewards.
Reviewing team: the Incubator DAO DAO
Status: PROPOSED — pending DAO team review
No funding, partner, or timeline yet.
Mentorship principles
Written principles for mentors: what a mentor does, what a mentor never does, and how a builder asks for a different mentor. The principles would be agreed before any mentor is appointed. No mentor is verified for this DAO.
What success would look like: A principles draft exists that the stewards have approved, covering what mentors do and how builders can change mentors.
Reviewing team: the Incubator DAO DAO
Status: PROPOSED — pending DAO team review
No funding, partner, or timeline yet.
Selection criteria proposal
A proposal for how ventures would be chosen: stated criteria, who applies them, and how a declined venture is told why. The proposal would be written before any application opens. No such criteria exist today.
What success would look like: A criteria paper exists with stated selection criteria and a process for telling declined ventures why.
Reviewing team: the Incubator DAO DAO
Status: PROPOSED — pending DAO team review
No funding, partner, or timeline yet.
Graduation and follow-on note
A note on what happens when a venture leaves the incubator: what support continues, what ends, and how the DAO stays in touch. The note would be written before any venture graduates. No such note exists today.
What success would look like: A graduation note exists describing what continues, what ends, and how the DAO stays in touch.
Reviewing team: the Incubator 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 Incubator DAO, and this series has no project page in the Foundation site’s projects/ section. The related reading on this site is a feature page, not a repository: The Cohort Machine describes Incubator DAO (Series S21) and the Delaware cohort series model. 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 s21-incubator-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
s21-incubator-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.