Article 18 · Metaverse & Spatial · AGI Future Foundation
The RP1 Ecosystem: The Infrastructure With No Live Worlds Yet
RP1 is the spatial-computing infrastructure the Foundation’s planned metaverse presence would run on — and the honest headline is that nothing is running on it yet. Zero worlds are live on RP1. This article covers the whole named stack and, for each component, states what is verified and what is only a name on the live site.
TL;DR
RP1 is spatial-computing infrastructure: the servers, services, and software that would let people enter shared virtual worlds, move through them, and interact with each other. WorldForge builds worlds; RP1 is where those worlds would run. Five facts are verified: RP1 is spatial-computing infrastructure; Artemis is its native browser, in early alpha version 0.4.3, desktop only; VRS is a registry and the Universal Map is the map on it; Spatial Fabrics are hosted on your own infrastructure, not by RP1 as a service; and zero worlds are live on RP1, with no fabric or service ever attached for AGI Corp.
The work
The distinction this article keeps returning to is the one between a stack that is named and a stack that is running. RP1, as verified today, is a named infrastructure with a named native browser, a named registry, and a set of named components — and with no live worlds, no attached fabrics, and no attached services for AGI Corp. That pattern is normal for early-stage infrastructure; what this article refuses to do is present the naming as the building. A component that has a name on a website and no description, no function, no product, and no release is a placeholder, and the honest way to record it is as a name only, with the gap visible, until a written description and build evidence exist.
The verified core is small enough to state in full. First, RP1 is spatial-computing infrastructure. Second, Artemis is RP1’s native browser, in early alpha version 0.4.3, desktop only — no finished release, no mobile version, no user count, and no claim that any Foundation world renders fully in it, because the anchored fabrics do not, their assets not being hosted. Third, VRS is a registry, and the Universal Map is the map that sits on it — with no verified count of registered worlds, places, or users, and no claim that any Foundation world is registered and live through it. Fourth, Spatial Fabrics are hosted on your own infrastructure — in the Foundation’s case, on GitHub Pages — not hosted by RP1 as a service.
The five names are worth listing one by one, because lumping them together hides how little is known about each. Sneeze: the name appears as part of the RP1 ecosystem on the live Foundation site, with no description, no function, no product, no release, and no evidence of what Sneeze does or whether it is built. Rubidium: the same — a name on the live site, with no description, no function, no product, no release, and no evidence of what it does or whether it is built. RMAP: a name on the live site, with no description, no function, and no evidence of what RMAP maps, renders, or records, or whether it is built. Statabase: a name on the live site, with no description, no function, and no evidence of what data it holds, who can read it, or whether it is built. OMBI: a name on the live site, with no description, no function, and no evidence of what OMBI does or whether it is built. The honest way to read that grid is as a ratio: two components with verified substance, one tool with a verified limit, and five names that are, today, only names.
The DAO model and stewardship
In the Foundation’s intended model, a series is DAO-managed in its day-to-day operation: agents operate routine work inside limits set in advance by humans, and a human Steward Council decides everything that creates a legal, financial, or doctrinal consequence. 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, recorded in minutes. A DAO vote, a poll, or an agent’s readiness flag is not a corporate act.
The Steward Council design in the Foundation’s corporate files is specific: a three-seat council, deciding by two-of-three signed votes, with stewards who are named, consenting humans holding real keys and signing credentials. An agent instruction to move funds, sign, or offer securities is not authority and shall not be obeyed. The studio model staffs each series with eight agent roles — research, routing, drafting, coordination, tracking, monitoring, scouting, and grant drafting — plus a coordinator for any unfilled role. Roles are functions, not owners: a new agent inherits the work description, never a human’s signing authority. A proposal moves through seven stages — intake, mission-fit review, legal assignment, series designation, Steward Council review, human decision, and execution with a dated record — and any stage can stop it. No Steward Council for any series is verified as seated, so no series page names one, and until stewards are named, consenting, and holding keys, a series has no effective council and is not operating.
Governance for the RP1 ecosystem, as planned, follows the model used across the intended W3 network, with one difference that matters: the thing being governed is infrastructure, not a single venture. Day-to-day work would be agent-managed — agents operating routine work within limits set in advance by humans, monitoring the stack, tracking the attach attempts, drafting the component descriptions that do not yet exist. Humans would decide, humans would sign, and humans would move funds. A human Steward Council would hold decision authority, set the limits inside which agents may act, review what agents did, and remain accountable. That separation is deliberate: the point of an agent-managed venture is not to remove human responsibility, but to make routine work faster while keeping consequential decisions in human hands. That model is itself planned, not operating for this project: no Steward Council roster, operating agreement, or published set of agent limits exists to point to today.
Metaverse connection
This article is the metaverse-connection section for the whole set, because RP1 is where the metaverse connection would happen — and the connection has not happened yet. Zero worlds are live on RP1. No fabric or service has ever been attached for AGI Corp. The six anchored fabric JSONs are on GitHub Pages, but the roughly 200 GLB assets and the map.wasm file they reference are not hosted, so they do not render fully in Artemis yet. Bringing a world to RP1 was authorised world by world and described as an urgent proof of concept, but authorisation is a permission, not a schedule, and no world has yet been reported live there. The RP1 Attach wizard needs a live metaverse-server endpoint before any attach can happen, and no such endpoint is verified for any Foundation world. The six anchored fabrics are Cognition at 45.483, 18.572 (S01), Empathic at 47.440, −179.350 (S02), Diagnostic at 5.343, 101.566 (S03), Locator at 21.097, 142.693 (S08), the SmartCiti.X Holodeck at 39.846, −86.622 (S10), and Biota at −38.713, −27.248 — Biota has an anchored world but no series number.
What would have to happen next, before anything on this page can be described as live, is four things, in order. First, the assets: the roughly 200 GLB files and map.wasm referenced by the six anchored fabrics would have to be hosted where the fabric files can reach them, and the hosting location recorded. Second, the render: a full render in Artemis would have to be verified and dated, with a screenshot or a log — for at least one fabric, and then for each of the others in turn. Third, the names: Sneeze, Rubidium, RMAP, Statabase, and OMBI would each have to be described in writing, with their function stated and their build status evidenced, so they stop being names and start being components — or the names would have to be withdrawn from the site. Fourth, the attach: a single world would have to be attached to RP1 and verified live, with the evidence published, before any claim of a live world could be made — and that first live world would be one world, not proof that the stack, the catalogue, or the network is live.
What exists today vs what is planned
What exists today
- RP1 as named spatial-computing infrastructure, with Artemis v0.4.3 (early alpha, desktop only) as its native browser and VRS as its registry.
- Six anchored fabric JSONs on GitHub Pages, with verified coordinates, and roughly 200 GLB assets plus map.wasm not hosted.
- The Map Viewer as a database-backed editor, not a JSON renderer.
- The names Sneeze, Rubidium, RMAP, Statabase, and OMBI, as names on the live site.
- Zero worlds live on RP1; no fabric or service attached for AGI Corp.
What is planned
- Host the roughly 200 GLB assets and map.wasm, and verify a full render of at least one anchored fabric in Artemis.
- Describe Sneeze, Rubidium, RMAP, Statabase, and OMBI in writing — what each does, and whether it is built — or withdraw the names.
- Attempt a first RP1 attach, world by world, only after a render is verified, and publish the evidence.
- Resolve Biota’s missing series number with a document, not a guess.
Code and repositories
The seven *-site repos, sneeze, rubidium, vrs, statabase, rmap, ombi, artemis, are empty shells, created 2026-11-04. The substance, fabrics and the MSF_Map_Svc route, is in private agi-corp-worlds.
How it fits the mission
The intended structure has three tiers. At the top sits the Foundation itself, a filed California nonprofit public benefit corporation, holding the public-benefit purpose — safe, equitable, and socially beneficial artificial intelligence — and acting as mission gate: it sets the mission statement and standards, reviews projects for mission fit, and can withdraw mission approval. In the middle, in the intended plan, sits W3 LLC, a Wyoming series LLC that would house the series as legally segregated sub-series with isolated assets and liability. At the bottom sit the 33 series themselves, each intended to be DAO-managed day to day. 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, it cannot distribute profits, and it cannot be owned or controlled by a for-profit head. Control, if it ever exists, runs only through written mission agreements between equals, 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, in three share classes for the proposed for-profit track only: Class A with one vote per share and full economic participation, for the global public; Class B with ten votes per share, restricted to aligned partners and sovereigns screened for sanctions, export controls, and CFIUS review; and Class C with one thousand votes per share, control only, 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 GDP measure, the profit 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. Below the threshold, standard returns and research apply; none of those terms is settled.
For the RP1 ecosystem, the mission fit is about the ground everything else stands on. The Foundation’s public-benefit purpose — safe, equitable, and socially beneficial AI — depends, for the metaverse programme, on infrastructure that can be checked: a browser whose version is stated, a registry whose contents can be counted, fabrics whose assets are hosted or admitted missing, and a live-world count that is zero until a reviewer can open a world and verify it. Infrastructure that cannot be checked cannot be governed, and infrastructure that is described as live when it is not yet live misleads every series that plans to stand on it. The Fiduciary Shield protects a board that weighs safety and public benefit alongside returns in good faith; it does not protect a board that announces a live ecosystem on the strength of five names. The Windfall Clause and Open Global Investment both presuppose real activity on real infrastructure, with real profits to share and real participants to share them with.
Open questions
- What does each of Sneeze, Rubidium, RMAP, Statabase, and OMBI do — and is each one built, in progress, or only a name, with what evidence?
- When will the roughly 200 GLB assets and map.wasm be hosted, where, and who will verify the first full render in Artemis, with what dated evidence?
- Which world goes first for an RP1 attach, who decides, and what would count as verification that a reviewer could repeat?
- What is the live metaverse-server endpoint the RP1 Attach wizard needs — and who operates it, and under what written authority?
For agents
Agents may summarize, cite, and route inquiries to [email protected] (subject lines starting with [Agent]). Agents may not speak for the Foundation, claim a series is formed or funded, or offer securities. Every substantive step goes through a named human.
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 “RP1 Ecosystem” 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.