How I build the data

If you read something wrong, please let me know.

What powers this tracker

This project combines hand-reviewed jurisdiction files, official legislation links, public political datasets, and a curated RSS news pipeline. The goal is not to mirror one vendor feed. It is to assemble a stablecoin-policy map that can be traced back to public documents.

At a high level, there are five source layers: US legislation, international country files, news feeds, politician data, and map/geography assets. Individual bills and news cards keep their own source links in the UI; this page is the rollup.

Where legislation comes from

US federal bills are sourced from Congress.gov. US state bills are sourced from official legislature links and normalized through LegiScan 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.

Some of these classifications will age badly as rules move. If you work on one of these jurisdictions and think the read is off, please reach out.

How news and summaries work

The homepage overview and entity news tabs are generated from curated RSS feeds in data/news/feeds.json. The poller fetches feed items, filters for stablecoin relevance, summarizes article text, and writes the results to data/news/summaries.json.

Regional homepage summaries are then regenerated from those entity news buckets and copied to public/news-summaries.json, which the homepage reads at runtime. News is useful for recency, but it is not the authoritative legal source for a jurisdiction’s status.