Skip to content
AGI Future Foundation PBC

W3 Series S19 · Intended / Planned · AGI Future Foundation

Moscone.X

A named W3 series whose focus is not stated in the files reviewed — listed as S19, and intended, not yet formed.

StatusContact the Foundation

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.

← BioDAO.blockchain DAO  |  CMMC →

What this series is

Moscone.X is W3 Series S19, named in the April 2026 internal W3 series list. That is, honestly, almost everything the files reviewed say about it. The name "Moscone.X" gives no focus in the way that "Diagnostic.X" or "Get.Delivery DAO" give a focus, and no description, mission, project, person, place, product, or partner for this series appears in the files reviewed. This page therefore says so plainly, rather than filling the gap with invention — and it is the thinnest kind of page in this group for exactly that reason.

It would be easy, and wrong, to guess. A reader might associate the name "Moscone" with a person, a place, or a building, and then write a page about whichever association came to mind first. This page does none of that. No association is stated in the list, no expansion or explanation of the name is given there, and no site copy, article, or planning document reviewed here explains what "Moscone" means for this series. To pick one association and present it as the series' focus would be to invent a fact and then build a page on it. The honest page is the short one: a name, a number, a status, and a list of the questions that would have to be answered before anything more could be said.

What can be said, without guessing, is what the ".X" suffix and the series number imply about the shape of the thing, as opposed to its subject. The ".X" series in the W3 list are the programme's named ventures or projects, each intended to become a liability-isolated series under W3 LLC, DAO-managed day-to-day with humans deciding, signing, and moving funds through a Steward Council. That shape is planned for the whole programme and is described in the "How it fits" section below. It says nothing about what Moscone.X would do — only how it would be governed if it ever did anything.

The questions that would have to be answered before this page could grow are simple to list and impossible to answer from the files reviewed: What does "Moscone" refer to? What field, problem, or community would the series serve? Who proposed it, and why? What would its first piece of work be, and who would do it? Is there an existing project, place, or partnership behind the name, or is the name a placeholder for an idea not yet written down? Each of those questions has a named human who could answer it, and until one of them does, in writing, this page should stay as it is: a name with its status stated, and no more.

That restraint is not a failure of the page; it is the page doing its job. A series page that invented a focus for Moscone.X would mislead everyone who read it — a potential collaborator would arrive expecting one thing and find another, a reviewer would cite a focus that never existed, and the real project, if one exists behind the name, would have to spend its first months correcting a public record it never wrote. A page that says "not stated" costs nothing and can be corrected in a single sentence the moment a real answer arrives.

Until then, the useful work for this series is not writing more about it, but asking the question: who named it, and what did they mean? The contact section at the foot of this page is the route for that answer. If you hold it — a mission statement, a description, a link to an existing project, or even a one-sentence explanation of the name — send it, and this page can be updated to cite it, with its source and date.

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, there is not even a basis to speculate about what a metaverse presence might be for. A spatial world serves a purpose — a place to meet, to train, to show, to build — and no purpose has been stated for Moscone.X, so no world can be described, even as a plan. The metaverse decision for this series comes after the focus decision, not before it: first say what the series is for, then ask whether a shared spatial place would help it do that, and only then consider coordinates, a fabric JSON, hosted assets, and an RP1 attach.

What exists today vs. what is planned

What exists today

  • A name and a series number (S19) in the April 2026 internal W3 series list.
  • The Foundation's filed nonprofit status and its intended W3 governance model, described on this page.
  • No stated focus, no description, no mission, no project, no partner, and no person named for this series in the files reviewed.
  • No formed company, no designation, no bank account, no EIN, and no metaverse fabric for this series.

What is planned

  • A one-sentence explanation of the name, and a one-page mission statement, from whoever proposed the series.
  • A named field, problem, or community the series would serve, and a first piece of work.
  • A Steward Council and named human stewards — only once there is something to steward.
  • A metaverse decision, only after the focus is stated: a fabric with coordinates and a verifiable RP1 attach, or a written record that no world is needed.

How it fits

Because no focus is stated, no related series can honestly be named for Moscone.X. To list neighbours would be to guess at a relationship on the basis of a name that has not been explained, and this page will not do that. The series belongs, in tier terms, to the commercial engine tier — the W3 Wyoming series network — under the Foundation's mission gate at the apex, in the same planned shape as every other series in the list. That is a statement about its intended legal and governance shape, not about its subject.

The governance model that would apply, if the series ever becomes active, is the programme-wide intended model described below: DAO-managed day-to-day, with agents operating within human-set limits, and humans deciding, signing, and moving funds through a Steward Council. No council for this series is named, no DAO vote or treasury is claimed, and no agent has authority to act for it today.

The most useful "fit" statement for this series is therefore a procedural one: Moscone.X fits the programme as a named, numbered, unfilled slot — a place held in the list for an idea whose description has not yet been written down. Its fit with any other series will be decided when its focus is stated, and the page should be updated then, with the relationships named and sourced, rather than now, by guesswork.

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.

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.

No verified description exists for this series beyond its name and its number in the April 2026 internal W3 series list. The name Moscone.X gives no focus in the way that Diagnostic.X or Get.Delivery DAO give a focus, and no description, mission, project, person, place, product, or partner appears in the files reviewed. The proposals below are therefore generic to the name only, and are framed as research and scoping work rather than as a domain plan.

Name and scope research proposal

A proposal to research what Moscone.X should mean: gathering the options, checking what the name has been used for inside the Foundation, and writing up the findings for the DAO team. The research would be a written note, not a decision. No such research exists today.

What success would look like: A research note exists with options for what Moscone.X could mean, ready for the DAO team to review.

Reviewing team: the Moscone.X DAO

Status: PROPOSED — pending DAO team review

No funding, partner, or timeline yet.

Scope definition paper

A one-page scope paper to be written once the research lands, stating what this series covers and what it does not. The paper would be approved by stewards before any building begins. No such paper exists today.

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

Reviewing team: the Moscone.X DAO

Status: PROPOSED — pending DAO team review

No funding, partner, or timeline yet.

Steward questions list

A list of questions the stewards must answer before this series can do substantive work: what is in scope, who the stewards are, what agents may and may not do, and how money would be held. The list would be a working document for the DAO team. No such list exists today.

What success would look like: A questions list exists covering scope, stewards, agent limits, and money handling, ready for stewards to answer.

Reviewing team: the Moscone.X DAO

Status: PROPOSED — pending DAO team review

No funding, partner, or timeline yet.

Placeholder governance draft

A minimal governance draft for a series with no stated focus: who decides, how decisions are recorded, and what must wait for a human signature. The draft would be a starting point, not a finished operating agreement. No governance document exists for this series.

What success would look like: A minimal governance draft exists covering decisions, records, and human signatures.

Reviewing team: the Moscone.X DAO

Status: PROPOSED — pending DAO team review

No funding, partner, or timeline yet.

First-focus options paper

A paper laying out candidate focuses for this series, with the case for and against each, for the DAO team to review. The paper would recommend nothing on its own. No such paper exists today.

What success would look like: An options paper exists with candidate focuses and the case for and against each.

Reviewing team: the Moscone.X DAO

Status: PROPOSED — pending DAO team review

No funding, partner, or timeline yet.

Code and repositories

No code repository for this series is verified. The Foundation’s repo audit lists no repo coverage for Moscone.X, and this series has no project page in the Foundation site’s projects/ section. One related file is listed in the WorldForge-Browser repo: a per-series tutor prompt, worldforge/out/training/tutors/s19-moscone-x.md. It has been identified by name only — its contents have not been read, so nothing from it is quoted or described here. 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 s19-moscone-x — 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.

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.