How I build the data

If you read something wrong, please let me know.

What powers this tracker

This project combines normalized jurisdiction records, official legislation links, a versioned legal corpus, and an official-source update pipeline. The goal is to assemble a Stablecoin policy map that can be traced back to public documents.

The public tracker uses four source layers: official legal and regulatory documents, normalized jurisdiction files, first-party update feeds, and map assets. Individual rules and update cards retain source links; paid playbooks pin versioned claims and evidence through the authenticated domain API.

Where legislation comes from

US federal bills are sourced from Congress.gov. US state bills are sourced from official legislature links and discovered through Open States when available. International stablecoin frameworks are stored country by country in data/international/*.json, and each file includes primary legal or regulator links for the measures described there.

How bills get tagged

Each bill gets a set of impact tags. For the stablecoin lens, the main dimensions are issuance, reserve backing, consumer protection, cross-border treatment, and monetary sovereignty. Tags describe what a measure does. They do not say whether it is normatively good or bad.

Tagging is done with Claude Sonnet 4.6. The model reads each bill’s summary and picks applicable tags from a fixed taxonomy. I spot-check the output, but I do not claim every tag is hand-labeled.

How stance gets picked

A jurisdiction’s stance can be favorable, review, restrictive, or none depending on the lens. For stablecoin policy, the most visible map coloring is the issuance outcome: non-bank permitted, bank-only, private stablecoin banned, or unclear / in progress.

Those judgments come from the current legal position and the weight of active measures. Enacted rules count more than floor passage; floor passage counts more than committee movement; committee counts more than filed bills.

Editorial classifications can become stale as rules move. The generated timestamp and source links make that limitation visible; corrections are welcome.

How news and summaries work

The homepage overview and entity news tabs are generated from first-party feeds in data/news/feeds.json and government APIs configured in data/news/professional-sources.json. The poller retrieves official documents, preserves document IDs and versions, filters for stablecoin relevance, and writes the results to data/news/summaries.json.

Regional homepage summaries are then regenerated from those entity news buckets, published as an immutable dataset release, and read through /api/public/datasets/news-summaries. News is useful for recency, but it is not the authoritative legal source for a jurisdiction’s status.