The complete developer kit in a single document: the safety model, the public API, your personal API key, and a ready-to-paste Base44 prompt that builds a working directive end to end. This same file ships at the root of the public GitHub repository as its README companion.

OFFWORLD CAREERS — CORPS FIELD KIT

The official developer kit of the Offworld Workforce Authority (OWA). A live, citizen-governed speculative-fiction platform — and a real developer training program where you build AI features that ship to production the same day.

Live site: https://offworldcareers.com Fiction notice: all agencies, positions, treaties, and worlds are invented. The Development Corps, its directives, verification protocols, and compute-ration economy are real program mechanics running on this live platform.

1. What this system is

| Layer | What it does |
|---|---|
| **The Board** | 100+ numbered personnel requisitions across 9 sectors, published daily by automated pipelines |
| **The Canon** | Single source of truth for physical constants; everything users create is validated against it |
| **Citizen Programs** | The Common Archive, Tribunal, Expeditions, World Register, Petitions Desk — all AI-adjudicated |
| **The Development Corps** | The training program: claim a directive, build it, face the Inspector, get merged |
| **AI Officials** | The Registrar, the Provost, the Inspector — in-app agents with strict, auditable scopes |

2. The Safety Model (why you can't break it)

You never touch the core. Your work enters as data and sandboxed capability — tools run through the ToolBridge with schema validation, timeouts, and metering. No external code executes in the trusted core.
Provenance on everything. Every artifact carries your callsign and a REFERENCE flag separating the Authority's originals from community additions.
No duplicate work. Directives are claimed exclusively; tool names are unique; a nightly audit sweeps for collisions.
One merge key. Repository contributions arrive as pull requests; the Inspector rules clause by clause; only the maintainer merges. No secrets ever exist in the repo.
Everything is metered and logged. AI calls debit your ration balance; every invocation and verdict enters a permanent public ledger.

3. Step one — build the worked example (no key needed)

This kit contains zero keys, on purpose. You build first, connect later. Create your own app at base44.com and paste the prompt below. It builds directive ED-M6-003 (Canon unit-conversion tool) end to end. Everything except the final "Register" press works without any key: composing the definition, Validate (the validate action is public), and the local test bench.

Build me a small single-page app called "Canon Unit Converter Workbench".

CONTEXT: I am building directive ED-M6-003 for the Development Corps at
https://offworldcareers.com. The platform exposes a public JSON API at
POST https://offworldcareers.com/functions/toolRegistry. Validation is
public; registration requires a personal API key that I will obtain LATER
and paste into a settings field — do NOT hardcode any key anywhere.

REQUIREMENTS:
1. A form to compose a tool definition: name (snake_case), display title,
   description, input JSON schema, output JSON schema, and an LLM_PROMPT
   handler template for converting between units: g (gravity), atm
   (pressure), sols (Mars days), AU (distance), °C.
2. A "Validate" button that POSTs { "action": "validate", "definition": ... }
   and renders any contract findings clause by clause. This needs NO key.
3. A Settings panel with a single field "Corps API Key (OWA-…)" stored in
   localStorage, empty by default, with a link to
   https://offworldcareers.com/corps/desk labeled "Issue your key here".
4. A "Register" button that POSTs { "action": "register", "apiKey": <the
   key from Settings>, "definition": ... } and shows the issued tool number
   (TL-…). If the key field is empty, disable the button and show:
   "Issue your personal key at the Engineer's Desk first."
5. A test bench that runs 3 sample conversions through my handler prompt
   locally (via an LLM call) and shows input/output pairs I can paste into
   my submission notes.
6. Institutional, document-like design: ivory background, deep indigo ink,
   monospace technical data.

When done, remind me to submit my artifact at
https://offworldcareers.com/corps/desk with action "submit" for ED-M6-003.

4. Step two — get commissioned and connect through OWA

Only now, with a working app in hand, do you connect it to the live platform:

Enlist at https://offworldcareers.com/corps (choose CADET / ENGINEER / ARCHITECT).
Activate your commission at the Engineer's Desk: https://offworldcareers.com/corps/desk
Register your external Base44 app in the OWA Connect · App Registry panel and copy its Client ID.
Your app must send users to https://offworldcareers.com/connect/authorize with OAuth-style PKCE (client_id, exact redirect_uri, state, code_challenge). The user signs in only at Offworld Careers. Your app exchanges the returned code at universeGateway and stores the short-lived access token in session storage.
Legacy OWA-… personal keys remain available for developer tools, but new Expansion Kits should prefer OWA Connect so all registration, users, moderation, and recovery stay central.
Claim the directive at https://offworldcareers.com/corps/backlog and submit your artifact link at the desk. The Inspector rules clause by clause; you hold one appeal.

5. The public API

Base URL: https://offworldcareers.com/functions/<desk> — JSON over HTTPS, POST only. Authentication: new connected apps use Authorization: Bearer <short-lived OWA Connect token>. Legacy developer desks also accept header X-Corps-Key: OWA-… or payload field "apiKey".

| Desk | Purpose | Key required |
|---|---|---|
| `toolRegistry` | Register a tool under the nine-clause Uniform Tool Contract | **Yes** (validate is public) |
| `corpsDesk` | Claim directives, submit artifacts, check rations, appeal | Commission email |
| `worldDesk` | File canon-validated world modules | **Yes** — central OWA identity or legacy key |
| `surfaceDesk` | Deploy installations onto living worlds; file field reports | **Yes** — central OWA identity or legacy key |
| `universeGateway` | OWA Connect login, app registration, shared network discovery, homes/forests/assets | **Yes** for writes; public for network reads |
| `petitionDesk` | File petitions into the public decision queue | No |

Fair-use quotas (anti-abuse)

Every write action is metered per identity — your callsign when keyed, a hashed caller fingerprint when anonymous (raw IPs and keys are never stored). Exceeding a quota returns a standard 429 QUOTA_EXCEEDED with the roll-over window.

| Action | Keyed quota | Anonymous quota |
|---|---|---|
| `toolRegistry` → `validate` | 30 / hour | 30 / hour |
| `toolRegistry` → `register` | 5 / 24 h | key required |
| `worldDesk` → `register` | 3 / 24 h | central OWA identity required |
| `surfaceDesk` → `deploy` | 2 / 24 h | key required |
| `surfaceDesk` → `observe` | 5 / 24 h | key required |

Register a tool (example)

POST /functions/toolRegistry
{
  "action": "register",
  "apiKey": "OWA-…your-key…",
  "definition": {
    "name": "canon_unit_convert",
    "displayTitle": "Canon Unit Converter",
    "toolDescription": "Converts between Canon-sanctioned units: g, atm, sols, AU.",
    "inputSchema": "{\"type\":\"object\",\"properties\":{\"value\":{\"type\":\"number\"},\"from\":{\"type\":\"string\"},\"to\":{\"type\":\"string\"}}}",
    "outputSchema": "{\"type\":\"object\",\"properties\":{\"result\":{\"type\":\"number\"},\"note\":{\"type\":\"string\"}}}",
    "handlerType": "LLM_PROMPT",
    "handlerSpec": "Convert {value} {from} to {to} using Canon constants. Return the numeric result and a one-line institutional note."
  }
}

A registered tool becomes live: the Registrar can invoke it in real correspondence, credited to your callsign, with every invocation logged publicly.

Surface Operations — build inside a living world

Every ratified world runs a continuous daily simulation with a live 3D Ground View (/worlds/<module>/ground). Through surfaceDesk, an OWA Connect session or legacy key lets you act inside those worlds — and your work becomes physically visible in the shared feed:

Deploy an installation. It renders as a real structure in the world's 3D scene, credited to your callsign, and permanently alters the outpost's daily telemetry:

POST /functions/surfaceDesk
{
  "action": "deploy",
  "apiKey": "OWA-…your-key…",
  "moduleNumber": "WM-2026-0001",
  "installation": {
    "name": "Meridian Relay Mast",
    "kind": "ANTENNA_ARRAY",
    "purpose": "Wide-band listening array supporting the outpost's anomalous-phenomena watch."
  }
}

Kinds and their daily simulation effects: GREENHOUSE (+oxygen), SOLAR_ARRAY (+power), DRILL_RIG (+resources), HABITAT / MONUMENT (+morale), ANTENNA_ARRAY (raises the chance of detecting anomalous phenomena — worlds carry a hidden xeno index and a contact ladder: SIGNS → BIOSIGN → SIGHTING → CONTACT; at SIGHTING, anomalous lights begin appearing in the world's live sky).

File a field report. Enters the world's public outpost log under your callsign; reports flagged "anomalous": true feed the contact ladder directly:

POST /functions/surfaceDesk
{
  "action": "observe",
  "apiKey": "OWA-…your-key…",
  "moduleNumber": "WM-2026-0001",
  "anomalous": true,
  "observation": "Repeating narrowband pulse logged at 0340 local, bearing 221, no registered traffic. Recording archived for the Registrar."
}

The world's 3D feed (installations and anomalies included) can be embedded anywhere via the iframe snippet on each Ground View page — so what you build inside the shared world is also showable on your own site.

6. Contributing to this repository

Fork this repo. Never commit secrets — all keys live in platform environment variables.
Claim a directive first (unclaimed work is not reviewed).
Open a pull request titled with the directive number, e.g. ED-M6-003: Canon unit converter.
Your PR faces the Inspector's clause-by-clause review and the verification protocols. Only the maintainer merges.

Directive authoring standards, style guide, and worked examples: https://offworldcareers.com/corps/authoring

7. Instructors & cohorts

Running a bootcamp or class? The Cohort Desk (https://offworldcareers.com/corps/cohorts) gives you seats, per-seat progress, ration spend, and a clean separation between the platform's REFERENCE artifacts and what each student produced.

The Corps Field Kit