AGI Future Foundation · Projects · Infrastructure
RP1 Ecosystem
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. No fabric or service has ever been attached for AGI Corp. The six anchored fabric files are published 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. This page covers the whole named stack — Sneeze, Rubidium, Artemis, VRS / Universal Map, RMAP, Statabase, and OMBI — and for each component it states what is verified and what is only a name on the live site.
What this is
RP1 is spatial-computing infrastructure: the servers, services, and software that would let people enter shared virtual worlds, move through them, and interact with them and with each other. In the Foundation's architecture it is the ground the metaverse presence would stand on. WorldForge, described on its own page, builds worlds; RP1 is where those worlds would run. The distinction matters, because a world can be built without being live, and a stack can be named without being attached. 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.
The stack's components are listed below, one by one, each with a verified column and a name-only column. The components closest to a user — the browser, the viewer, the map — carry the most verified detail, while the services named only on the live site carry the least. That pattern is normal for early-stage infrastructure; what this page refuses to do is present the naming as the building.
The filing facts that anchor every page in this section are the same. AGI Future Foundation is a California Nonprofit Public Benefit Corporation, Entity No. B20260196664, with Articles filed on 2026-04-24 and Secretary of State approval on 2026-04-30. Its Employer Identification Number was assigned on 2026-05-07. No IRS 501(c)(3) determination letter is in the files reviewed for this site, so no page here claims that the Foundation is tax-exempt, and no page claims that any donation to the Foundation is tax-deductible. Nothing on this site is legal, tax, or financial advice.
One fork in the Foundation's materials should be known to every reader. The live site calls the organisation a “PBC” in the for-profit benefit-corporation sense, and some papers describe a for-profit benefit-corporation track, with equity, a SAFE, and a priced raise. The filed entity is a nonprofit public benefit corporation — a different legal form: a filed nonprofit cannot offer equity, a SAFE, or a profit share, and it cannot be owned or controlled by a for-profit head. This site follows the filed status and notes the site label where relevant, rather than presenting the two as the same entity. Counsel would have to choose one track in writing before any solicitation. Being named on a website, in an internal list, or in a plan is not the same as being formed: a filing, a bank account, an EIN, a signed agreement, a customer, or a dollar of revenue would each be a separate, verifiable fact, and none is claimed here unless the page cites the document, the date, and the issuing authority.
The verified core
Five facts about RP1 are verified, and they are the frame for everything else on this page. First, RP1 is spatial-computing infrastructure. Second, Artemis is RP1's native browser, in early alpha version 0.4.3, desktop only. Third, VRS is a registry, and the Universal Map is the map that sits on 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. Fifth, and most important, zero worlds are live on RP1: no world has been verified live there, and no fabric or service has been attached for AGI Corp.
Two further verified facts belong in the same frame. The Map Viewer is a database-backed editor, not a JSON renderer: it edits the database that holds map data, and it does not render a world from a JSON file. And the six anchored fabric JSONs are on GitHub Pages, but approximately 200 GLB assets and map.wasm are not hosted: the fabric files are reachable, the assets they reference are missing, and the worlds therefore do not render fully in Artemis yet.
The components, one by one
Artemis — verified, early alpha
Verified: RP1's native browser, early alpha v0.4.3, desktop only. Not verified: no finished release, no mobile version, no user count, no claim that any Foundation world renders fully in it — the anchored fabrics do not, because their assets are not hosted.
VRS / Universal Map — verified as a registry
Verified: VRS is a registry; the Universal Map is the map on that registry. Not verified: no verified count of registered worlds, places, or users, and no claim that any Foundation world is registered and live through it.
Sneeze — name on the live site
Verified: the name appears as part of the RP1 ecosystem on the live Foundation site. Not verified: no description, no function, no product, no release, and no evidence of what Sneeze does or whether it is built. Treated here as a name only.
Rubidium — name on the live site
Verified: the name appears as part of the RP1 ecosystem on the live Foundation site. Not verified: no description, no function, no product, no release, and no evidence of what Rubidium does or whether it is built. Treated here as a name only.
RMAP — name on the live site
Verified: the name appears as part of the RP1 ecosystem on the live Foundation site. Not verified: no description, no function, and no evidence of what RMAP maps, renders, or records, or whether it is built. Treated here as a name only.
Statabase — name on the live site
Verified: the name appears as part of the RP1 ecosystem on the live Foundation site. Not verified: no description, no function, and no evidence of what data it holds, who can read it, or whether it is built. Treated here as a name only.
OMBI — name on the live site
Verified: the name appears as part of the RP1 ecosystem on the live Foundation site. Not verified: no description, no function, and no evidence of what OMBI does or whether it is built. Treated here as a name only.
Map Viewer — verified, and limited
Verified: a database-backed editor, not a JSON renderer. Not verified: no claim that it renders Foundation fabrics, and no claim that any world has been edited into a live state through it.
The honest way to read that grid is as a ratio: two components with verified substance (Artemis and VRS / Universal Map), one tool with a verified limit (the Map Viewer), and five names (Sneeze, Rubidium, RMAP, Statabase, OMBI) that are, today, only names. A stack that is two-eighths built and five-eighths named is not a working ecosystem; it is an ecosystem under construction.
The six anchored fabrics — and Biota, which has no series number
Six fabric files are published on GitHub Pages as the Foundation's anchored worlds: 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.71260348427612, -27.248278366617797. Five of the six map to series. The sixth does not, and this page says so plainly rather than assigning it one.
Biota.blockchain has an anchored world, but no series number. Its fabric is published, its coordinates are verified, and it appears in the Foundation's materials as Biota.blockchain — but Biota does not appear in the April 2026 internal list of 33 named W3 sub-series, and no document reviewed for this site assigns it a series number. This site does not assign it one. Inventing a number for Biota would corrupt the series list, mislead anyone counting the series, and create a false mapping that later work would have to undo. Biota is therefore recorded here exactly as it stands: anchored, published, and unnumbered, with the gap flagged for resolution. The same discipline applies to the WorldForge coordinate sets: the first 41 worlds in the WorldForge set carry latitude and longitude values that differ from these agi-corp anchor coordinates, and the two sets must never be mixed in an RP1 attach.
All six fabrics share the same limit: their JSON files are live on GitHub Pages, but the roughly 200 GLB assets and the map.wasm file they reference are not hosted, so none of the six renders fully in Artemis yet. “Anchored” therefore means “defined and located”, not “live” and not “rendering”. The remaining 28 series have no anchored fabric verified at all.
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 ~200 GLB assets + map.wasm not hosted.
- The Map Viewer as a database-backed editor.
- 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 ~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.
No timeline is given for any of these steps, because no timeline is verified. 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.
What you can enter today: the browser worlds (not RP1)
Zero worlds are live on RP1 — and that is not the same as having nothing to enter. The worlds built from the same anchored fabrics are playable in a browser today, in two places, and this section records them so the RP1 headline is not misread as “nothing exists”. Both are web 3D interpretations, not RP1 and not footage, and neither changes the RP1 count.
worlds-3d: seven playable flagships. The worlds-3d repository (AGIFutureFoundation/worlds-3d) is, in its own llms.txt, “a web 3D lobby over the 544 WorldForge worlds: 7 playable flagships built from the real anchored fabrics… Fully static, no backend.” Live at agifuturefoundation.github.io/worlds-3d/. The seven world files were counted in the 2026-11-07 review: 38 districts, 186 buildings, 56 NPCs, 46 quests, 73 collectibles. Per world (NPCs / quests / collectibles): AGI Corp Hub 3 / 2 / 6; Biota.blockchain 9 / 7 / 12; Cognition.X 9 / 8 / 9; Diagnostic.X 7 / 6 / 10; Empathic.X 8 / 6 / 10; Locator.X 9 / 7 / 11; SmartCiti.X Holodeck 11 / 10 / 15. The engine is plain Three.js r160, ES modules, no backend, no runtime CDN, with a procedural skybox and day cycle, 8 weather presets, seeded heightfield terrain, animated water, instanced foliage by biome, procedural buildings with enterable interiors, a third-person capsule avatar, NPC dialogue with quest accept, a quest tracker, rotating collectibles, and agent companions that follow the avatar. The lobby holds the 7 flagship cards plus the full 544-world index with search, biome filter (12 biomes), group filter, and 24-per-page pagination, under a header banner reading “Web 3D interpretation — not RP1, not footage.” The IWSDK 1.0 cutover (commit 83e33df9) added a VR + browser dual-runtime, with Havok physics WASM. Direct entry to the Holodeck flagship: worlds-3d/player.html?world=smartciti-holodeck.
How the flagships stay honest. All NPC dialogue is original game dialogue — never attributed to a real person, and no NPC claims to be a real person. Steward seats are real fabric nodes (“Steward seat 1–3 · human” in each zone fabric) but were not built as NPCs, because they represent human seats, not game characters. Advisor dialogue states the steward seats are held by humans and advisors only carry messages and never decide. Agent companions use only the 5 Virtuals agents, and their greetings name the real Virtuals ACP job, price, and offline status — for example, Tactile: “Hello — I'm Tactile, a workflow companion. On Virtuals ACP I offer workflow_plan ($10/24h), step_check ($1/5min) and workflow_audit ($50/48h), but my live instance is shut down, so no hire can be fulfilled today — I'm a game character only.” Each world has 2 companions. Quests are 3–5 step chains (talk, collect, visit a place, confirm); for example, q-first-lift, “Learn the crane signals and complete your first supervised lift”, rewards a Crane Signal Badge. Sample NPC dialogue (Ironworkers Foreman, SmartCiti Holodeck): “First day on the deck? Watch the crane, mind your tie-off, and ask before you lift.”
The Foundation VR entry and the agi.lease staging entry. The Foundation site's own VR tour shell lives at agifuturefoundation.github.io/agifuturefoundation.org/vr/ (vr/index.html + vr/vr-tour.js, “VR Tour — AGI Future Foundation”). A separate staging entry for SmartCiti.X was built locally on 2026-11-07 in the agi.lease repository track: a Three.js magic-window scene (vendored Three.js r160; 1 instanced building mesh, 48 buildings; instanced amber path markers; a glowing Holodeck gate; a bobbing guide orb), with a guided path in 3 steps — see the world, meet the guide, enter the Holodeck (linking to worlds-3d) — and three modes (VR headset with real WebXR immersive-vr, desktop WebGL magic window, mobile touch). It is labelled “IWSDK-patterned”: it does not import @iwsdk/core and is not “built with IWSDK”. It is local staging, not pushed, shared, sent, or posted, and its real WebGL render, mobile touch, and Quest headset entry are not verified. The live www.agi.lease page, served from the same repository, is the SmartCiti.X WorldForge landing page, last modified 28 Oct 2026.
The Worlds Hub (fellowship.chat). The flagship front door for the worlds is AGIFutureFoundation/fellowship.chat: a game-lobby homepage for the AGI worlds, the Omega Hive agents, and the Idea Exchange, with the deep Plans on one side and the Worlds on the other. Its own status board records 544 WorldForge worlds, 35 showcase entries, and 0 live on RP1, with 29 Virtuals jobs and 6 subscriptions listed and 0 instances online. Its rules for agents are explicit: do not attempt a hire (all 5 agent instances are offline), do not call an x402 endpoint (none is live), do not present the Agent Commons as live traffic (it is a labelled simulation), do not present either nonprofit as tax-exempt, and do not sum suggested valuations into a family total.
Series mapping for the flagships. Five flagships map to series: S01 Cognition.X, S02 Empathic.X, S03 Diagnostic.X, S08 Locator.X, and S10 SmartCiti.X (Holodeck). The AGI Corp Hub flagship maps to AGI Corp. Biota.blockchain is the seventh flagship and maps to no series. Two mapping facts from the review belong here: S01 Cognition.X and S10 SmartCiti.X are flagship fabrics but are not in the 544-world index (0 hits each) — they have worlds-3d presence via the flagship route, not the index route. And S18 BioDAO has no s18 curated entry in the 544 index; only biota-blockchain appears, which is not S18. Every other series (30 of 33) has exactly one curated 544-index entry.
Code and repositories
Repositories: AGIFutureFoundation/worlds-3d (the lobby, the 7 flagship world files, data/worlds.json with the verbatim 544-world list, data.js registry, IWSDK scene, and the tools/ generator — with the review's warning that the generator is out of sync and tools/build_worlds.py must not be re-run as a script, or it would wipe the Phase 2 fill), AGIFutureFoundation/agi.lease (the staging VR entry and the live www.agi.lease page), AGIFutureFoundation/fellowship.chat (the Worlds Hub), AGIFutureFoundation/WorldForge-Browser (the Earth worlds front end), and AGIFutureFoundation/agi-corp-worlds (the fabrics and the metaprompt system). A GLB hunt in the review found 151 of 168 fabric GLB references in WorldForge-Browser, with 17 not found anywhere reachable — part of why the anchored fabrics do not yet render fully. Both worlds-3d and fellowship.chat have empty (0-byte) README files; the real documentation lives in their llms.txt and *-NOTE.md / *-REPORT.md files, and neither repository has an AGENTS.md.
What would have to happen next
Before anything on this page can be described as live, four things would have to happen, 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.
Until those steps are taken, the honest public record for the RP1 ecosystem is this page: a real browser in early alpha, a real registry, six anchored fabrics that do not yet render fully, five names that are only names, and zero worlds live on RP1.
How it would be governed
Governance for the RP1 ecosystem, as planned, follows the model used across the intended W3 network. Day-to-day work would be agent-managed: agents would operate routine work within limits set in advance by humans. Humans decide, humans sign, and humans move funds. Agents do not sign documents, do not move money, do not hire or fire, do not offer securities, and do not enact doctrine or charters. 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. The Foundation's role in the intended structure is as mission steward, under written mission agreements, with its board remaining independent: a California nonprofit cannot be owned or controlled by a for-profit head. No agent message, draft, or page like this one is a commitment by the project or the Foundation; only a named human acting within signed, written authority can commit either one, and any future fundraising, partnership, or customer agreement would need its own documents, its own issuer, and counsel review.
Get involved / contact
If this project interests you, the route is a conversation, not a transaction. Write to [email protected] and say who you are, what you do, and what you would like to explore — research, a future partnership, volunteering, or a question about the Foundation's mission. A human steward will read it. Please do not send money, do not ask for investment terms, and do not treat this page as an invitation to invest: there is no offering here, no price, no terms, and no return is promised or implied. What is genuinely useful at this stage is specific, verifiable help: a named contact in the field, a written source that corrects or confirms something on this page, or a question that exposes a gap in the plan.
Nothing on this page is legal, tax, or financial advice, and no signing, membership, payment, investment, or offering is made here. the RP1 ecosystem is intended/planned, not formed, funded, or offered, unless this page cites a filing that says otherwise. The Foundation is a California Nonprofit Public Benefit Corporation, Entity No. B20260196664, filed 2026-04-24; no IRS 501(c)(3) determination letter is in the files reviewed, so no tax-exempt status or tax-deductible donation is claimed.