Stable or Gone (SOG) is a public historical registry for stablecoins and closely related stable-value assets. It records identity, issuers and organizations, backing and stabilization models, redemption, legal and regulatory context, deployments, launches, incidents, migrations, wind-downs, failures, evidence, access conditions, and unresolved questions.
Public site: https://www.stableorgone.com/
SOG is not a live price dashboard, trading terminal, safety ranking, market-cap ranking, yield leaderboard, or source of investment advice.
Canonical stable assets: 119
Organizations: 109
Relationships: 131
Events: 194
Evidence: 585
Evidence Relations: 585
Deployments: 186
Market Access Records: 12
Archive recorded: 463
Archive not recorded: 122
Detail routes: 422
Metadata-checked detail routes: 422
Production/canonical checkpoint semantics:
review authority entry commit: c9588b092277bd14d87ce9209ba087e4752b3346
current production commit: dynamic; verify via deploy-production workflow and Issue #479
last canonical-changing implementation commit: 77e80dd3e2a62fea53ea0eabe91ef78a2d8ab1da
canonical hash: sha256:f386c1043ca5e83cafbd88e99746d0609aab0154ed48de1970677758a66ed5fa
canonical file count: 466
official origin: https://www.stableorgone.com
legacy-host 301: complete and strict-gated
A fixed work-item commit is an immutable entry checkpoint, not a perpetually current production claim. Current main and production equality is verified dynamically by .github/workflows/deploy-production.yml, the domain-migration gate, provenance/output-parity checks, relevant production visual review, and Issue #479.
PR #523: merged and production-verified canonical Market Access implementation
PR #534: merged and production-verified closeout
PR #535: bounded Japan Market Access Expansion Review Batch 1 authority
PR #536: Market Access review no-go closeout
Current implementation authority: REVIEW GATE
Current active review authority: Evidence Archive Payload Verification Batch 2
Review mode: review-only
Later canonical implementation lane authorized: no
The active Batch 2 lane deterministically selects ten current unarchived canonical Evidence identities using the historical Queue v7 non-ranking priority semantics after excluding the ten Evidence identities already reviewed in Payload Verification Batch 1. It then permits manual exact-source and dated-Wayback payload review only.
Canonical archived_url changes remain prohibited in this review authority. Any exact dated archive URLs judged promotable require a separate reviewed and merged implementation authority.
Registry records
Stats
Compare
Compare presets
Access & Regulation Explorer
Change Timeline
Update Feed
Maintenance Log
Guides
machine-readable projections and manifest discovery
The 2026 regulation guide cluster is published and the shared Guide/readability remediation is complete. Guide content is maintenance-only unless a material regulatory change, correction/source update, or justified search/content gap requires new work.
The canonical public origin is:
https://www.stableorgone.com
It governs canonical links, hreflang, OGP, JSON-LD, sitemap URLs, robots, machine-readable outputs, production verification, and deployment reporting.
The legacy host sog.badjoke-lab.com receives an exact path- and query-preserving HTTP 301 through public/_worker.js in Cloudflare Pages Advanced Mode. PR #530 made the migration contract strict in production and scheduled audits.
Read the merged current versions in this order before non-trivial work:
AGENTS.md
docs/spec-governance.md
docs/roadmap.md
docs/deployment-policy.md
docs/roadmap-amendments/2026-08-09-evidence-archive-payload-verification-batch-2-review-authority.md
docs/quality/evidence-archive-payload-verification-batch-2-review-authority-spec.md
config/evidence-archive-payload-verification-batch-2-review-authority.json
config/evidence-archive-payload-verification-batch-1.json
docs/migration/evidence-archive-maintenance-queue-v7-pr403.json
config/evidence-archive-maintenance-queue-v7-pr403.json
current named source reviews, baselines, queues, audits, and validators
Merged repository authority outranks chat memory, handoff prose, issue discussion, stale branch state, generated reports, and unmerged drafts. Historical PR-specific checkpoint artifacts remain historical evidence.
archive recorded: 463
archive not recorded: 122
candidate target count: 10
Batch 1 reviewed identities excluded: 10
selection semantics: Queue v7 deterministic non-ranking order
manual archived payload review required: yes
canonical archive additions authorized by this review: 0
Redirect-only results, CDX metadata alone, replacement targets, or payloads whose claim scope cannot be independently verified are insufficient. reviewed_no_safe_change is a valid outcome. Automatic archive promotion is prohibited.
PR #523's bounded transition is complete and production-verified:
Evidence: 584 -> 585
Evidence Relations: 584 -> 585
Market Access Records: 8 -> 12
Archive recorded: 462 -> 463
Detail routes: 422 -> 422
The JPYSC records remain provider-scoped to SBI VC Trade / VCTRADE in Japan and are not generalized into country-wide availability or future transfer capability.
RLUSD × SBI VC Trade / BITPOINT — no-go
USDC × SBI VC Trade / BITPOINT — no-go
JPYSC × SBI VC Trade / BITPOINT — no-go
promotable pairs: 0
promotable Market Access Records: 0
Market Access expansion may be reopened only on material new source evidence, such as an FSA provider/handled-instrument register change, a published stablecoin intermediary relationship, BITPOINT-specific function-level evidence, or a material BITPOINT/VCTRADE integration change.
- Reviewed canonical data only is published as registry truth.
- Unknown values remain explicit until reviewed evidence supports replacement.
- Monitoring, candidate, discovery, editorial-research, and private material is not canonical data.
- Stable assets, organizations, events, evidence, deployments, legal profiles, reserve components, income profiles, known unknowns, and Market Access Records remain distinct record families.
- Rebrands, aliases, wrapped representations, migrations, and deployments do not become separate canonical assets without scope and lineage review.
- Automatic candidate promotion is prohibited.
- Missing product-list entries are not canonical unavailability evidence.
- Guide/editorial context is not automatically canonical asset-level availability, approval, legality, or safety evidence.
npm ci --no-audit --no-fund
npm run validate:active-workstream
npm run validate:data
npm run check
npm run buildNormal merged changes publish automatically from main through .github/workflows/deploy-production.yml. Material UI work additionally requires desktop/mobile artifact capture and direct inspection under the active specification. A repository merge is not itself proof of production parity.
/version.json
/data/manifest.json
/llms.txt
/ai.txt
/data/stats.json
/data/stats-history.json
/data/comparison.json
/data/access-regulation-index.json
/data/change-timeline.json
/data/update-feed.json
/data/maintenance-log.json
The public safety boundary remains:
canonical_only = true
includes_unreviewed_candidates = false
includes_internal_monitoring = false
includes_private_notes = false
Use GitHub Issues for public, source-backed corrections that can be discussed openly. Do not submit private personal information, unsupported allegations, investment recommendations, or candidate material as canonical facts.