Arkansas

Arkansas

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 Arkansas. A ZIP personalizes priority; it does not decide a parcel boundary.

What is established here

Arkansas does not adopt a statewide WUI construction book. The Arkansas Fire Prevention Code is a three-volume set based on the International Fire, Building, and Residential Codes. The Department of Labor states that code applies statewide. IWUIC is not those volumes. 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 Arkansas →

What is not established

A ZIP in Arkansas 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 Arkansas (not reprinted here):

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

Plants documented in Arkansas

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.

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

Plant groups in Arkansas →

Human page and machine twin

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