W3 LLC · Series S08 · Intended / Planned
Locator.X
Location, finding, and navigation — knowing where things and people are, planned.
Source for the name and number: the April 2026 internal W3 series list (internal printout, dated 2026-04-03, not a Wyoming Secretary of State filing). The list names 33 sub-series, Series 1–33. It proves no filing, no legal designation, no bank account, no EIN, and no Steward Council per series.
What this series is
Locator.X is Series 8 in the April 2026 internal W3 series list. Its name points at location: finding things, finding people, finding places, and knowing where something is in relation to everything else. That is the domain the name implies, and it is stated here as a planned focus, because beyond the name, the series number, and its anchored metaverse world, no product, service, dataset, partner, or publication for Locator.X is verified in the files. The page is therefore built from the name, the anchor, and the questions a location series would have to answer — not from a product that exists.
The domain the name implies is broad, and the breadth is worth naming because it shows how much is still undefined. Location work could mean navigation for people moving through a city, or finding an object, a vehicle, a building, or a service. It could mean mapping — building and keeping the record of where things are — or it could mean search: answering “where is” in a way that is fast, accurate, and respectful of privacy. It could serve travellers, delivery, emergency response, or simply someone trying to find a place they have never been. No verified document says which of those Locator.X intends, and this page does not choose on the series’ behalf. A location service that does everything is a slogan; a real one picks a user, a place, and a question, and does that well.
What can be said without inventing anything is what a location series would have to get right if it were built, and the first item is privacy. Location is personal information in a direct and sometimes sensitive sense: where a person is, where they have been, and where they go can reveal health, belief, relationships, and routine. A series in this domain would need, before it collected anything, a written answer to what location data it collects, from whom, with what consent, how precisely, how long it keeps it, who can see it, and how a person opts out or deletes it. It would also need to say what it does not track, and to mean it. No such answer exists for Locator.X today. The absence of a location-data policy is not a detail to be filled in later; for this domain, it is the first thing that would need to exist, and its absence is part of why this page describes the series as planned rather than operating.
The neighbouring domains help to sketch, without inventing, where such a series might matter. A city-scale environment (SmartCiti.X, Series 10) needs to know where its places, vehicles, and people are. Finding and using places (ParkingSmart.X, Series 12) is location work in a specific setting. Moving things to people (Get.Delivery DAO, Series 22) depends on knowing where both ends of a delivery are. Learning in a place (Cognition.X, Series 1) can be location-aware. Locator.X, if it is built, could sit beneath those neighbours as shared location infrastructure, or alongside them as its own service. That is a statement about the shape of the domain, not a claim that any collaboration exists: no joint work with any neighbouring series is verified.
Metaverse connection
Anchored world: Locator.X, 21.09705311564314, 142.69254864512746. This is one of the verified anchored worlds in the Foundation’s metaverse work: a Locator.X fabric with those coordinates. Its fabric JSON is live on GitHub Pages under the WorldForge-Browser my-fabric directory (fabric JSON), but the referenced assets behind it — on the order of two hundred GLB model files plus the map.wasm module — are not hosted there, so the world does not render fully in Artemis yet. That is the verified state: a published fabric definition, an anchored location, and an incomplete render because the assets it points to are not in place.
What that means in practice is that the world exists as a plan and a partial build, not as a place a visitor can enter today. The next step, if it is to be visitable, is specific: host the referenced GLB assets and map.wasm at the paths the fabric expects, then verify the render in Artemis. Until that is done, any image or description of the world should be labelled as a concept or a partial build, not as a live world. And the world is not on RP1: zero worlds are live on RP1, no fabric or service for this series has ever been attached there, and the RP1 Attach wizard needs a live metaverse-server endpoint before any attach can happen.
For a location series, the anchored world is a fitting illustration of both the promise and the limit. A world with coordinates is, in a small way, already a location claim: this place, at these numbers, exists in the Foundation’s map. But a coordinate on its own is not a location service. It does not tell a visitor how to get there, what is nearby, or what is there when they arrive, and it says nothing about real-world places at all. The anchored fabric is a location for a future build, not evidence of a working locator, and this page keeps that distinction visible.
What exists today — and what is planned
What exists today
Two things are verified. First, the name and number: Locator.X, Series 8, in the April 2026 internal W3 series list. Second, the anchored metaverse fabric: a Locator.X world at 21.09705311564314, 142.69254864512746, with its fabric JSON live on GitHub Pages and its assets not yet hosted, so it does not render fully in Artemis. That is the complete verified inventory for this series. No product, dataset, partner, user, or publication is verified.
What is planned
Everything else is planned, not existing: the formation of W3 LLC and the designation of this series; a human Steward Council and operating rules; any location product, dataset, or service; any location-data and privacy policy; any funding; and a fully rendering world on a live metaverse service. Each of those would need its own document, decision, and human signature before it could be stated as fact here.
The most useful next step for Locator.X would be the smallest one that adds real information: a written statement of scope from a named human steward, saying which location question the series intends to answer first, for whom, and under what privacy policy. Until that document exists, the honest size of this series is a name, a number, and a partial world — and this page is content to leave it at that.
How it fits — tier, related series, and governance
The intended structure, in words. At the top of the intended structure sits the AGI Future Foundation, a filed California nonprofit public benefit corporation (Entity No. B20260196664, Articles filed 2026-04-24, EIN assigned 2026-05-07). Below it, in the intended plan, sits W3 LLC, a Wyoming series LLC, and below that the individual series — of which Locator.X is S08 in the April 2026 internal list. That is the plan as described in the Foundation’s own materials. It is not a description of a completed legal structure: W3 LLC formation and per-series designation are not verified in filings, so the middle and bottom tiers of that diagram are intended, not established. Nothing on this page should be read as saying the Foundation owns, controls, or has formed Locator.X, or that Locator.X exists as a company, a fund, or an operating business today.
Related series. The series that sit closest to Locator.X by subject matter are listed in the card below. “Related” here means only that their names point at neighbouring domains. It does not mean that any joint project, shared budget, shared staff, partnership agreement, or data-sharing arrangement exists between them. No such arrangement is verified for Locator.X, and none is claimed here. If two series ever do work together, that would need its own written agreement, its own human approvals, and its own public record — none of which exists yet for this series.
Related series (by domain only)
S10 SmartCiti.X (city-scale location and navigation), S12 ParkingSmart.X (finding and using places), S22 Get.Delivery DAO (moving things to people), and S01 Cognition.X (location-aware learning) are the nearest neighbours by domain. No joint work is verified with any of them.
Governance — planned, not yet operating
The planned governance model for the W3 series, as described on the Foundation site, is DAO-managed day-to-day work with human decision-making at every point that matters: agents may draft proposals, prepare research, and operate routine systems, but humans decide, humans sign, and humans move funds. A Steward Council of humans is intended to hold that gate. No Steward Council membership, no signed votes, no seated manager, and no operating agreement for Locator.X is verified in the files, so none is named here. Until those human roles are seated in writing, there is no one who can speak for, commit, or spend on behalf of this series — and this page does not do so.
What governance would have to answer first. Before Locator.X could do substantive work, its human stewards would need to settle, in writing, at least these questions: what exactly is in scope and what is out of scope; who the stewards are and how they are replaced; what agents may and may not do without a human signature; how money, if any ever exists, is held, accounted for, and reported; and how the series relates to the Foundation’s public-benefit purpose. None of those answers exists in a verified document today. Listing the questions is not the same as answering them, and this page deliberately does not pretend otherwise.
What would have to happen before this series could operate
A named series is not a formed series. For Locator.X to move from a line in an internal list to an operating venture, several distinct steps would each have to happen, in order, with documents to prove them. First, W3 LLC itself would need to be formed and evidenced by a filing that can be checked. Second, this series would need to be designated in writing as a series of that LLC, with its own name, purpose, and manager recorded. Third, the series would need its own operating rules, its own human stewards, and its own segregated accounting — so that its money, liabilities, and records are not mixed with any other series or with the Foundation. Fourth, any bank account, contract, hire, or public claim would need a named human signer acting under those written rules. Fifth, any fundraising would need its own counsel-approved documents, its own issuer, and its own securities compliance — it could not borrow the Foundation’s nonprofit status, and the Foundation, as filed, cannot offer equity or a SAFE. None of those steps is verified as done for Locator.X. This section is included so that a reader can see the gap plainly, rather than mistaking a polished landing page for a finished company.
That gap is also why this page carries no timeline. There is no launch date, no funding date, and no hiring date stated here, because none has been set in a verified document. A date on a landing page would look like a commitment; without a filing, a budget, and a human team behind it, it would be a decoration, not a plan. When a real date exists, it should appear here with the document behind it cited.
Proposed projects — for DAO review
These are proposals for the series DAO team to review. None is approved, funded, staffed, or scheduled.
Grounded in the name and the anchored metaverse world on this page: location, finding things, finding people, finding places, and knowing where something is in relation to everything else. The GitHub review records a Locator.X code repo with real-estate tooling and an Academy, but beyond the name, the number, and the anchor, no product, service, dataset, partner, or publication for this series is verified in the files.
Finding-things scope paper
A one-page written statement of what finding means for this series: finding things, finding people, and finding places, and the differences between them. The paper would be approved by stewards before any service is designed. No such paper exists today.
What success would look like: A scope paper exists that the stewards have approved, stating what finding covers here.
Reviewing team: the Locator.X DAO
Status: PROPOSED — pending DAO team review
No funding, partner, or timeline yet.
Locator repo review proposal
A proposal to review the existing Locator.X code repo against the purpose of this series: what its real-estate tooling and Academy do, what they do not do, and what would need to change for them to serve this series. The review would be a written note, not a rebuild. No such review exists today.
What success would look like: A review note exists listing what the repo does and does not do, with recommendations for the DAO team.
Reviewing team: the Locator.X DAO
Status: PROPOSED — pending DAO team review
No funding, partner, or timeline yet.
Location literacy curriculum outline
An outline for location literacy lessons building on the Academy already in the repo: how maps work, how location data is made, and how to read a place. The outline would be a teaching plan, not a claim that lessons exist. No curriculum is verified for this series.
What success would look like: A curriculum outline exists with lesson topics and learning aims, reviewed by stewards.
Reviewing team: the Locator.X DAO
Status: PROPOSED — pending DAO team review
No funding, partner, or timeline yet.
Mapping accuracy standard
A proposal for how location claims from this series would be checked: what counts as accurate, how errors are corrected, and who checks. The standard would be written before any map or guide is published. No such standard exists today.
What success would look like: An accuracy standard exists with a checking process and a correction process, approved by stewards.
Reviewing team: the Locator.X DAO
Status: PROPOSED — pending DAO team review
No funding, partner, or timeline yet.
Privacy and location data paper
A written paper on how location data about people would be protected: what is collected, what is never collected, and who may see it. The paper would be approved before any location service handles personal data. No such paper exists today.
What success would look like: A privacy paper exists that the stewards have approved, stating what location data is collected and who may see it.
Reviewing team: the Locator.X DAO
Status: PROPOSED — pending DAO team review
No funding, partner, or timeline yet.
Real-world anchor registry — Locator.X
A seeded prompt in the fellowship.chat Idea Exchange names a real-world anchor registry for Locator.X: a record of where anchored worlds sit on the real Earth. The prompt is seeded by the hub itself, not posted by a person or agent, and it is listed here as an idea for the DAO team to consider, not as work underway. Six fabrics are anchored today (SmartCiti.X Holodeck, Cognition.X Campus, Locator.X, Biota.blockchain, Empathic.X, Diagnostic.X); a registry would record those anchors and any future ones in one place.
What success would look like: A registry draft exists listing the anchored worlds with their coordinates and sources, reviewed by stewards.
Reviewing team: the Locator.X DAO
Status: PROPOSED — pending DAO team review
No funding, partner, or timeline yet.
Code and repositories
- Locator.X — Substantive code repo with real-estate tooling and an Academy. Described in the organisation listing as real-estate analytics and mapping.
- locatorx-site — Landing site repo for Locator.X, described as real-estate analytics/mapping for the smart city’s physical layer.
- agi-corp-worlds —
agents/prompts/locator-x.json: 15 generated prompts (team charter, coordinator, and 13 specialists), each held to a ten-point eval; all checks passed. Its spec metaprompt records the founder’s one-line focus verbatim: “Real-estate development and investment predictive tooling, plus the Academy that teaches it.” The advisor contract (agents/advisors/locator-x.json) defines three scripted advisors — Host, Steward Liaison, and Alignment — answering bysay(a sentence about this world’s own policy, with the record named) orread(a binding to the data path the answer is read from at view time). Advisors are scripted guides, not AI.
A per-series tutor prompt, worldforge/out/training/tutors/locator-x.md, was identified in WorldForge-Browser; its contents have not been read, so nothing about it is described here. An Omega liaison card, omega.locator-x, is listed among the 38 agent cards in Metropolis-SmartCiti (agents/cards/); its contents were not individually read.
Visit in VR
Locator.X is one of the seven flagship worlds in the worlds-3d web 3D lobby: a playable world definition with 9 NPCs, 7 quests, and 11 collectibles, anchored at 21.09705311564314, 142.69254864512746. The lobby labels itself plainly: a web 3D interpretation — not RP1, not footage — and zero worlds are live on RP1.
- Foundation VR tour — the Foundation’s VR tour shell.
- worlds-3d lobby — the seven flagship worlds and the full 544-world index, where this series also has a curated entry (
locator-x). - Locator.X in the worlds-3d player — the flagship world.
Every world in the lobby gets three scripted advisors — Host, Steward Liaison, and Alignment — who are scripted guides under an advisor contract, not AI: no model runs behind one, and advisors carry messages but never decide. All NPC dialogue in the lobby is original game dialogue, never attributed to a real person, and no NPC claims to be a real person.
Get involved / contact
If you are interested in Locator.X, the route is a conversation, not a transaction. Write to [email protected] and say who you are, what your interest is, and what you could contribute — research, building, review, or simply following the work. A reply, if one comes, will come from a human. Agents writing in should follow the same route the Foundation sets out on its home page: state your operator and your human principal, and do not present yourself as the Foundation or commit it to anything.
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 for this series. There are no investment terms here — no price, no valuation, no cap, no discount, no minimum, no return, and no deadline — because there is nothing to invest in yet: the series is not formed, not funded, and not offered. No suggested valuation is assigned to Locator.X on this page, and none should be inferred from valuations discussed elsewhere for other entities; those figures, where they exist, are illustrative planning figures for different issuers and do not transfer to this series. If you are considering any payment to any entity in this family, ask first for the filing, the determination letter if tax treatment matters to you, and the counsel-approved offering documents — and take independent legal and tax advice before acting.
Nothing on this page is legal, tax, or financial advice. Filed facts stated here are: AGI Future Foundation, 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 in the files, so no tax-exempt status or tax-deductible donations are claimed. AGI Corp has an EIN only (assigned 2026-05-16); its incorporation is unverified. The live Foundation site lists a “66-W3 Wyoming Series network” and “33 agentic subsidiaries” — that numbering is site copy, not a filing, and it sits alongside the 33 named sub-series in the April 2026 internal list.
Long-form articles
Three long-form articles (4,000–5,000 words each) go deeper than this page: