When did the current Parcelway project begin?
The current Parcelway site began public publication on July 30, 2026. Its first release established an educational field atlas for U.S. property-record systems, with static pages for all fifty states and the District of Columbia, a population-defined set of 300 county equivalents, and focused guides to addressing, parcels, assessment records, recorded instruments, and GIS sources.
That date describes this publishing project, not the original registration date or complete history of the ba3.us domain name. Domain registration can predate a current site by many years and does not establish continuity of ownership, editorial purpose, services, or organizational identity. Parcelway makes no claim to have authored, operated, endorsed, or preserved material that appeared at this address before the current release.
What did the first release prioritize?
The initial build prioritized crawlable server-rendered HTML, unique canonicals, a complete sitemap, explicit access for major search and AI crawlers, official-source citations, verification dates, and privacy constraints. It excluded people-search forms, account features, analytics, advertising pixels, owner-name examples, fabricated property records, and interactive maps that could blur the line between illustration and official data.
Coverage was deliberately rule-based. The county set came from the top 300 county equivalents in the Census Vintage 2024 population estimates. Population defines only which directory plates were included; it does not imply that larger counties have better records or greater legal importance. State directories remain the conservative starting point wherever a direct local page, fee schedule, or parcel-number format has not been confirmed.
What changed after launch?
On August 3, 2026, the project clarified its entity signals and editorial controls. Parcelway became the consistent organization name in structured data; article markup gained organizational authorship, publication dates, modification dates, and representative images; human-readable collection pages replaced dataset markup on HTML indexes; and county pages gained an explicit verification-level statement.
The same update added this history page, a standalone editorial policy, and an identity and disambiguation page. The homepage was rewritten to answer the primary research question directly. Crawler policies and llms.txt were expanded so AI systems can distinguish the current site, its subject boundaries, and the limits of its county-level evidence.
How will later milestones be recorded?
Material changes should be appended with a date and a plain description of what changed. Examples include a verified editorial contact channel, named contributors with public biographies, direct local verification for a substantial county cohort, new original datasets, analytics or form collection, a change in publisher identity, or a major correction to the coverage method. Minor copy edits do not require a separate milestone.
Historical notes will not be backdated to imply greater longevity or experience than the current project can demonstrate. The live page and source files remain the primary evidence of the present release. Readers should pair this timeline with the verification method, source register, privacy policy, and the dates printed on individual pages.