One thesis: a neutral resolver serves resolution; it never homes identity — so where a brand runs its own Digital Link door, that door rides first-class in the linkset and resolution passes through it — id.org.ai's resolution, served at this door — because a resolver that replaces the brand's door has just rebuilt the walled network it claimed to fix.
If you own a brand's digital and DTC surface, you have been pitched the other model: join the network, publish into it, and the network becomes the answer for your products. The record is authoritative because you joined. That model has a name in this family's writing — it is the anti-reference — and this post states the opposite posture precisely, because "neutral" is a claim that has to be architectural to mean anything.
Home versus serve, defined
Every identifier scheme has an issuer that homes allocation. GS1 licenses company prefixes and the GTINs under them to brand owners; the U.S. federal rule and the OEMs home VIN allocation; ISBN allocation is homed with the international agency and its group agencies. Nobody else gets to mint those identities, and no resolver should pretend to.
Serving resolution is a different job: given an identifier that someone else legitimately issued, answer "where are the doors for this thing" — and answer it the same way for a reader who has joined nothing. The GS1-Conformant Resolver standard 1.2.0 (ratified January 2026, royalty-free under the GS1 IP Policy) is built on exactly this separation. It is ownership-agnostic by design: nothing in it restricts resolver operation to GTIN owners; a resolver's description file at /.well-known/gs1resolver simply declares which keys it serves. GS1's own resolver at id.gs1.org — seventeen primary key types in its live description file — is the canonical default, not a monopoly.
What "resolving through" looks like in the JSON
The standard's linkset behavior (RFC 9264) is the mechanism: asked for the full picture, a conformant resolver "SHALL NOT redirect but SHALL return a full list of links." Here is the shape of the linkset this door serves for a GTIN whose brand publishes its own resolver:
{
"anchor": "/01/09506000134352",
"gs1:defaultLink": {
"href": "https://id.brand.example/01/09506000134352",
"title": "Brand-operated Digital Link resolver",
"note": "resolved through — the brand's door is the default, not a competitor's copy of it"
},
"gs1:pip": { "href": "https://id.brand.example/01/09506000134352?linkType=gs1:pip" },
"linkset": [
{ "linkType": "scheme", "href": "/schemes/gtin" },
{ "linkType": "enrichment", "href": "…", "license": "public-domain", "source": "usda-fdc" },
{ "linkType": "traceability", "href": "https://epcis.dev/…" },
{ "linkType": "transactions", "href": "https://transactions.dev/…" }
]
}Two properties matter. First, the brand's own door is the gs1:defaultLink — a phone scan routed through this door lands where the brand decided scans land. The door carries the brand's link; it never shadows it, caches its content, or interposes a landing page. Second, every link added around it carries its own provenance and license class, so the additions are auditable rather than mysterious. A linkset is a list of doors; this one says whose each door is.
Why neutrality is architecture, not policy
A policy of neutrality is a promise from a vendor; an architecture of neutrality is a property a reader can check. Three checkable properties do the work here:
- Allocation is never claimed. The resolver mints no identities. Vehicle identity is the worked precedent inside this family: the vehicle estate's own constitutional rule is that the government and the OEMs home VIN allocation while the platform serves resolution — the same law, ratified before this resolver existed, and generalized here to every scheme.
- License classes travel with links. A link to an enrichment record names its source and license class in the linkset itself (the provenance envelope post is the full argument). A resolver that cannot say where a link's content came from is one acquisition away from becoming a walled catalog.
- Pass-through beats replication. Brand-published targets are resolved through, live, at answer time — never scraped into a copy that would drift stale and, worse, would make the served record compete with the brand's own.
Contrast the network model on each property: it homes the record (yours, inside their tenancy), it does not label per-attribute rights, and it replaces your door with membership. The record it produces is authoritative for members, about members, inside the network. That is a fine business. It is not a resolution layer.
What this buys the brand seat
For your seat specifically, the through-not-over posture means the 2D investment you are already making — the mark, the domain decision, the resolver you stand up or rent — is not hostage to any aggregator's index. A conformant third-party resolver that encounters your GTIN carries your door as the default; readers who arrive through this door end up with you. And the doors added alongside — the trace door, the transaction-context door, the identity door at id.org.ai — are ones no brand resolver carries today, which is why a neutral layer is worth existing at all.
The one sentence underneath all of it, the same sentence this family repeats on every surface: the record holds up whether or not the reader joined anything. A resolver either makes that sentence true or it is the thing the sentence is about.
The hosted resolution door — description file, conformant linksets, your brand's door carried first-class; resolution itself is id.org.ai's, served through this door — is the network half of this property. Get an API key and say what arrives at your door; provisioning follows the list, in order.
Keys open the network half of the verb set. Get an API key — say what arrives at your door, and the provisioning order follows the list.
We answer in writing. We take at most five conversations a month, only when you ask for one, and only after you already have the written read.