Roadmap
What exists today vs what is planned, in order. The rule for this page is simple: nothing is presented as done until it is. An item moves from "planned" to "exists" only when a filing, a deployment, a signed agreement, or a verified live check says so — not when it appears in a plan.
Filed fact: AGI Future Foundation — CA Nonprofit Public Benefit Corp, Entity B20260196664, filed 2026-04-24. AGI Fellowship — CA Nonprofit Religious Corp, Entity B20260229217, filed 2026-05-13. No IRS 501(c)(3) determination letter exists for either — neither is presented as tax-exempt and no donation is presented as tax-deductible. AGI Corp has an EIN only; incorporation is unverified.
⚠ A note on counts before you read the lists
Different sources in this project give different counts for the same things, and this page does not pick a winner. The W3 list is 33 named sub-series in an April 2026 internal printout — that is the verified count from the filed paperwork. Other figures appear elsewhere in the project's own materials — including "35 cells" on the Foundation site and "34 worlds" in a repository listing — and they are flagged here as conflicting figures, not facts: they contradict the 33-series internal list and have not been explained or corrected in the files reviewed. Until one count is confirmed in writing with a source, this page quotes only the 33-series internal list as the series count, and treats the other figures as unresolved conflicts. The same caution applies to the "~200" figure sometimes quoted for AR/VR spaces: no verified source lists 200 spaces; the underlying count is of 3D model files referenced by the fabrics, and model files are not worlds.
What exists today
The list below is everything the roadmap can claim as done, with the evidence for each item. It is shorter than the planned list, and that is the honest shape of the project today: two filed nonprofits, an EIN-only corporation, a set of live demos and listings, and a great deal of paper.
● Filed entities
- AGI Future Foundation filed — CA nonprofit public benefit corp, Entity B20260196664, Articles filed 2026-04-24, SOS approval 2026-04-30, EIN assigned 2026-05-07.
- AGI Fellowship filed — CA nonprofit religious corp, Entity B20260229217, Articles filed 2026-05-13, SOS approval 2026-05-18, EIN assigned 2026-05-18.
- AGI Corp has an EIN only — IRS notice dated 2026-05-16. Incorporation is unverified: no SOS articles or entity number are in the files. An EIN alone does not prove incorporation.
● Worlds and fabric files
- 6 anchored fabric JSON files live on GitHub Pages, plus a POC fabric and a Hub demo scene — 8 fabric files in total.
- AGI Corp POC and Hub demo scenes exist as demos — rendered scenes, not anchored worlds, with no coordinates and no RP1 attach.
- 544 WorldForge worlds in the Earth index — all recorded as rp1:null, meaning none is live on RP1.
- W3 = 33 named sub-series in an April 2026 internal list. That list is a printout, not a Wyoming SOS filing, and it proves no filing, no legal designation, no bank account, no EIN, and no council per series.
● Agents, jobs, and sites
- 29 Virtuals ACP jobs + 6 subscriptions listed (verified 2026-11-06), with Require Funds on and prices in USDC — but the agent instances are offline, so a hire fulfills only after each agent is deployed.
- Fellowship site live with 40 articles, plus glossary, FAQ, faith bridges, agents, and get-involved sections.
- Foundation site live on GitHub Pages — while www still serves the older Kylon site until the DNS step is taken. The live Foundation site and the older Kylon site do not yet agree with each other (see the Structure page's notes on the outdated copy).
That is the full "exists" list for this roadmap. Every other item in the project — every filing, formation, issuance, raise, deployment, and agreement described in the plans — belongs in the next section.
What is planned / not done
Each item below is planned, not done. No date is given for any of them, because no date is on record in the files reviewed — a planned item with an invented date would be worse than a planned item with no date at all. Where a deadline is known from a filing rule, it is stated as a rule, not as a completion date.
| Planned item | What "done" would require | Current state |
|---|---|---|
| IRS 501(c)(3) determination letters — for both the Foundation and the Fellowship | An IRS determination letter for each entity | Neither is on file. No letter exists for either entity, and neither is presented as tax-exempt; no donation is presented as tax-deductible. |
| Fellowship Statement of Information | A filed Statement of Information with the California Secretary of State | Filing status unverified. Due within 90 days of 2026-05-13 (about 2026-08-11). No filing was in the files reviewed. |
| Bylaws (Foundation and Fellowship) | Adopted bylaws on file for each entity | Not in the files. Unverified. |
| California Attorney General registration | AG registration on record | Not in the files. Unverified. |
| Inter-entity agreements | Written agreements adopted by the relevant boards, including Fellowship partnership agreements with an independence clause | Not in the files. Unverified. |
| W3 LLC filing (Wyoming series LLC) | A Wyoming SOS filing | Not filed. Intended only; the April 2026 list is an internal printout, not a filing. |
| Delaware series filings (C1S1–S3) | Delaware series LLC filings | Not filed. Intended only; cohort series to confirm. |
| SmartCiti.X, Inc. formation | Incorporation, charter, bylaws, EIN, bank account, cap table — plus name/trademark clearance first | Not formed. Proposed only; Delaware C-corp recommended, Wyoming alternative, PBC vs standard corp for counsel to choose. |
| Any SAFE issuance | A lawful offering process, counsel review, issuer chosen in writing, Form D where required | Nothing issued. Drafts and blank terms only. |
| Any series raise | A formed series, a seated Steward Council, counsel review, a lawful offering | No raise has happened. Suggested figures only; see the Numbers page. |
| RP1 portal attach | A public map-service endpoint in /fabric/<id>/<version>/ form | Blocked. The portal wizard rejects static file URLs; the map service runs locally only. 0 worlds live on RP1. |
| Hosting the ~200 referenced GLB model files | 168 unique model files hosted at reachable URLs | Not hosted. The 6 fabrics load as data but cannot render fully without them. |
| Deploying the 5 Virtuals agents' instances | An online, deployed instance per agent (Omega, Tactile, ALS, CMMC, WAVE) | Not deployed. Consoles show "No Instance — Deploy to get online"; WAVE also needs a hosting payment settled first. |
| A named donation route | A published, working donation route for the Foundation and the Fellowship | Not named. No payment link exists on this hub; donations are arranged by email only, and no route is confirmed. |
| The fellowship.chat subdomain rollout | Subdomains live and resolving | Not done. Planned only; no subdomain is verified as live. |
Two items on this list deserve emphasis because they are easy to misread as done. The first is the Fellowship's Statement of Information: the due date (about 2026-08-11) has passed, and the filing status is unverified — that is not a statement that it was filed late, and it is not a statement that it was never filed. It is a statement that no filing was in the files reviewed, and the status must be checked with the Secretary of State before anyone claims otherwise. The second is the donation route: the Fellowship and the Foundation both accept donations in principle, but no named, working route exists on this hub, and no donation link is published here. A donor today would be arranging a gift by email, not clicking a confirmed route.
Sequencing — the order of operations
The raise advice in the corporate paperwork sets a sequence, and the roadmap follows it. The sequence is: cleanup → donations → AGI Corp SAFE → first series raise. Each step depends on the one before it, and skipping a step does not make the later steps happen faster — it makes them happen without the foundation they require.
1. Cleanup. Resolve the filed-versus-intended record first: confirm filings and their status, complete missing filings (including the Fellowship Statement of Information question), put bylaws and registrations on file, settle the PBC fork by choosing one track in writing, and correct the website copy that contradicts the filings. Cleanup is not administrative tidying; it is what makes everything after it lawful to attempt.
2. Donations. The nonprofit lane comes before any securities lane: donation and grant support for the Foundation and donation and tithe support for the Fellowship, with no tax-deductibility claim until an IRS determination letter exists. A named donation route belongs here, once it exists.
3. AGI Corp SAFE. Only after cleanup and the donations lane, and only once AGI Corp's incorporation is verified and counsel has designed the offering, does the studio's SAFE become a live step — with the issuer chosen in writing and the AGI Corp SAFE and PBC SAFE treated as alternatives, never both for the same round.
4. First series raise. The first series raise — SmartCiti.X is the proposed first — comes last in this sequence, after the studio is formed and funded, the series is formed, its Steward Council is seated, its gates are defined, and counsel has reviewed the offering. A series raise before those pieces exist is not an accelerated timeline; it is a raise with no issuer, no council, and no lawful process.
Nothing in this sequence has a date attached in the files reviewed. The sequence is an order, not a calendar. When dates exist — because a filing is made, a board adopts a plan, or counsel sets a timetable — they can be added here with the filing or the minutes as the source. Until then, the roadmap shows the order and says the dates are unknown.
Stage gates — the progression framework
Every series and every studio project moves through the same progression framework: Stage 0 Idea → Stage 1 Validate → Stage 2 Build → Stage 3 Launch → Stage 4 Operate/Scale → Stage 5 Exit/Wind-down. The gates are the mechanism that keeps a project honest about where it is: a project is at the gate it has passed, not the gate it aspires to.
| Gate | Name | What it means |
|---|---|---|
| 0 | Idea | An idea exists on paper. Nothing is validated, built, or funded. |
| 1 | Validate | The idea has been tested against evidence: need, feasibility, and fit with the mission. |
| 2 | Build | Building has begun under an approved plan, with humans accountable for it. |
| 3 | Launch | The work is live in its first real form, with real users or real operations. |
| 4 | Operate / Scale | Live operations, sustained and growing under stewardship. |
| 5 | Exit / Wind-down | An orderly exit or wind-down, with obligations settled and records kept. |
Two rules govern the gates, and both are hard rules. First, a series with no Steward Council is capped at Gate 1. It can be an idea, and it can be validated — but it cannot pass into Build, because there is no council to approve the gate, no council to move funds, and no council to be accountable for the build. Since no series has a verified seated council today, no series today is past Gate 1 on this framework, whatever stage its materials may suggest.
Second, each gate needs a human approver's signature plus filed evidence. A gate is not passed by an agent's assessment, a demo, or a plan document. It is passed when a named human approver signs and the evidence for that gate is filed — the validation evidence for Gate 1, the build plan and accountability for Gate 2, the launch record for Gate 3, and so on. Without the signature and the filed evidence, the gate is not passed, and the project stays where it is. That is why the "exists today" list and the gate framework agree with each other: the worlds, fabrics, and demos that exist are real work, but the series and raises built on top of them are still at the idea and validation stages, waiting on councils, filings, and signatures that do not yet exist.
The gate framework also governs the end of a project, not just its beginning. Gate 5 — Exit / Wind-down — is a planned, orderly stage with obligations settled, not a failure state and not an afterthought. A series that reaches Gate 5 winds down under its council's authority, with the same signed-vote discipline as every other gate.
What changes this page
This page is written to be updated by evidence. A filing moves an item from "planned" to "exists" when the filing is produced. A deployment moves an item when a live check confirms it. A signed agreement moves an item when the agreement is on file. A seated council moves a series past Gate 1 when three named, consenting humans hold keys and vote. Until one of those things happens, the item stays where it is on this page — and the page stays honest about it.
The most consequential near-term changes, in the order the sequence implies, would be: resolving the Fellowship Statement of Information status; putting bylaws and AG registration on file; choosing the PBC track in writing; verifying AGI Corp's incorporation; seating the first Steward Council; standing up the public map-service endpoint that unblocks RP1; hosting the GLB model files; deploying the five Virtuals agent instances; and naming a donation route. None of those has a date in the files reviewed. Each of them is a real, achievable step — and each of them is, today, not done.