Editorial Process
TinyHomeList covers a topic — local tiny-home zoning, regulation, and builder information — where misinformation has real downstream costs. A buyer who relies on a wrong zoning claim can lose tens of thousands of dollars on land they can't legally build on. This page describes how we work to keep that from happening.
Who writes the content
Most state pages, city pages, and builder profiles are produced by an editorial team working under the direction of Jake Montazeri, the site's founder. Some content is AI-assisted in the research and drafting phases; every regulatory claim is reviewed and dated by a human before publication. We never publish under fabricated author identities — every byline links to a real, verifiable person or to this institutional page.
How we source
- Primary sources first. Municipal codes (Municode, American Legal Publishing, eCode360), state legislatures, city/county planning departments, official zoning maps. Builder profiles draw from the builder's own website plus public records (state contractor licensing, RVIA/NOAH/ANSI/L&I/HCD certifying bodies).
- Secondary sources are dated and cited. When we cite a news article, local reporting, or a real-estate platform, the citation includes the URL and the date of access.
- Every regulatory claim is dated. "As of [Month, Year]" appears at the point of the claim, not in a footer. If we can't verify a claim with a primary source, we hedge in print — "Per public reporting, last confirmed [date]" — rather than state it as fact.
- We don't fabricate. Ordinance numbers, bill numbers, statute IDs, community names, builder relationships, certifications — all of these are verified against original sources. When something can't be verified, the page says so.
How we review
Each piece of content goes through a quality gate before it ships. For pSEO city pages, that gate is a machine-readable check (src/lib/city-content-quality.mjs) plus a jurisdiction-specificity check that requires the zoning summary to cite a real local code section, ordinance, or zoning district — not just a generic state-level overview. For blog posts, every post must tie to (a) an interview, (b) original data or analysis, or (c) first-hand experience. We do not publish commodity content — the "7 Tips for First-Time Buyers"-style aggregations that AI models can produce from training data alone.
How we handle corrections
If you spot a regulatory claim that has changed, a broken citation, or a builder profile that needs updating, please reach out via the contact form. We update the underlying content, advance the page's lastmod, and note the correction in the page's commit history. Corrections that materially change a published claim are also logged in the editorial team's review notes.
What we don't do
We don't accept payment for builder placement or for "favorable" coverage. Featured builder slots are based on editorial judgment of completed work and verifiable customer outcomes, not paid placement. We don't run sponsored content disguised as editorial. We don't generate per-query-variation pages (the "scaled content abuse" pattern Google's spam policy targets), and we don't add machine-readable AI files like llms.txt — see how we approach AI search for the longer version of that argument.
For the full editorial rubric — banned phrases, citation format, voice rules — see our public editorial-policy.md in the repo. The same file is what our content-producing skills and CI lint read at every build.