A useful answer must show its work.

01 · Jurisdiction

Address geography is matched before a city rule is applied.

A mailing address can name a city even when another municipality, county or special authority issues the permit. The Permit Navigator sends a complete address to the U.S. Census Geocoder and reads the matched incorporated place and county geography.

A Census geography match is not a parcel survey and does not resolve every special district, utility, historic overlay or project-specific agency. The result keeps that limit visible and offers a manual fallback when matching is unavailable.

02 · Local starting point

Approximate location changes recommendations, never published facts.

On general pages, HomeRulebook may suggest an approximate city and state from the visitor's network location. The user must confirm or change that suggestion before it becomes a device preference.

The hint may reorder local starting points and prefill city and state fields. It never redirects the visitor, rewrites the indexed page, proves residence or substitutes for the property-address jurisdiction match.

03 · Source hierarchy

Official material comes first.

• Issuing department pages and project checklists
• Municipal or county code and adopted amendments
• Official forms, fee schedules and inspection documents
• Documented clarification from the issuing authority

04 · Rule structure

Conditions stay separate from conclusions.

A production rule should record the jurisdiction, project type, scope conditions, likely permits and approvals, inspection path, evidence and review state. When evidence is incomplete, the product tells the homeowner to confirm with the permitting office instead of inventing certainty.

05 · Evidence labels

A routing entry never masquerades as a decision.

Direct official rule means the project conclusion is tied to city- or county-specific evidence. Official route mapped means the authority and relevant official workflow are reviewed, but the exact property and scope still require confirmation. Routing entries are consolidated in city hubs; they are not published as standalone search pages.

06 · Freshness

Every authority record has a review date and a source-health check.

Official links are checked with browser-compatible and identified-monitor requests. Confirmed 404/410 responses and unclassified network failures open editorial review; they never automatically rewrite a conclusion.

A 403, 405 or verified network restriction is reported separately as restricted—not healthy and not proven broken. That exception is time-limited and requires a normal-browser recheck. A stale, moved or unavailable source lowers confidence and can remove a guide from the search sitemap until the rule is verified again.

07 · Search safeguards

Coverage grows only when evidence grows.

HomeRulebook does not publish city-by-project pages merely to capture keyword variants. An indexable local guide needs a direct official source, a distinct homeowner decision, visible scope limits, a next action and a review date.

When only the official authority route is verified, the project remains a useful anchored entry inside the city hub and Permit Navigator. A former research URL redirects to that consolidated entry instead of persisting as a thin noindex page.

Universal answer pages are indexed selectively. The nationwide coverage atlas does not create a state URL until an authority map, multiple local sources, an address-to-authority route and useful resident actions are ready.

08 · Corrections

Corrections should be traceable and fast.

Reports should identify the page, jurisdiction, project scope and supporting official material. Material changes refresh the source review date and should be recorded in the rule history.