Pasco Roadmap is built so that you don’t have to take my word for anything. This page explains where the figures come from, how they are checked and corrected, how the site keeps up with new documents, and what part AI plays.
Where the figures come from
Every figure on the site, and every statement marked †, comes from a public document: the county’s traffic boards, newsletters and budgets, Commission agendas and minutes, the MPO’s plans, FDOT’s traffic counts and the Turnpike’s studies. The site currently has 144 figures from 54 documents.
Each figure is written down once, in a data file, together with the document it comes from, where in that document it appears, and the date of the document. The pages don’t contain the numbers themselves; they look each one up when the site is built. So a figure reads the same everywhere it appears, and fixing it in one place fixes it everywhere.
The site won’t build if a page asks for a figure that doesn’t exist, or a figure names a document that isn’t listed. Tap any underlined figure to see its document, and the exact page or board it comes from. All of them are listed on All figures & sources.
Facts and readings kept apart
A fact is what a document says, such as a traffic count printed on one of the county’s boards. A reading is what someone makes of it. Where a project page gives a reading, it shows the figures it is built from, and differences and totals are worked out from those figures when the site is built rather than typed in by hand. Every project gets the same sections and the same questions, whether a lot or a little has been published about it.
How the figures are checked
Verified by a human 88%Checked by AI only 12%Not yet checked 0%
Checked by AI means Claude, an AI assistant, has compared the figure with its document.
Verified by a human means I have compared it with the document myself. Only I mark figures verified.
You can check too. Each figure’s details box has a short form: compare the figure with its document and say whether it matches. Every answer is treated as a claim to check against the document, however many people send it.
New projects wait for checking. A new project is added only once I have verified at least 90% of the figures in every project already on the site, so the site never takes on figures faster than they can be checked. Where things stand: Rangeland Blvd corridor 99%, Sunlake Blvd corridor 20%.
How mistakes and changes are handled
Mistakes are corrected in public. When a figure was wrong, the correction is listed on the project’s page, for example the corrections on the Rangeland guide.
Newer documents don’t erase older ones. When a newer document gives a different figure, the new one is added and the old one is kept, marked as replaced. All figures & sources lists what has changed and when.
How the site keeps up
Once a day the site rebuilds itself from what has already been approved, with nothing new added, so “coming up” and the Timeline move on by themselves as dates pass.
Every week an automated check looks through the county’s Commission agendas, meeting packets and minutes, the county’s project pages and the MPO’s agendas for anything new about the projects here, and sends me a report. Nothing it finds goes on the site until I have read the document and decided to add it.
The part AI plays
I use Claude, an AI assistant, to write the code behind the site, to help find and read through the documents, to pull figures out of them, to make the first check of each figure, and for first drafts of the writing. I read and check everything before it goes up, decide what is published, and verify the figures myself. Because every figure is linked to its document, you can check any of it without trusting either of us.
The technical side
The code is public. Everything that makes the site, including every figure’s data file, is on GitHub at github.com/patricka3s/rangeland, with the full history of every change.
Every change is reviewed before it goes live. Each change is made as a separate proposal (a “pull request”) that is built and checked automatically, and goes live only when I approve it. The version line at the foot of every page shows which change is live.
Built from plain files. The site is assembled by a tool called Eleventy from data files and page templates, and hosted on GitHub Pages.
No ads, no tracking. The only visit counter is GoatCounter, which sets no cookies, stores nothing on your device and does not identify you.
Get in touch
A question, a document I’ve missed, a project you’d like covered, or something that doesn’t look right: send me a message here. To say whether one particular figure matches its document, it’s quickest to tap the figure and use the form in its box.