Verify scope
State exactly what was verified—ownership, namespace, identifier, source or action.
Product direction
Trust layer
Make identity, provenance and rights inspectable.
Trust is not a generic badge. It is a precise statement about the entity, controller, identifier, action, source or right that was actually verified.
ENTITY PASSPORTNIKE:4827NAMESPACE
#
ACTIONVERIFYBRAND CONTROL
The principle
A persistent identifier only matters if its history, ownership, lifecycle and safety decisions remain understandable.
01 · Scoped verification02 · No code reuse03 · Provenance04 · Lifecycle and tombstones
System model
From identity to useful action.
Preserve history
Record versions, transfers and tombstones without silently recycling identities.
Expose confidence
Return transparent lifecycle, safety and provenance signals to authorized consumers.
Truthful product status
Built in layers.
Explained without blur.
Available now
Safe unknown-code behavior
LinkCode never guesses an unrelated destination when a code does not exist.
Foundation live
Verification and lifecycle fields
The data model separates verification, safety, visibility and lifecycle states.
Product direction
Signed provenance and rights
Cryptographic provenance, rights evaluation and portable trust receipts are later-phase work.
Human + machine
One identity.
Several interfaces.
application/linkcode+json
{
"schemaVersion": 1,
"entity": {
"id": "NIKE:4827",
"type": "namespace",
"verificationStatus": "scoped"
},
"actions": ["verify"]
}Resolution examples
Designed to travel.
VERIFY
BRAND CONTROLREAD
VERSION 12 · ARCHIVEDAUTHENTICATE
SERIAL · PROVENANCEClear answers
What to know.
Does verified mean LinkCode endorses the entity?
No. Verification must always identify its scope and does not imply a general endorsement.
Can a retired code be reassigned?
The architecture is designed around durable tombstones and no silent identifier reuse.