FireApproved

Missouri

Missouri

Program and model No adopted WUI code we can source here. IBHS Wildfire Prepared asks for the inspection measures, and the 2024 IWUIC model says the same floor.

No statewide construction book — sourced Last verified 2026-08-26

One local briefing, built from separate evidence layers: what the state has published, where an instrument is documented to apply, what still depends on a map or project fact, and which plant records are documented in Missouri. A ZIP personalizes priority; it does not decide a parcel boundary.

What is established here

Missouri does not adopt a statewide WUI construction book. RSMo 67.280 lets a community incorporate construction codes by reference. IWUIC is not a statewide book. Confirm with the building official.

No exact code-application record is normalized for this state. A source node alone does not activate requirements.

Open the Build rules for Missouri →

What is not established

A ZIP in Missouri is a postal match, not a parcel, map, or permit. No city or county briefing is open here yet.

What differs here

Object records that name Missouri (not reprinted here):

Child-place and sibling claims stay on those place pages, their object URLs, and the JSON twin.

Plants documented in Missouri

State distribution, native range, invasive status, hardiness, and fire evidence answer different questions. None is a planting approval. The list itself is on Grow — this page carries the aggregates.

Fire-resistant 305 Keep away 41 Documented conflict 11 Awaiting evidence 136

493 plant records documented in the state. 0 explicitly document Missouri as native range. 120 carry an invasive or noxious flag applying here. 0 fire-evidence sources name Missouri in publication scope.

Plant groups in Missouri →

Human page and machine twin

This briefing is the place answer. The claim graph lives on object pages and the JSON twin. Methodology · Missouri JSON · place node JSON