Field-guide appendix
Archive counts
Static counts generated from the canonical registry records.
These figures summarize registry coverage, lifecycle aftermath, exclusive status counts, chain coverage, marketplace scope, and review-quality signals. They are not live market analytics, rankings, uptime monitoring, or price data.
Review-state note: reviewed_staging means a source-reviewed canonical draft, not final public-quality certification. Missing lifecycle or successor data means “not recorded in the registry”, not proof that no event occurred.
Archive at a glance
Marketplaces
Events
Evidence notes
Active-side
Faded-side
Dead
Source-reviewed drafts
Public-quality reviewed
Core analysis
What the archive looks like now
Active-side, faded-side, and unknown
These three groups are mutually exclusive and sum to the total.
Active-side status mix
Active-side is active + limited.
Faded-side status mix
Faded-side is inactive + dead + rebranded + acquired + merged. Dead and transitioned are subgroups, not extra records.
Lifecycle aftermath
How marketplace histories end or continue
Recorded lifespan buckets
Only records with both canonical launch and end years are included; same-year records remain a separate bucket.
Successor & migration coverage
These are recorded lifecycle links and events, not inferred outcomes.
| Faded records with successor / migration | 11/162 · 7% | Canonical faded-side records with a successor marketplace or an asset-migration event recorded. Absence means not recorded. |
|---|---|---|
| Successor links recorded | 16 | Marketplace records with canonical successor_marketplace. |
| Predecessor links recorded | 16 | Marketplace records with canonical predecessor_marketplace. |
| Migration events recorded | 0 | Distinct marketplaces with canonical asset_migration_announced events. |
| Lifespan computable | 15/385 · 4% | Only records with both canonical launch_year and end_year are included in lifespan buckets. |
Lifecycle event depth
Number of canonical event records linked to each marketplace, grouped as zero / one / multiple.
Breakdowns
Where the records cluster
Coverage & provenance
Evidence coverage is descriptive registry provenance depth, not a marketplace safety or quality score.
| Archive coverage | 100% · 385/385 | Records with a marketplace archived URL present. |
|---|---|---|
| High-reliability evidence coverage | 3% · 10/385 | Records with at least one canonical high-reliability evidence item. |
| Archived-evidence coverage | 100% · 385/385 | Records with at least one evidence item carrying an archive URL. |
| Source-reviewed drafts | 385 · 100% | Canonical public drafts with source review; not final public-quality certification. |
| Public-quality reviewed | 0 · 0% | Records that have completed the stricter public-quality review state. |
| Records with open flags | 385 · 100% | Canonical records that still expose unresolved review work. |
| Evidence depth | 383 with multiple sources | How many records have more than one evidence note. |
| Quality flags | 1563 | Total open review flags; one record may carry multiple flags. |
| Generated from | 385 records | 388 events and 811 evidence notes. |
Registry timelines
Launch and end-year distributions
Launch-year distribution
Yearly counts are shown as a column distribution.
End-year distribution
Unknown-heavy data stays visible without pretending it is a normal ranking.
Deep quality notes
Review signals
Evidence depth
Confidence labels
Machine-readable review state
Coverage / quality
How to read these figures
Generated from 385 marketplaces, 388 events, and 811 evidence notes.
