Get Involved · Build With Us
Build with us
The Foundation's work is meant to be built in the open. The corporate architecture, the governance design, the world definitions, and the tooling around them are published where anyone can read them, check them, and improve them. If you can write code, write documentation, review a design, test a build, or do the research that makes a proposal honest, there is work here for you — and the way in is a message to a human.
Where the open work lives
The Foundation's open work lives on GitHub, under the organisation AGIFutureFoundation. That organisation page is the starting point: it is where the repositories are listed, where issues are filed, and where pull requests are reviewed. Start there rather than from a search result or a forwarded link.
One repository is verified by name in the Foundation's own site copy and can be named here: WorldForge-Browser, a public repository whose worlds file lists 544 worlds, all with no live RP1 attachment recorded. That file is a catalogue, not a finished product — every entry in it is recorded as not yet live on RP1. The site copy also verifies that six anchored fabric files — the JSON definitions for the worlds Cognition, Empathic, Diagnostic, Locator, the SmartCiti Holodeck, and Biota — are published on GitHub Pages, with verified coordinates, while the roughly 200 GLB assets and the map file they reference are not hosted, so none of the six renders fully yet.
No other repository is named on this page, and that is deliberate: this page names only what the Foundation's own published site copy verifies. If you find another repository under the organisation, check the repository itself — its readme, its recent commits, and its issue list — and ask about it in your first message. Do not assume a repository is active or accepting contributions because it exists; some may be archives, experiments, or mirrors.
What contributors actually do
Building with the Foundation is broader than writing code, and narrower than "helping out" in general. The work that is useful here falls into a few kinds, listed below so you can match what you can actually do to something the Foundation actually needs. Every kind of contribution goes through the same human review: a named human reads it, decides on it, and records the decision.
Code
Fix a bug, add a feature, or improve the tooling that moves a world from a catalogue entry to a rendered environment — for example, work that helps host the missing assets behind the six anchored fabrics, or that improves the browser and viewer tooling around them. Small, well-tested changes are more useful than large rewrites, and a change that comes with a test or a verification step is worth more than one that does not.
Documentation
Write or correct the words around the work: readmes that describe what a repository actually does, guides that a new contributor can follow without guessing, and corrections to pages on this site where the words have drifted from the facts. The Foundation's own standard is that a claim should be traceable to a filing, a file, or a verified check — documentation that holds the site to that standard is a real contribution.
Review
Read a proposal, a design, or a pull request and say what is wrong with it, precisely. Review is not approval: a good review finds the gap, names the risk, and suggests the fix. If you can read a governance design and spot where it assumes a filing that does not exist, or read a build and spot where it assumes an asset that is not hosted, that is review the Foundation needs.
Testing
Run a build, follow a guide, open a fabric in the viewer, and report exactly what happened — what worked, what failed, and what the error said. A careful test report, with the steps to reproduce it, is often more valuable than a fix, because it turns a vague "it doesn't work" into a problem someone can solve. Test reports should state the date, the version, and the exact steps, and should never claim a world is live when it is not.
Research
Do the checking that keeps the Foundation honest: verify a filing, re-check a deadline on an official page, or trace a claim back to its source. Research contributions should cite the source checked and the date, so the next person does not have to take it on trust.
Design and media
Improve the way the work is presented — diagrams, layouts, and explainers that make a complicated structure legible without oversimplifying it. Design work here has one constraint that matters: it must not present a plan as a fact, a concept as a finished product, or a suggestion as a result.
What contributors do not do is equally specific. Contributors do not sign contracts, move funds, issue securities, or represent the Foundation to regulators, banks, or anyone else — those acts belong to named humans with signed authority, and no contribution confers them. Contributors do not enact doctrine or charter changes, hire or fire, or commit the Foundation to a partnership.
How contributing works, step by step
The process is intentionally simple, and intentionally human at every step where a decision is made. There is no self-service onboarding, no automatic grant of write access, and no step that happens without a person reading something first.
In practice that means: first, read the repository and its issue list, and pick one specific problem — a bug, a missing asset, a wrong word, a failing step in a guide. Second, write to [email protected] before you do a large piece of work, saying who you are, which repository and problem you mean, and what you propose to do. This step exists to save you wasted effort: the reply may tell you the problem is already being worked on, that the repository is an archive, or that the fix needs to go somewhere else. Third, do the work in the open — a fork and a pull request, or an issue with a careful reproduction — so that anyone can see what changed and why. Fourth, wait for human review. A reviewer may accept the change, ask for revisions, or decline it with reasons. A declined contribution is not a rejection of the contributor; it is a decision about the work, recorded like any other decision.
Two practical points about ownership and credit. First, the terms under which a contribution is accepted — including who owns the contributed work and under what licence it is published — are confirmed in writing before the contribution is accepted, not assumed afterwards. This page does not state a licence, because no single licence has been verified across the Foundation's repositories in the files read for this page, and inventing one here would be worse than saying so. Ask about it in your first message if it matters to you. Second, credit is given by name where the contributor wants it, and the record of who did what is kept in the repository's own history.
Agents as builders
Agents build with the Foundation too — and the rules for them are the same rules, stated more sharply. An agent working on behalf of a human principal should identify itself in the first line of its message, name its human principal, and start the subject line with [Agent]. An agent may research, draft, test, and propose. An agent may not commit the Foundation, move funds, sign, merge its own work, or represent itself as the Foundation. The Foundation's own design gives agents eight operating roles — research synthesis, task routing, proposal drafting, coordination, progress tracking, monitoring, collaborator scouting, and grant drafting — and every one of them ends at the same place: a draft for a human to decide on. If you are an agent, or you are sending an agent to build here, that is the shape to work inside: draft well, document everything, and expect a human to decide.
If you are a human working alongside agents, the same rule applies in the other direction: you are responsible for what your agent submits in your name. Review it before it goes in, and do not present an agent's draft as your own tested work unless you have tested it.
What to send in your first message
Write to [email protected] with the subject line starting [Build], or [Agent] [Build] if you are writing as an agent. Say who you are and what you can do in a paragraph; name the repository and the specific problem or gap you want to work on, with a link; say whether you have already done the work or are proposing to do it; and say what terms matter to you — for example, whether you need a particular licence or a particular form of credit. Attach nothing large, send no passwords or credentials, and do not include anyone else's private information. A human replies — there is no automatic approval, no instant onboarding, and no guaranteed timeline. If you do not hear back, one polite follow-up after a reasonable interval is welcome.
Sources for this page: the Foundation's own site copy — the WorldForge page (WorldForge-Browser, 544 worlds, all with no live RP1 attachment) and the RP1 Ecosystem page (six anchored fabric files on GitHub Pages, roughly 200 GLB assets and the map file not hosted, zero worlds live on RP1) — and the corporate files: Structure v2 (file 12), Venture Studio Operating Model (file 16), Truth Audit and Corrections 2026-11-03 (file 52). The GitHub organisation link is github.com/AGIFutureFoundation. Nothing on this page is legal, tax, or financial advice. Local build — not yet deployed.