pitch.industries.org.ai
Every industry, one URI that answers.
The industry dimension of the economy as dereferenceable canon: seeded from the open standards, enriched into typed records, licensed CC BY 4.0 — the coordinate surface the estate's citing records key their G2 industry lines on. Every liveness claim in this deck checked cold, gaps carried in amber.
↓ scroll · arrow keys
The industry axis of the economy is published as code lists — NAICS, SIC,
UNSPSC — in PDFs and lookup pages built for human clerks. None of it
dereferences. None of it is typed. So every vertical system re-encodes
"which industry is this" as its own strings, no two systems' strings
agree, and when an agent reads a record that says automotive, it gets
folklore, not a fact it can resolve.
That was survivable while software was operated by people who could hold the taxonomy in their heads. It is not survivable for an estate that compiles businesses from records: branded verticals here — the auto rail, the finance and credit rails, the insurance rail, the sales tribes — carry a G2 line naming their industry, and a machine will read that line. The coordinate has to answer, or the record is citing a ghost.
Resolve industries.org.ai/automotive cold and this is the record — not
a landing page, a typed canon entry:
Thing / Industry / Automotive
Automotive — Motor vehicle manufacturing
Extends: Industry (schema.org.ai)
Reference: Automotive — industries.org.ai
naicsCode: 3361
naicsUrl: census.gov/naics/?input=3361
relatedTo: naics.org.ai/api/3361
Usage: import { $ } from 'sdk.do'
await db.query({ subject: $.Automotive })
License: © 2026 .do · CC BY 4.0 — attribution with backlink
The seed is carried verbatim — the NAICS code and its census URL are on
the record, so the open standard stays inspectable under the enrichment.
The type is canonical — the record extends Industry on the estate's
own substrate. And the usage line is a query, not prose: the coordinate
is built to be a subject in someone's database, not a paragraph in a
deck.
The automotive coordinate dereferences — industries.org.ai/automotive
returned 200 on a cold check (2026-07-30) with the typed record above:
Thing / Industry / Automotive, "Motor vehicle manufacturing", Extends:
Industry, NAICS 3361 seed, sdk.do usage, CC BY 4.0 license line.
The served record's own relatedTo link — naics.org.ai/api/3361 — did
not answer a cold check (2026-07-30). The seed code and its census URL
are on the record either way; the seed registry link is carried here
as intent until it resolves.
This surface is not a brand looking for users — it is already load-bearing.
The estate's role register (roles.tsv) binds canon.industries to
https://industries.org.ai, filed active, and the citation graph is
the proof: the automotive rail keys its G2 on /automotive, the
finance and credit rails on /financial-services, the insurance rail
on /insurance, the accounting rail on /accounting, the mortgage
rail on /mortgage, and the sales tribes on /coaching,
/solar-energy, /real-estate, /media, /live-events,
/performance-marketing, /professional-communities and
/consumer-services. That is the citing set today — the apis rails and
the sales tribes; the projections that carry no G2 industry line yet
are exactly that, and are not implied in.
The canon.industries role binding and the citation graph above are
book facts today — the binding filed active in the estate's own role
register, the citing records filed in the estate's own repo — neither
yet resolvable by a stranger's curl. Both post as evidence when the
register and the citing records are published at public URLs.
Concreteness over adjectives, on the canon's own terms: each door below was checked cold on 2026-07-30 and carries its own state. Serving is a liveness fact about a URL — nothing here asserts coverage or identity beyond what its own evidence shows.
The apex serves — industries.org.ai returned 200 on a cold check
(2026-07-30). What it renders today is the canon browser under the
sibling substrate's masthead: title "schema.org.ai - Schema.org
Vocabulary Reference", schema.org.ai nav and identity throughout.
The naming seam, worn openly (apis.autos shared-apex precedent): the zone serves the schema.org.ai application, and only the record pages' Reference line ("Automotive — industries.org.ai") carries this domain's own name. This record files the apex-under-own-identity as intent, not as a fact.
A second coordinate dereferences — industries.org.ai/real-estate
returned 200 on a cold check (2026-07-30) as a typed record: Thing /
Industry / RealEstate, "Real estate property management and leasing",
Extends: Industry.
Coverage, stated plainly: of the industry URIs the estate's own records
cite today, /automotive and /real-estate answer cold, and the rest —
/financial-services, /insurance, /accounting, /mortgage,
/coaching, /solar-energy, /media, /professional-communities and
siblings — returned 404 on the same cold check (2026-07-30). Those URIs
are minted names awaiting records, and this canon says so rather than
letting the citations imply otherwise.
The motion is B2A: the canon is consumed by dereference — an agent (or a record, or a build script) cites a URI and GETs it. There is no funnel, no signup, and nothing to buy; adoption is citation, and the citation graph inside this estate is the first cohort. The boundary with the masthead is by rule, not by tone: do.industries narrates the whole machine to a human evaluator deciding where years of work go; this surface answers one machine question — which industry is this, and what does that mean — for the builder or agent writing a record. One ICP, one motion, on each side of the line.
A canon built for machine callers should hand them the index:
industries.org.ai/llms.txt returned 404 on a cold check (2026-07-30).
The machine index is carried as intent until it serves.
Price model: none. The served records post their own terms — CC BY 4.0, attribution with backlink — and attribution is the only consideration. This is not modesty; it is architecture. A coordinate system is only authoritative if citing it is free, and every commercial term in the estate lives on the record of the door that charges it: the rails meter functions, the doors recruit supply, the cells sell regulated work. The canon answers what an industry is; it never competes with the doors that sell what gets done in one.
Resolve one yourself: industries.org.ai/automotive answers cold.
If this was forwarded to you: industries.org.ai is the industry dimension of an estate built on one thesis — business logic is now executable, so the coordinates businesses are keyed on must dereference. One URI per industry, seeded from the open standards verbatim, enriched into typed records, licensed CC BY 4.0. Every factual claim above carries its own state and evidence URL, checked cold — including the five ambers it wears openly: the apex still serving under the sibling schema.org.ai masthead, the cited coordinates that 404 today, the seed registry link that does not resolve, the unpublished machine index, and the role binding and citation graph that are still book facts. Judge a coordinate system the way this deck judges itself: resolve a URI and read what comes back. Start at industries.org.ai/automotive.