pitch.occupations.org.ai2026

occupations.org.ai

The workforce, as canon.

One URI per occupation — seeded from the open standard, enriched into machine-readable canon: the credential lattice, the reserved acts, the register class of the work. The namespace the estate’s labor doors already key their people to, published so any agent can dereference it. Every liveness claim below checked cold, with its own evidence URL — including the ones about this canon’s own unbuilt front door.

occupations.org.aithe G2 canon of who does the work — the labor half of the twin pair with industries.org.ai (what the economy makes), and the namespace the estate’s gigs doors, sales seats, and regulated cells already key their people to5 posted · 4 pending

“Occupation” is still a string

Labor products are being built agent-first — routing work to credentialed humans, gating acts on licenses, settling on sign-off. But the coordinate at the center of all of it is still a bare string. Every marketplace re-invents its own occupation list; who-may-sign-what lives in statute PDFs and tribal knowledge; credential lattices are re-derived product by product and can never be cited, because each one is private. An agent that asks “who may sign this?” today gets a listicle, not a coordinate.

The open standards already name the workforce: O*NET-SOC enumerates the occupations of the economy the way NAICS enumerates its industries. What the standards were never built to be is dereferenceable — a URI an agent resolves into a canonical record. That gap between a published catalog for humans and a resolvable canon for machines is the whole reason this surface exists.

Seed → canon — enriched IS canonical

G1 · Seed — the open ground truthevery occupation starts as a row of the published open standard, ingested verbatim and never touched by a model — the standard is the seed, not the ceiling
G2 · Canon — one URI per occupationthe seed enriches into a canonical, machine-readable record: credential lattice, reserved acts, register class of the work — open to every agent that can dereference a URL
Consumers — records, doors, agentssibling records key their tribes to the coordinates; agents resolve “who may sign this?” into a credential class instead of a listicle

The enrichment shape is design intent, stated as such: the record grammar — what a coordinate must carry for the doors to route on it — is what the estate’s live labor decks already assume, and the canon publishes when it can serve it. The seeds and the substrate it publishes against serve today:

Posted

The seed layer serves — standards.org.ai, the estate’s home for the open standards the economy is compiled from, returned 200 on a cold check (2026-07-30).

standards.org.ai
Posted

The $type substrate serves — schema.org.ai, the vocabulary this record’s own frontmatter agrees against, returned 200 on a cold check (2026-07-30).

schema.org.ai

Already load-bearing — the namespace precedes the surface

The unusual fact about this canon: its demand is not projected, it is recorded. Across the estate’s own brand records, the labor-touching decks key their ICPs to this namespace by URI — the legal door to occupations.org.ai/lawyer, the clinical doors to physician, registered-nurse, and nurse-practitioner, the claims door to claims-adjuster, the engineering door to professional-engineer, the sales seats to setter and closer. The estate has been writing checks against this name in its own books, one coordinate at a time, before the apex serves.

Pending

Candour about those coordinates: every occupations.org.ai URI in the estate’s records is minted-but-unratified — they sit in the estate’s open mint queue, and none of them dereferences today. The namespace is load-bearing as a filing convention; it becomes load-bearing as infrastructure when the apex serves and the mints ratify. This record states the gap rather than blurring it.

gate: minted occupation URIs ratified and dereferencing at the apex

The doors keyed to it

occupations.org.ai/lawyer

gigs.lawyer

attorneys and USPTO patent agents — the legal cell’s supply door

occupations.org.ai/claims-adjuster

gigs.claims

carrier-side adjusters — the insurance cell’s supply door

occupations.org.ai/physician

gigs.doctor

physicians — clinical sign-off

occupations.org.ai/registered-nurse

gigs.care

RN-grain review of nursing work

occupations.org.ai/nurse-practitioner · pharmacist

gigs.health

telehealth clinicians

occupations.org.ai/professional-engineer

gigs.engineering

PEs — the seal is the act

occupations.org.ai/tax-professional

gigs.tax

CPAs and EAs — tax sign-off

occupations.org.ai/accountant

gigs.accountants

accountants — the books-side door

occupations.org.ai/mortgage-loan-originator

gigs.mortgage

MLOs — the mortgage labor door

Each row is a sibling record that files its tribe as an occupation coordinate under this canon — the supply doors of the labor family, plus the sales seats and regulated cells not shown. Liveness is each door’s own claim to make, on its own record, with its own evidence; two reference points are posted here because this deck routes readers to them:

Posted

The flagship labor door serves — gigs.expert, the generic door of the expert register for credentialed professionals no vertical door names yet. Cold check 2026-07-30.

gigs.expert
Posted

The reference vertical door serves — gigs.lawyer, the legal cell’s supply door, keyed to occupations.org.ai/lawyer in its record. Cold check 2026-07-30.

gigs.lawyer

Agents don’t browse — they resolve

One motion, B2A: the canon’s consumer is a machine dereferencing a coordinate. A sibling record’s frontmatter resolves an occupation $id; a resolver answers “who may sign this?” with a credential class; an agent grounds a labor decision in a record it can cite. The canon completes no transaction — every motion that ends in money completes on the doors, on their own posted terms. Publishing and being dereferenceable is the entire go-to-market, which is why the only launch that counts is the apex serving.

The masthead names a human-capability exchange above the labor doors; that face is still a reserved name, and its state is carried — amber and openly — on the records that own it, not re-claimed here. What this canon owes that future exchange is the same thing it owes every consumer: coordinates that resolve.

Where it stands — pre-launch, stated plainly

Posted

What the apex actually serves today, posted as a live fact: on a cold check (2026-07-30) occupations.org.ai answers 200 with a hosting “Coming Soon” placeholder — “Domain occupations.org.ai is not yet provisioned,” marked noindex — not the canon. This deck is the name’s first real record.

occupations.org.ai
Pending

Nothing of the canon itself serves yet: no occupation URI dereferences, no llms.txt, no machine index. This claim flips green when a cold request to a minted coordinate returns the canonical record.

gate: the occupations canon serving at the apex — one dereferenceable record per minted URI, seeded from O*NET-SOC
Pending

The estate’s own roles register files canon.occupations → occupations.org.ai as active while the apex serves a provisioning placeholder — the books lead the door here, and this record wears the contradiction rather than picking a side silently. Queued estate-side with the other filing seams.

gate: roles.tsv canon.occupations filing reconciled with the live apex
Pending

The twin’s state, carried because the pairing is load-bearing to this record’s positioning: on a cold check (2026-07-30) industries.org.ai answers 200 with a page titled as the schema.org.ai vocabulary reference — a shared-surface seam of the same class the estate has queued elsewhere. The twin’s own record carries its own claims; this deck only refuses to imply a serving twin canon that a curl would falsify.

gate: industries.org.ai apex serving the industries canon as itself
pitch.occupations.org.ai2026

The ask

The canon’s name is occupations.org.ai — its coordinates already bind the estate’s labor records, and until the apex serves, this record is the name’s front door. The nearest serving door it feeds is gigs.expert.

If this was forwarded to you: occupations.org.ai is the labor half of a canon pair — industries.org.ai names what the economy makes; this names who does the work — seeded from the open O*NET-SOC standard and enriched into one dereferenceable URI per occupation, carrying the credential lattice, the reserved acts, and the register class of the work. The estate’s own labor doors already key their tribes to these coordinates. Every factual claim above carries its own state and evidence URL, checked cold — including the four ambers this record wears openly: the canon that does not yet serve at its own apex, the minted-but-unratified coordinates, the roles-register filing that leads the door, and the twin apex’s shared-surface seam. Judge the canon the way it will have to be judged to matter: by whether its names resolve, and by how plainly it labels the ones that don’t yet.

5 posted · 4 pending