Oklahoma

Oklahoma

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

What is established here

Oklahoma does not adopt a statewide WUI construction book. OUBCC’s adopted-code families are IRC, IBC, IEBC, IFC, IFGC, IMC, IPC, and NEC. The commission has adopted 2024 IBC, IEBC, IFC, IFGC, IMC, IPC, and IRC, effective 14 September 2026; 2018 editions remain in effect until then. IWUIC is not on that list. 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 Oklahoma →

What is not established

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

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

Plants documented in Oklahoma

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.

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

Plant groups in Oklahoma →

Human page and machine twin

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