FORM OWA-104 · OPEN SOURCE PROGRAM · PUBLIC ISSUE
Contribute on GitHub
This entire platform — every desk, agent, and world — is built in the open and synchronized to GitHub. Students and engineers fork the repository, build against real directives, and ship features that go live for every citizen. Your keys are never in play: all secrets live outside the codebase, in the Authority's vault.
THE CONTRIBUTION PIPELINE · SIX STATIONS
FORK THE REPOSITORY
The platform's full source is synchronized to GitHub. Fork it — every secret and API key lives outside the code, so nothing sensitive ships with the repo.
CLAIM A DIRECTIVE
Pick an open directive from the board (or author one at the Authoring Desk). Claim it at the Engineer's Desk so the board shows your callsign.
BUILD ON YOUR FORK
New desks, new worlds, new tools — built to the Technical Canon and the Uniform Tool Contract, in the Authority's register.
OPEN A PULL REQUEST
Reference your directive number in the PR title. The maintainer reviews; the Inspector rules on your submission clause by clause.
MERGE AND GO LIVE
Merged work deploys to the live platform. Points post to your commission, your callsign enters the public engineering record, and your feature serves every citizen.
CLAIM YOUR CERTIFICATE
Every merged directive builds toward your numbered commission certificate — a public, verifiable record of what you shipped.
THE PLATFORM API · BUILD WITHOUT THE CODEBASE
You do not need repository access to ship on this platform. These public desks accept JSON over HTTPS at https://offworldcareers.com/functions/<desk> — register tools, file worlds, and submit directive artifacts from your own code, agents, or MCP-style tool clients. Every registered tool runs live through the Registrar's ToolBridge.
POST /functions/toolRegistry
Register a tool under the nine-clause Uniform Tool Contract. Requires your personal API key (issued at the Engineer's Desk). The tool becomes invocable by the Registrar on the live site.
{ "action": "register", "apiKey": "OWA-…your-key…",
"definition": { "name": "orbit_window_calc",
"displayTitle": "Orbit Window Calculator",
"toolDescription": "Computes transfer windows between two registered worlds.",
"inputSchema": "{\"type\":\"object\",\"properties\":{...}}",
"outputSchema": "{\"type\":\"object\",\"properties\":{...}}",
"handlerType": "LLM_PROMPT", "handlerSpec": "..." } }POST /functions/corpsDesk
Your commission: claim directives, check rations, submit artifacts for Inspector review, file appeals.
{ "action": "submit", "directiveNumber": "ED-M6-003",
"callsign": "your-callsign", "email": "you@example.com",
"artifactUrl": "https://github.com/you/your-fork/pull/12",
"notes": "Implements all six acceptance criteria; tests attached." }POST /functions/worldDesk
File a world module. Parameters are validated against the Technical Canon's hard limits before ratification.
{ "action": "file", "worldName": "Veyra Deep",
"gravityG": 1.4, "atmosphere": "N2/CH4", "pressureAtm": 3.2,
"lore": "…at least 90 characters of institutional lore…",
"ownerCallsign": "your-callsign", "ownerEmail": "you@example.com" }POST /functions/petitionDesk
Programmatic petitions: propose content, images, or designs. AI-triaged into the public decision queue.
{ "action": "file", "type": "NEW_CONTENT",
"petitionText": "…state your case, 30 characters minimum…",
"email": "you@example.com", "callsign": "your-callsign" }Authentication: writes to the Tool Registry require a personal API key (header X-Corps-Key or payload apiKey), issued and rotated at the Engineer's Desk. Identity always binds to the key — never to caller-supplied fields. Abuse is rate-limited, AI-triaged, and logged.
THE SAFETY MODEL · HOW AN OPEN UNIVERSE STAYS SOVEREIGN
Hundreds of engineers can extend this world simultaneously without any of them being able to break, duplicate, or seize it. Six layers make that possible.
01 YOU NEVER TOUCH THE CORE
External work runs in a sandbox: tools execute through the ToolBridge with schema validation, timeouts, and metering — never as code inside the platform. Worlds, entries, and petitions are data, adjudicated before they render. Nothing you submit can execute in the trusted core.
02 PROVENANCE ON EVERY ARTIFACT
Every tool, world, entry, and directive artifact carries its owner's callsign and a REFERENCE flag separating the Authority's originals from community additions. Instructors see exactly what each seat produced versus what the platform shipped with — per seat, on the Cohort Desk.
03 NO DUPLICATE WORK
Directives are claimed exclusively — a CLAIMED directive is locked to one callsign until merged or released. Tool names are unique in the registry. A nightly duplicate audit sweeps community content for collisions.
04 CODE MERGES ONLY THROUGH THE MAINTAINER
Repository contributions arrive as pull requests against a fork. The Inspector rules clause by clause, verification protocols run on every merge, and the maintainer holds the only merge key. No secret, key, or credential ever exists in the repository.
05 EVERY ACTION IS METERED AND LOGGED
AI calls are debited from personal ration balances; invocations, verdicts, and denials enter permanent public ledgers. Abuse is rate-limited at the desk, triaged by AI, and block-listed by the Authority.
06 AN INFINITE WORLD UNDER ONE KEY
The universe grows without limit — worlds, tools, agents, lore — because contributions are data and sandboxed capability, never control. Final verdict on everything that stands rests with the Authority alone.
NOT AN ENGINEER? THREE MORE WAYS TO CONTRIBUTE
DESIGNS, IMAGES AND CONTENT
Propose your own images, plates, and texts to replace or extend what stands. Every filing enters the public AI decision queue.
The Petitions Desk →FINANCIAL SUPPORT
Fund the platform's AI operations by purchasing compute-ration resupply packs. Every ration meters real inference.
The Rations Store →LORE AND WORLDBUILDING
File worlds, lifeforms, theories, and mission logs to the Common Archive and build your public service record.
File to the Archive →WHAT YOU CAN BUILD
- · New desks and pages
- · Worlds for the World Register
- · Tools under the nine-clause contract
- · Agents grounded in the Canon
WHAT PROTECTS THE PLATFORM
- · Secrets never ship in the repo
- · Maintainer review on every PR
- · The Inspector rules clause by clause
- · Verification protocols on every merge
WHAT YOU TAKE WITH YOU
- · A public engineering record
- · Points on your commission
- · A numbered certificate
- · Shipped features on a live platform
REPORT FOR DUTY
Enlist for a commission, study the directive board, then fork and build. Institutions can open a cohort and bring an entire class.
Contributions are governed by the Terms of Use and the Copyright and IP Notice. Merged work becomes part of the platform; contributor callsigns stand in the public record.