Foundation / Authenticity and Scan Tags
The zHezar scan tag is intended to use secure NFC technology to connect a physical product to its official Product Identity. A copied link, browser effect, visible code, or physical possession cannot replace a live server-validated interaction.
Reference only. No NFC scan, live verification, authenticity result, product record, Claim, Ownership, transfer, replacement, support case, or protected action exists here.
Physical product / secure NFC / server authority
Current evidence
Bounded input, privacy-safe logging, and a temporarily unverifiable result demonstrate fail-closed behavior. They do not show that a product is counterfeit.
Five authority layers
The physical piece stays central. Its credential, live verification, permanent Product Identity, and current Ownership authority remain related but distinct.
The garment and its approved physical configuration.
A secure NFC credential associated through controlled production.
The authoritative decision about the current live scan and token state.
The permanent official product, artist, Edition, configuration, and history.
Separate canonical account authority created only through an approved process.
High-level verification flow
This explanation stops before keys, values, counters, thresholds, provider configuration, and other sensitive implementation details.
A supported device interacts with the scan tag.
The request reaches the official verification boundary.
A live interaction is distinguishable from a copied static link.
Approved cryptography, freshness, and token rules are checked.
Product Identity, token, Claim, and Ownership states remain separate.
Only approved public information and separately authorized next actions appear.
Six customer-safe states
Device behavior, connectivity, damage, unsupported technology, copied links, retired credentials, outages, malformed requests, and security failures require different language and recovery.
The server recognizes an authentic registered token and may return safe Product Identity information.
Public information may be readable, but it cannot prove current physical interaction or authorize a protected action.
The service could not confirm authenticity now. Protected actions fail closed and static-link bypass is prohibited.
The current credential cannot authorize protected actions while approved identity and token history remain distinct.
The product may still be authentic. Evidence and any remedy require an approved protected process.
State what could not be verified without automatically publishing a counterfeit finding.
Information boundary
A public result should explain the official product and current safe state without exposing another person, weakening security, or turning telemetry into surveillance.
Product Identity ≠ Ownership
Platform Ownership is created only by an authorized first Claim, completed approved transfer, or another approved ownership process. A public scan cannot perform those actions.
These facts do not independently create platform Ownership
Hardware and support
A scan tag can be damaged, unreadable, inactive, retired, replaced, unsupported, or temporarily unreachable. Safe status and continuity must preserve history.
Approved review may distinguish the authentic product from current tag functionality.
Protected actions stop while the prior token remains connected to the official record.
Essential explanation and Help remain available without pretending every device scans identically.
Cached public information must be labelled unverified or previously known; protected actions remain blocked.
Public-promise limits
Public language must distinguish a strong system, one scan result, token functionality, platform Ownership, legal title, and financial value.
Counterfeiting is impossible.
NFC can never fail.
Every device scans identically.
A copied URL proves physical possession.
Public verification establishes Ownership.
A scan resolves every legal title dispute.
A retired authentic token is counterfeit.
The system guarantees resale value.
Readiness / July 2026
This table records repository evidence and unresolved gates. It is not a verification service, registry, token inventory, ownership ledger, support system, or production dashboard.
Static education only; no scan, product result, or protected action.
Input is bounded and verification returns temporarily unavailable with no authenticity claim.
Production token, configuration, keys, custody, reconciliation, and migration are unapproved.
Attachment, comfort, wash, durability, read range, placement, and production testing remain incomplete.
Dynamic verification, UID binding, replay defense, monitoring, and production domains are not configured.
No live product, token, Claim, Ownership, provenance, or protected action exists.
Evidence, inspection, remedy, successor, history, privacy, and support operations remain unresolved.
Current public route
How It Works provides the broader sequence. Legal & Trust shows document readiness. Help provides general routing without a scan-tag case.