How This Guide Is Maintained
The U.S. Stablecoin Field Guide is written, edited, and published by Collin Canright under the FinTech Rising imprint of Canright Communications. This page explains how to tell what is current, what has changed, and who has checked it.
Ownership
One editor is responsible for every page. There is no sponsored or paid placement anywhere in the guide, including the Company Directory; organizations appear because research or reported developments name them. Editorial standards and the evidence rules are on Source Framework & Criteria and The Ferguson Method.
Versions and cadence
The guide is released in numbered versions. The Digital Money Adoption score is re-evaluated quarterly; each score is fixed at a stated evidence cutoff and is not revised after publication. When a new score is released, the prior baseline is kept at its own address, marked as superseded, so that earlier figures remain citable. The weekly News Digest is published Fridays between releases.
The current version and release date appear in the metadata line at the top of every content page. The Release Notes record what changed in each release, content first and infrastructure second, with corrections listed under the release in which they were made. The Roadmap shows planned releases.
Page History
Every content page ends with a collapsed Page History block generated from the publishing repository at build time. It lists the date, release, and description of each reader-facing change to that page: new material, corrections, and verification passes. Formatting and infrastructure changes are omitted. The "Page updated" date in the metadata line is the date of the most recent change of any kind. The weekly News Digest is the exception: each issue is dated in its title, so the page carries no Page History, and a correction to an issue is noted in that issue.
A verification pass means the page was re-read against its sources and found current, with no substantive change. A page that has not had a verification pass or a content change since the last release should be read with that in mind.
Corrections
Factual errors are corrected on the page where they occur and recorded in two places: the page's own Page History, and the Corrections list in the Release Notes for the release in which the fix was made. Corrections are not made silently.
Outside review
Pages that have been read by an outside reviewer carry a "Reviewed" date in the metadata line and name the reviewer in Page History. Reviewers read for factual accuracy and evidentiary support; editorial judgments remain the editor's.
Machine-readable metadata
Each page carries hidden metadata for search engines and AI systems: author, publisher, version, creation and modification dates, status (canonical, reference, or archived), evidence cutoff where a page presents scored findings, and supersession links between score baselines. The vocabulary follows Dublin Core terms with a schema.org Article block. Readers who use AI assistants can point them at this guide knowing that each page declares what it is, when it was last changed, and whether a newer version exists.
Comments
Comments and corrections are welcome at collin@canrightcommunications.com.
Page History
1 reader-facing change since 2026-10-12; last change 2026-10-12 (v1.0).
Show all changes
| Date | Release | Change |
|---|---|---|
| 2026-10-12 | v1.0 | How This Guide Is Maintained notes the News Digest has no Page History |
Infrastructure and formatting commits are omitted. Release-level detail is in the Release Notes.