01 / Formatting
Equivalent references do not always look equivalent.
T1374071104100T137.407.11.041.00A compact source string and a punctuated manufacturer reference can represent the same canonical watch.
WristAtlas
Reliable watch identity layer
Messy watch data in. Reliable watch identity out.
Listings, feeds, and catalogs rarely describe the same watch the same way. WristAtlas is Blue Dial Labs' canonical identity product for resolving supported evidence to a stable Brand → Collection → Model → Reference → Variant hierarchy while keeping provenance and uncertainty visible.
The identity problem
One watch can arrive as several different records.
Reference punctuation changes. Model names get shortened. Source-specific identifiers do not travel across systems. Variant detail may be incomplete or contradictory. Without a stable identity layer, downstream software has to reconcile the same product repeatedly.
02 / Fragmentation
Source records are evidence, not shared identity.
Listings and feeds may carry their own titles, SKUs, aliases, and taxonomy. Those values remain useful evidence, but they are not a durable cross-source key by themselves.
03 / Uncertainty
Ambiguity should not disappear downstream.
A plausible reference match is different from a resolved variant, physical watch, authenticity judgment, or seller assessment. WristAtlas keeps those boundaries explicit.
Guided resolution demo
See inconsistent source evidence become one canonical identity.
These four guided examples use references already represented in Blue Dial Labs' current canonical catalog work. They are illustrative, do not call a public API, and do not imply broader catalog coverage.
01
Messy source evidence
“Rolex Submariner 124060 blk dial full set”
02
Canonical result
- Brand
- Rolex
- Collection
- Submariner
- Model
- Submariner
- Reference
- 124060
- Variant
- —
- Matching confidence
- High
This demo uses a canonical catalog record for reference 124060. No WatchVariant is asserted for this curated example.
What this demonstrates: canonical identity can remain stable even when source wording changes.
What this does not claim: a production API response, comprehensive coverage, authenticity, physical-watch identity, seller quality, or numerical confidence precision.
Canonical output
A stable hierarchy replaces repeated free-text reinvention.
The hierarchy is product identity. It does not collapse a listing, purchase, ownership record, or individual physical watch into the same concept.
- 01BrandRolex
- 02CollectionSubmariner
- 03ModelSubmariner
- 04Reference124060
- 05VariantNot asserted
Stable identity
Canonical values are not copied listing titles.
Source wording can change while the canonical reference remains the same identity anchor.
Evidence lineage
Normalization should not erase provenance.
WristAtlas is designed to distinguish what a source reported from the canonical interpretation built from that evidence.
Confidence boundary
Unknown stays unknown.
A resolved reference does not require WristAtlas to invent a variant or silently upgrade incomplete evidence into stronger certainty.
Built on explicit data standards. Canonical identity is only useful when provenance, source roles, timestamps, confidence, and evidence boundaries remain explicit.
From evidence to usable identity
Resolve once. Carry the identity forward.
WristAtlas establishes the product identity layer. Downstream systems can then work from a stable reference while preserving the evidence and confidence that supported it.
01
Listings, feeds, aliases & identifiers
02
WristAtlas resolution
03
Canonical identity + provenance + confidence
Used now
WristOwl
Canonical Pursuit targets, offer matching, reference-level market evidence, and ownership continuity depend on knowing what watch the evidence represents.
Explore WristOwlFuture · only if validated
External identity use
Potential future uses include catalog reconciliation, reference lookup, external-identifier mapping, professional data feeds, or API access. None is announced as a public production service today.
Downstream value
Stable identity makes better data work possible.
WristAtlas is not valuable because it adds another watch database. Its job is to give supported evidence a durable identity so comparisons, history, and downstream decisions can refer to the same product consistently.
Cross-source continuity
Different source strings can converge on one canonical reference without discarding the original evidence.
Reference-level history
Market observations can attach to a durable product identity rather than temporary listing wording.
Like-for-like comparison
Downstream systems can determine whether evidence belongs to the same reference before attempting economic or product comparison.
Explicit uncertainty
Unresolved variants and lower-confidence identity evidence can remain visible instead of silently becoming authoritative facts.
Internal first, external later
Built for WristOwl first. Designed so the identity layer can stand on its own later.
WristAtlas exists today because Blue Dial Labs needs canonical watch identity for its collector decision product. Keeping that capability product-neutral preserves the option for broader use without forcing a second commercial operating surface before external demand is validated.
Company Data StandardsNow
Canonical identity infrastructure for Blue Dial Labs products
Now
Canonical reference data and supported aliases
Now
Provenance and confidence-aware identity boundaries
Later
External access only after product and commercial validation
Watch data conversations
Working through an identity or reference-data problem?
Blue Dial Labs is interested in learning where watch identity breaks in real catalogs, feeds, and software workflows. That conversation does not imply pilot access, a catalog-audit service, or a public WristAtlas API.