Skip to content
AGI Future Foundation PBC

AGI Future Foundation · Projects · Infrastructure

WorldForge

WorldForge is the world-building side of the Foundation's network — the tooling and the catalogue of worlds that the planned metaverse presence would be built from. The numbers attached to it disagree with each other, and this page keeps the disagreement visible instead of picking the largest number: 80 worlds as stated on the Foundation site, and 544 worlds in the WorldForge-Browser repository's worlds file, every one of them with no RP1 attachment recorded.

What this isGet involved

What this is

WorldForge is the name for the world-building work in the Foundation's network: the creation of virtual worlds — spatial environments with terrain, structures, and assets — that the planned series and ventures would inhabit. On the live Foundation site it appears as part of the network story, alongside the series and the RP1 spatial-computing stack. What is verified about it is narrow, and this page stays inside that narrow verified core: there is a public repository called WorldForge-Browser, it contains a worlds file listing 544 worlds, and every one of those 544 entries records no RP1 attachment. There is also site copy stating 80 worlds. Those two numbers describe different things — a site claim and a repository file — and neither of them is a count of worlds that exist as finished, rendering, inhabited places.

That distinction matters because “worlds” can mean several different things, and the Foundation's materials use the word loosely. A world can be an entry in a JSON catalogue, a fabric definition file published on GitHub Pages, a fully rendered environment in a browser like Artemis, or a live place attached to RP1 that people can enter. Those are four different stages, and a world can be at stage one without being at stage four. The six anchored fabrics in the Foundation's network — Cognition, Empathic, Diagnostic, Locator, SmartCiti Holodeck, and Biota — are at stage two: their fabric JSON 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. Zero worlds are live on RP1, which is stage four. WorldForge, as a name, covers the tooling that would move a world from one stage to the next; it does not by itself prove that any world has completed the journey.

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 numbers, kept apart

Three numbers circulate for WorldForge and the worlds around it, and they must not be blended into a single claim. Each is quoted below with its source, and none is quoted as a count of finished, rendering, inhabited worlds.

80 worlds, as stated on the Foundation site. The live site copy states 80 worlds for WorldForge. That figure is quoted here as site copy, not as a verified fact. No document reviewed for this site explains how the 80 was counted — whether it is worlds built, worlds listed, worlds planned, or worlds in some other sense — and no independent count confirms it. Until a source explains the counting method, the honest way to quote it is exactly this: “80 worlds, as stated on the Foundation site.” It should not be quoted to a lawyer, a bank, or an investor as a verified count, and it should not be combined with any other number below.

544 worlds in the WorldForge-Browser repository. The public WorldForge-Browser repository contains a worlds file listing 544 worlds. That is a verified count of entries in a file, and it is the largest number in this section — which is precisely why it must not be quoted as “544 worlds built”. An entry in a catalogue is not a finished world. What the file does verify, and what matters more than its length, is the attachment column: every one of the 544 entries records rp1 as null. Not one of the 544 is recorded as attached to RP1. That is consistent with the wider verified fact that zero worlds are live on RP1, and it is the single most important thing the repository file establishes.

41 worlds, and the two repositories. The WorldForge-Browser repository is public and holds 41 worlds in one verified count, while a separate private repository, agi-corp-worlds, holds 40 worlds. Those counts describe repositories, not the same catalogue as the 544-entry worlds file, and they must not be mixed with it or with each other. The first 41 worlds in the WorldForge set also carry latitude and longitude values that differ from the agi-corp anchor coordinates.

34 worlds, and 35 cells. Other Foundation materials have mentioned 34 worlds and 35 cells. Those figures disagree with both the 80 and the 544, and with the 33 named series in the April 2026 internal list. This page does not resolve the disagreement by choosing a favourite. The safe counts on this site are the ones with a cited source: 33 named series in the April 2026 internal list, and 544 entries in the WorldForge-Browser worlds file, all with no RP1 attachment.

What is verified vs what is only a name

Verified

  • A public repository named WorldForge-Browser exists.
  • Its worlds file lists 544 worlds, all with rp1: null.
  • Its README describes 41 agentic training worlds on real Earth maps, with satellite imagery, elevation data, OpenStreetMap buildings, robot digital twins, and union trade certification courses.
  • Six anchored fabric JSONs are published on GitHub Pages (Cognition, Empathic, Diagnostic, Locator, SmartCiti Holodeck, Biota).
  • Zero worlds are live on RP1.
  • The agi-corp-worlds repository holds the metaprompt system for the same worlds: 264 generated prompts, held to a ten-point eval, with advisors as scripted guides, not AI.

Only a name, or site copy

  • “80 worlds” is site copy, with no counting method verified.
  • No finished, fully rendering world is verified.
  • No users, visitors, revenue, customers, or partners are verified for WorldForge.
  • No team, timeline, or launch date is verified.

The gap between those two columns is the whole story of this page. WorldForge is real as a repository and a catalogue, and it is unverified as a finished product with users. The work that has been done is cataloguing and fabric-writing; the work that has not been done is hosting the assets, verifying a full render, and attaching a world to RP1.

How it fits

Tier. WorldForge is infrastructure, not a company and not a series. In the intended three-tier structure it would sit underneath the commercial tier: the tooling that builds the worlds the series would inhabit, rather than a cell inside the W3 network. It is therefore not assigned a series number, not presented as a subsidiary, and not given a valuation. Suggested valuations in the Foundation's planning papers cover series and proposed corporations; no suggested valuation is assigned to WorldForge on this page, and none should be invented for it.

Relationship to RP1. WorldForge builds worlds; RP1 is the spatial-computing infrastructure those worlds would run on, and Artemis is RP1's native browser. The relationship is sequential, not simultaneous: a world must be built, its assets hosted, and its render verified in Artemis before any RP1 attach can even be attempted, and the attach itself is authorised world by world. No fabric or service has ever been attached for AGI Corp, and no world in the network has been verified live on RP1. The RP1 ecosystem page gives the full verified account of that stack, including the components that are only names on the live site.

Relationship to the series. The six anchored fabrics map to series where a mapping exists: Cognition to S01, Empathic to S02, Diagnostic to S03, Locator to S08, and the SmartCiti Holodeck to S10 SmartCiti.X. Biota is the exception that proves the rule about not inventing mappings: its anchored world sits at -38.713, -27.248, but Biota has no series number, and this site does not assign it one. The remaining 28 series have no anchored fabric verified, and their pages say so. WorldForge's catalogue is therefore much larger than its anchored set, and the anchored set is much larger than anything live — a nesting of claims that collapses if the stages are confused.

What exists today vs what is planned

What exists today

  • The WorldForge-Browser public repository and its 544-entry worlds file, all rp1: null.
  • Six anchored fabric JSONs on GitHub Pages, with their coordinates verified.
  • The Foundation's filing record (California Nonprofit Public Benefit Corporation, Entity No. B20260196664, filed 2026-04-24, EIN assigned 2026-05-07).
  • This page, as a public statement of the numbers and their limits.

What is planned

  • Host the roughly 200 GLB assets and map.wasm the anchored fabrics reference, and verify a full render in Artemis, with the date and result recorded.
  • Explain or correct the 80-world site figure with a stated counting method, or withdraw it.
  • Reconcile the 544, 41, 40, 34, and 35 counts in one dated note that says what each counts.
  • Pursue an RP1 attach world by world, only after a render is verified — and report the first live world with evidence, not assertion.

Each step would need its own document or dated verification. None is presented here as done, scheduled, or promised by a date, because no date is verified. In particular, no timeline is given for a first live world on RP1: “authorised world by world” is a permission, not a schedule.

What the WorldForge-Browser repository contains

The repository review of 2026-11-07 read the WorldForge-Browser README in full, and the record below is drawn only from what it states. The repository's own summary: “41 agentic training worlds on real Earth maps. Walkable 3-D worlds with satellite imagery, elevation data, OpenStreetMap buildings, robot digital twins, and union trade certification courses.” Its motto, quoted as repository copy, is “Agents operate; people govern. Powered by AGI Corp. Owned by AGI Future Foundation PBC.” The “Owned by” wording is the repository's own phrasing; it is not repeated here as a legal claim about the filed nonprofit Foundation, whose board must remain independent and which cannot be owned by a for-profit head.

What the 41 worlds contain. Satellite imagery (Esri), elevation (AWS Terrain Tiles), and OpenStreetMap buildings on real Earth maps — the worlds named in the README include London, New Orleans, Detroit, San Francisco, Boston, Houston, Austin, Seattle, and Kennedy Space Center. ROS 2-style robot tasks for 10 robot types, including Boston Dynamics Spot, Unitree Go2, PAL TALOS, UR10e, and Franka FR3. Union certifications: 8 industry programs (UAW, Teamsters, IBEW, 1199SEIU, UFCW, Laborers) with 70–140 hour courses. An “AGI Robotics Language” of JSONL training schemas. A quest system with XP and checkpoints. Avatar roles named in the README: Omega Stewards, Hermes messengers, Hive swarms, and Coaches.

Industry training hubs (city, industry, union, hours, robots — as stated in the README): Detroit automotive, UAW/IAM, 120h; Memphis logistics, Teamsters/ILWU, 80h; Miami construction, Laborers/Ironworkers, 100h; Boston healthcare, 1199SEIU, 90h; Central Valley agriculture, UFCW, 70h; Houston clean energy, IBEW, 110h; Austin electronics, IBEW/IUE-CWA, 130h; Seattle aerospace, IAM/UAW, 140h. These are repository-stated training hubs, not verified operating schools: no enrolment, graduate, employer, or completion figures are verified for any of them.

Where it runs. The deployed surface is site/earth/ — the live site is agifuturefoundation.github.io/WorldForge-Browser/earth/ — with a world registry (worlds.json, about 823 KB), and pages for the world view, console, RP1, training, AR training, marketplace, and dashboards. The root earth/ directory holds the data and build tooling: a smaller worlds file, locations, an agent network file (5.9 MB), courses, dialogue, and build scripts. The related repositories named in the README are SmartCiti.X (Trade Craft Academy) and Metropolis-SmartCiti (the on-chain agent layer on Monad) — see Metropolis-SmartCiti and S10 SmartCiti.X.

How it looks. The repository's style guide (SMARTCITI-STYLE.md, read in the org-wide sweep) specifies a deliberate 2000s-console aesthetic for SmartCiti environments: “era-authentic but polished”, internal resolution at devicePixelRatio × 0.42 with pixelated upscale, antialiasing off, ACES exposure 0.88, BasicShadowMap at 1024², fog Fog(0xb4d0ea, 420, 2300), a CRT scanline overlay, per-vertex (Gouraud) lighting, and a 512px texture ceiling with NearestFilter magnification. The look is a design choice recorded in the repository, not a rendering claim: no finished, fully rendering world is verified on this page.

Worlds you can enter in a browser today. The 41 Earth worlds are the front end; the playable browser worlds built from the same fabrics live in worlds-3d: seven flagship worlds at agifuturefoundation.github.io/worlds-3d/, with 38 districts, 186 buildings, 56 NPCs, 46 quests, and 73 collectibles counted across the seven world files, and the Foundation's own VR tour entry at agifuturefoundation.github.io/agifuturefoundation.org/vr/. Both are web 3D interpretations, not RP1 and not footage, and zero worlds are live on RP1. The flagships map to series where a mapping exists: S01 Cognition.X, S02 Empathic.X, S03 Diagnostic.X, S08 Locator.X, and S10 SmartCiti.X (Holodeck), plus Biota, which has no series number. S29 Metaverse DAO is the series whose repo coverage is this repository itself; S30 Robotics DAO is covered by the robot-task and simulator content. See the RP1 ecosystem page for the full anchored-fabric record.

Code and repositories

Repository: AGIFutureFoundation/WorldForge-Browser (public). Related: AGIFutureFoundation/agi-corp-worlds (the fabric and agent registry; see the next section), AGIFutureFoundation/worlds-3d (the playable browser worlds), AGIFutureFoundation/SmartCiti.X (the Trade Craft Academy curriculum). Per-series tutor prompts live in WorldForge-Browser at worldforge/out/training/tutors/*.md (for example empathic-x.md, diagnostic-x.md, s20-cmmc.md, s33-infogurus.md, locator-x.md, s04-curable-x.md, s11-molecular.md, s07-divine-dao.md, s06-blockchain.md, s13-gonstead-x.md, s14-askdoc-x.md, s25-mypet-ai.md, s26-lyka-dao.md, s32-solar-dao.md, s19-moscone-x.md, s34-als-dao.md, plus non-series cancer-dao.md, climate-dao.md, ecology-dao.md, education-dao.md, and agentic-payments.md) — the files were identified by search, and their contents were not read in the 2026-11-07 review, so no description on this site is drawn from them yet. Also not yet read: the structure and sample of site/earth/worlds.json, the site/earth/data/ listing, and the agents/ listing in WorldForge-Browser (all blocked by a GitHub rate limit during the review, stopped per the hard-stop rule — not proven missing). No series page on this site links directly to a github.com repository URL; the repository names above are the citable references until links are verified.

The metaprompt and advisor system (agi-corp-worlds)

The actual metaprompt system for the AGI Corp worlds lives in AGIFutureFoundation/agi-corp-worlds, not in the site repositories: an org-wide search for “metaprompt” and “persona” returned no hits from the Foundation or Fellowship site repos. What the 2026-11-07 review read in agi-corp-worlds is summarised here, because it is the instruction layer any future world or project page would build on — and because its honesty rule is the same one this site follows.

264 metaprompts, held to their own evals. agents/metaprompt.mjs generates one system prompt per coordinator and specialist (264) plus the concierge, from each world's spec, worlds/PBC.json, the built swarm's routing table, and the middleware's own constants. Every prompt is held to a ten-point eval: umbrella present; every human-reserved action listed and marked Held for the Steward Council; every forbidden action listed; source cited; zone named; no PII or key-shaped strings; under 6,000 characters. Four deliberately broken prompts must each fail exactly their own check. The generated prompts live in agents/prompts/ (about 40 files, one per world); the sample read in full, locator-x.json, holds 15 prompts with all ten eval points passing. A coordinator prompt routes each turn to the specialist whose keywords match, with at most 3 handoffs per turn. The common block template states the management model (“agents operate, people govern”), lists the actions reserved for humans, lists forbidden actions, limits reading to named surfaces, requires a source beside every claim, refuses personal data, and carries a not-advice line (“Nothing you say is legal, financial, medical or investment advice”). The agents are deterministic stubs until a model is plugged in; the LangGraph and Sentient adapters are design only and have never been run.

Spec metaprompts and the “awaiting a founder focus” rule. Each world also gets a spec metaprompt: the prompt that would regenerate worlds/<slug>/spec.json under SPEC.md's nothing-invented rule. The 28 series worlds whose focus the stewards have not set are marked awaiting a founder focus rather than filled with a guess. agents/prompts/index.json records spec-metaprompt readiness as true for the 3 program-track worlds and the 6 anchored/DAO worlds, and false for all s04–s35 series worlds (founder focus unset). The founder focus sheet itself, worlds/focus.json, has every focus, lat, and lon as null across all 34 entries. No model has run any of these prompts.

Advisors are scripted guides, not AI. Advisors get no prompt, by contract. Each world has three scripted advisors — Host (welcoming visitors, pointing them to the right zone), Steward Liaison (“Who decides here?” → “Human stewards hold oversight, values alignment and final governance; agents coordinate between decision cycles”), and Alignment Advisor (the Alignment Evaluation Gate; “What happens if an agent tries a reserved action?” → “It is held for the Steward Council and recorded; the agent cannot complete it”). A topic is either a say (a sentence about the world's own policy, with the record it comes from named in cites) or a read (a binding to the data path the answer is read from at view time). The advisor contracts live in agents/advisors/ (about 40 files); only locator-x.json was read in full. This is the guide pattern any VR space on this site should follow: scripted, cited, and steward-gated.

Governance machinery, as code. The swarm layer (agents/) runs on the Trade Craft fabric's tested router and middleware, vendored unchanged; a concierge routes visitors to the right world's coordinator. DAO management teams (agents/dao.mjs) seat one team per world in the eight roles worlds/PBC.json says agents handle (research synthesis, task routing, proposal generation, operational coordination, progress tracking, monitoring, collaborator scouting, grant drafting). The proposal pipeline runs draft → under_review → enacted | declined, and steward transitions (enact, decline, 2-of-3 quorum) refuse any signer who is not a seated steward: an agent that tries is held and counted, never obeyed. No treasury is held; treasury.transfer is refused to everyone. The agent ledger (agents/ledger.mjs) is a hash-chained log that only a 2-of-3 steward quorum can extend, and it is not deployed on any chain. Comms (comms/build.mjs) maps one channel per world; the opening transcript is generated from the records, one agent reaches for proposal.enact and treasury.transfer (held) and for a forbidden action (contained), and the stewards are paged. No human message is ever generated, and the Coshell bridge is a dry run: nothing has reached Coshell.

Scaffolds, not worlds. The world factory (worlds/factory.mjs) generates 4,000 scaffold worlds — 40 team agents, one per parent world plus the AGI Corp Hub and the SmartCiti.X Holodeck, each generating 100 worlds, one per custom space across 20 templates (classroom, lab, forum, observatory, studio, clinic, workshop, library, arena, gallery, plaza, council, gate, desk, liaison, alignment, yard, hall, annex, commons). A scaffold's status is scaffold, never coming soon, and a scaffold becomes a real world only when a steward writes its focus into worlds/focus.json. Models are referenced from my-fabric/worlds/models (91 files) and never copied, which is why 4,000 worlds cost 16 MB. Deep builds (my-fabric/build_deep.py) put a furnished room behind every zone pad of every world — 38 worlds, 228 rooms — each room with a console and placard, each world with one gate. The RP1 export covers 38 world installers; none has been run against a live map service, and RP1's Dev Center asks an exporter to state that they own or lease each Earth location.

What would have to happen next

Before WorldForge can be described as anything more than a catalogue and a set of fabric files, 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 would have to be recorded. Second, the render: a full render in Artemis would have to be verified and dated, with a screenshot or a log, not merely asserted. Third, the count: the Foundation would have to publish one dated note reconciling the 80, 544, 41, 40, 34, and 35 figures, stating what each counts and which of them, if any, is the number to quote. 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 whole catalogue is live.

Until those steps are taken, the honest public record for WorldForge is this page: a real repository, a real catalogue of 544 entries with no RP1 attachment, six anchored fabrics that do not yet render fully, a site figure of 80 worlds quoted as site copy, and zero worlds live on RP1.

How it would be governed

Governance for WorldForge, 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. WorldForge 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.

← Back to the Foundation home page   ← Projects hub