State DNRs publish emergency rules via news releases when species hit population thresholds or when invasive concerns trigger closures. Add an emergency_alert field to the row that mirrors the press release headline and date. A selector mapping promotes that field into a red banner on the page, refreshed on every cache cycle. The canonical rule still renders below the banner.

Combined is simpler and the URL pattern handles it. One page group with /fishing-regs/{slug}/ as the pattern reads the merged feed and ranks across every state-species pair. Per-state archives at /fishing-regs/state/{state}/ are a parallel page group that lists the state's species without rewriting the rules per page.

Yes. Each row carries a prior_year_diffs field listing the changed columns and their previous values. A list mapping renders a diff table below the current rules so visitors who fished last year see exactly what changed without flipping between archived URLs.

Some species have one rule statewide; others have water-body-specific rules. A water_bodies array per row covers the second case. A list mapping renders the inline table, and if the variations are extensive enough, a separate /fishing-regs/{state}/{species}/{water-body}/ page group runs against a sub-feed.

Yes. Each row carries a license_purchase_url field. A templated href injects the link in the CTA slot of the base page, keyed to the state. Visitors land on the right state DNR purchase page without typing 'minnesota fishing license' into Google a second time.

Yes. The same model handles freshwater and saltwater species; the state DNR or state fisheries agency publishes both, just on different schedules. Add a habitat column to differentiate, and let the URL pattern carry the species slug regardless of habitat. Florida snook and Minnesota walleye sit in the same page group.

Treat the upstream source as authoritative. The page renders an editorial summary above the canonical text, with a link to the official rule in the footer. The page never silently reinterprets the rule; the table reflects exactly what the DNR feed says, and any commentary is clearly labelled. Anglers verify with the DNR; the page makes the verification fast.

Yes. Some species have different rules for fly tackle versus spinning gear, or for ice fishing versus open water. A gear_variants array renders inline below the canonical rule. The slug stays state-species; the gear nuance lives in the data layer rather than the URL.