How RoyaltyBook is built
The well directory, land registry, map, production totals, and open data all come from one validated release. This page states the joins, evidence gates, and gaps.
The publication pipeline
- Source current status and land description. Read the official ECMC Daily Activity Dashboard export and keep current producing rows with complete section-township-range locations and recognized well classes.
- Reconcile the physical well. Match the base API exactly to ECMC’s well Feature Service for field, spud date, and actual measured coordinates.
- Aggregate one complete production year. Query the same base API in ECMC’s annual COGIS result and sum all returned wellbores for January–December 2025; no name matching is used.
- Build exact land keys. Group published rows by literal county, section, township, and range. A land key is not promoted to a spacing unit, pooled area, lease, or ownership finding.
- Validate and resume. Reject malformed or conflicting inputs. Cache each valid production response atomically so an interrupted import can resume without discarding completed work.
- Gate adjudicated claims. Every order, unit, lease, or instrument verdict needs an official saved artifact, a matching SHA-256 checksum, and an append-only human decision. Empty ledgers authorize nothing.
- Publish once. Profiles, land pages, map data, counts, sitemap URLs, and both open-data files regenerate deterministically from the same rows.
Live bridges stay candidates
The address tool and each land page send only a validated section-township-range reference to a same-origin Cloudflare Pages Function. It reads ECMC’s current section-order summaries, caps and caches the official response, and returns source links. A section result can be historical, amended, vacated, broad-area, or non-governing; applicability still requires reading the application lands and later history.
The Weld recorder path stays manual because the county’s terms prohibit automated searching. RoyaltyBook organizes parcel, subdivision, STR, and legal-description clues, then sends the user to the official index. The private unclaimed-property tool likewise prepares local search passes and never sends a person’s name to RoyaltyBook.
We publish the instrument. We do not declare the owner.
Yes: “Deed recorded in 1962 conveying an undivided 1/4 mineral interest.”
No: “The Smith family owns 1/4 of the minerals.”
The numbers right now
- Published well profiles
- 500
- Land-record pages
- 242
- Reported operator names
- 13
- Substantive operator pages
- 12
- Mapped profiles
- 500
- Adjudicated decisions
- 9
- Evidence artifacts
- 13
- Production year
- 2025
- ECMC snapshot
- August 9, 2026
- Release
- 2026.08.09-weld-500
View Colorado ECMC’s downloadable-data page · Read ECMC’s production-completeness note.
Known gaps, stated plainly
- This is a 500-well, 242-land-record release, not a complete Weld County or Colorado inventory.
- A land page is a literal PLSS grouping, not a unit, parcel, lease, or ownership map.
- The live bridge returns order candidates; it does not choose the governing order or prove parcel participation.
- The recorder packet guides a manual search; it does not build a title chain or interpret legal effect.
- Reported well production is not a royalty calculation or payment record.
- A missing profile is not evidence that no well, unit, order, instrument, or interest exists.
Maintainer and corrections
RoyaltyBook is maintained in Colorado. Found a source conflict? Email a correction. Material corrections remain visible in the append-only ledger.