Article 14 · Metaverse & Spatial · AGI Future Foundation
Locator.X: Knowing Where Things Are
Location is the quiet infrastructure underneath almost everything else the Foundation plans to build: you cannot deliver to a place, train in a place, or meet in a place until you can say where it is. Locator.X is the series that would answer that question — and it is also the one series in this set whose metaverse world has actually been anchored.
TL;DR
Locator.X is W3 Series S08, named in the April 2026 internal W3 series list, with a planned focus on location, finding, and navigation. It is intended and planned, not formed, funded, or offered, and no product, partner, or location-data policy is verified for it. What sets it apart from the other series in this set is its metaverse anchor: a Locator.X fabric at 21.097, 142.693, with its fabric JSON live on GitHub Pages — but the roughly two hundred GLB assets and the map.wasm module it references are not hosted, so the world does not render fully in Artemis yet.
The work
The name points at a simple human question — “where is it?” — and the simplicity is deceptive, because the question is asked in so many different settings that a single service could spend years choosing which one to answer first. 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” quickly, accurately, and in a way that respects the person asking. 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 article does not choose on the series’ behalf.
Why the domain matters is easier to state than what the series will do, because location is infrastructure: it makes other work possible rather than being the work itself. A city-scale environment needs to know where its places, vehicles, and people are. Finding and using a place is location work in a specific setting. Moving things to people depends on knowing where both ends of a delivery are. Learning in a place can be location-aware. If Locator.X is ever built, it could sit beneath its neighbours as shared location infrastructure, or alongside them as its own service — and the difference between those two shapes is itself a decision that has not been made. Shared infrastructure would need to serve several series at once, with agreements about who maintains it and who pays for it; a standalone service would need its own users, its own scope, and its own reason to exist. Neither shape is verified, and neither is claimed here.
The first thing a location series would have to get right is privacy, and it would have to get it right before it collected anything. 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, in writing, an 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 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.
For Locator.X specifically, the stewardship questions are sharper than for most series, because the data at stake is personal and the harm from getting it wrong is concrete. A Steward Council for this series would need to settle, before any collection began, what 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. Agents in this series would do the routine work — maintaining records, drafting proposals, tracking progress, monitoring systems — inside written limits, with a spending limit of zero dollars without Council approval unless the Council sets a written threshold. But the decision to collect a person’s location, to keep it, to share it, or to delete it would be a human decision every time, by a named steward, on a written record. 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.
Metaverse connection
Locator.X is one of the six anchored worlds in the Foundation’s metaverse work, and the anchor is specific: a Locator.X fabric at 21.097, 142.693. Its fabric JSON is live on GitHub Pages under the WorldForge-Browser my-fabric directory, 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 would have to happen next is equally specific: host the referenced GLB assets and map.wasm at the paths the fabric expects, then verify the render in Artemis, with the date and the result recorded. 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. The remaining 28 series have no anchored fabric verified at all, which makes Locator.X unusual in this set — but “anchored” means defined and located, not live and not rendering, and this article does not let the anchor stand in for a working service.
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.
What exists today vs what is planned
What exists today
- A name and a series number (S08) in the April 2026 internal W3 series list.
- An anchored metaverse fabric at 21.097, 142.693, with its fabric JSON live on GitHub Pages and its assets not yet hosted, so it does not render fully in Artemis.
- The Foundation’s filed nonprofit status and its intended W3 governance model, described on this page.
- The Locator.X repository puts tooling, a 92-lesson Academy, and 85 modules on record; no partner, user, publication, location-data policy, or Steward Council is verified.
What is planned
- Formation of W3 LLC and written designation of this series, with its own name, purpose, and manager recorded.
- A human Steward Council and operating rules, with segregated accounting so the series’ money, liabilities, and records are not mixed with any other series or with the Foundation.
- A written statement of scope: which location question the series answers first, for whom, and under what privacy policy.
- Any location product, dataset, or service; any funding; and a fully rendering world on a live metaverse service — each needing its own document, decision, and human signature.
Code and repositories
Locator.X offers real-estate development/investment predictive tooling: a 92-lesson Academy, 85 modules, 50-state guides; its ~4 GB of public-record data is not committed. locatorx-site is the landing stub: real-estate analytics and mapping for the smart city's physical layer.
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 Locator.X, the mission fit is a test of restraint as much as of ambition. A location service that served everyone, everywhere, would be a surveillance service by another name, and the Foundation’s public-benefit purpose — safe, equitable, and socially beneficial AI — would fail at the first question if the series collected location data without consent, kept it without limit, or shared it without a written rule. The Fiduciary Shield protects a board that weighs safety and public benefit alongside returns; it does not protect a board that ignores the benefit purpose. The Windfall Clause, if it ever applies to this series, would obligate it like the other 33 series, with its threshold and terms still blank for counsel.
Open questions
- Which location question does Locator.X answer first — navigation, mapping, search, or something narrower — and for whom, in which place?
- What is the location-data policy, in writing: what is collected, from whom, with what consent, how precisely, how long it is kept, who can see it, and how a person opts out or deletes it?
- Is Locator.X shared infrastructure beneath its neighbours (SmartCiti.X, ParkingSmart.X, Get.Delivery DAO) or a standalone service — and who maintains it and pays for it in each case?
- What precision, freshness, and failure modes will the series state publicly, and how will a wrong answer be corrected and disclosed?
- Who are the named human stewards, and what written limits bind the agents that operate the series day to day?
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 “Locator.X (S08)” 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.