---
id: t7-jurisdiction-rule-map
title: Jurisdiction Rule Map
module: GROW-S6
module_slug: grow-s6-govtech-compliance
cluster: Trust
type: map
version: v0.1.0
status: Gate-reviewed
tier: membership
contract_role: ""
canonical_url: "https://grow.goodcombinator.ai/library/registry/t7-jurisdiction-rule-map"
download_url: "https://grow.goodcombinator.ai/library/registry/t7-jurisdiction-rule-map.md"
license: CC-BY-4.0 (proposed — owner confirmation required)
source: GROW by Good Combinator
retrieved_at: 2026-05-29
---

# Jurisdiction Rule Map

The Jurisdiction Rule Map is the foundational catalog for any govtech compliance agent. It identifies every governing agency whose rules apply to the agent's operating domain, maps each rule to the specific ordinance, statute, form, deadline, or approval flow it creates, and marks each rule as universal (applies across all deployments) or local (specific to one jurisdiction). Every downstream artifact in the t7 cluster reads from this map; no compliance determination is valid unless its `rule_id` resolves to a row here. Rows carry mandatory `[VERIFY]` flags where currency is uncertain and `[ATTORNEY REVIEW]` flags where the provision is legally operative.

## 1. Map Schema

Each row in the jurisdiction rule map uses this structure. Maintain it as a version-controlled register; add rows by appending and tag a map version whenever a new rule enters the active set.

```yaml
- rule_id: <kebab-case, globally unique>
  jurisdiction_id: <kebab-case, e.g. fl-walton-county | fl-state | us-federal>
  rule_class: <statute | ordinance | rule | policy | form | deadline | approval-flow>
  citation: <exact text — chapter, section, or docket reference>
  scope: <universal | local>
  summary: <one-sentence plain-language description of the requirement>
  agency: <governing body that issues and enforces this rule>
  agent_trigger: <the input condition that activates this rule for the compliance workflow>
  forms_required: [<form ids or "none">]
  deadline_days: <integer, calendar days from trigger event, or "none">
  approval_flow: <ordered sequence of approvals, or "none">
  verify_flag: <true | false>    # true → append [VERIFY] in display
  attorney_review: <true | false> # true → append [ATTORNEY REVIEW] in display
  last_confirmed: <YYYY-MM-DD or "unknown">
  notes: <any ambiguity, conflict, or pending legislative change>
```

## 2. Universal Rules (apply across all Florida special-district and stormwater deployments)

These rules are universal because they arise from state or federal authority and bind any agent operating in Florida regardless of the specific municipality or special district.

| rule_id | jurisdiction_id | citation | scope | summary | agency | verify | atty |
|---|---|---|---|---|---|---|---|
| `fl-pub-records-access` | `fl-state` | FS Chapter 119 [VERIFY] | universal | Public records produced or received by a public body are open to inspection and must be produced on request within a reasonable time unless a statutory exemption applies. | FL Department of State | yes | yes |
| `fl-pub-records-retention` | `fl-state` | FS Chapter 119 + FL Dept of State retention schedules [VERIFY] | universal | Records must be retained for the period specified in the applicable state retention schedule; local variation requires formal exemption. | FL Division of Library and Information Services | yes | yes |
| `fl-sunshine-law` | `fl-state` | FS Chapter 286 [VERIFY] | universal | Meetings of public boards and commissions where official acts are taken or public business discussed must be held in public. AI-generated staff summaries distributed before a meeting may be subject to this chapter. | FL Attorney General | yes | yes |
| `fdep-stormwater-general` | `fl-state` | FAC Chapter 62-330 [VERIFY] | universal | Environmental Resource Permits (ERPs) are required for any activity that alters stormwater systems above the de minimis threshold. | FL Department of Environmental Protection (FDEP) | yes | yes |
| `fl-ada-digital` | `us-federal` | ADA Title II [VERIFY] | universal | Digital communications and outputs of public agencies must meet WCAG 2.1 AA accessibility standards under DOJ guidance effective 2026. | US Department of Justice | yes | yes |
| `fl-grant-lpa0381` | `fl-state` | DEP Grant LPA0381 [VERIFY] | universal | Stormwater infrastructure grant work must comply with grant conditions including reporting, procurement, and records-access requirements specific to the grant award. | FDEP Office of Water Policy | yes | yes |

## 3. Local Rules — South Walton County / Walton County Special Districts

These rules are local to the South Walton County corridor and the South Walton Community Council (SWCC) / special-district governance context. An agent deployed outside this jurisdiction must substitute the applicable local table.

| rule_id | jurisdiction_id | citation | scope | summary | agency | verify | atty |
|---|---|---|---|---|---|---|---|
| `walton-co-ldco` | `fl-walton-county` | Walton County Land Development Code (LDC), Chapter 5 [VERIFY] | local | Development activities above thresholds defined in Ch. 5 require a local development order with stormwater management plan before construction. | Walton County Planning & Development | yes | yes |
| `walton-co-stormwater-ord` | `fl-walton-county` | Walton County Stormwater Ordinance [VERIFY] | local | Post-construction stormwater systems serving new development must be inspected annually and maintained to design standards. Special districts may be delegated enforcement authority. | Walton County Department of Environmental Services | yes | yes |
| `swcmcd-permit-intake` | `fl-walton-county` | SWCMCD Operating Resolution, current version [VERIFY] | local | South Walton County Municipal Complex District intake process requires submission of permit applications via the district portal with supporting parcel data and site plan. | SWCMCD Board of Supervisors | yes | yes |
| `walton-hoa-720` | `fl-walton-county` | FS § 720.3085 [VERIFY] | local | Homeowner association assessment collection procedures are governed by FS § 720.3085; non-compliance with these procedures is a defect that can invalidate a lien. | FL Office of the Condominium Ombudsman (enforcement) | yes | yes |
| `swcmcd-public-meeting` | `fl-walton-county` | FS § 189.016, special district notice requirements [VERIFY] | local | Special district board meetings must be noticed per FS § 189.016; AI-assisted agenda preparation must not substitute for a compliant notice procedure. | FL Department of Economic Opportunity | yes | yes |

## 4. Approval Flow Reference

This section maps `rule_id` values to their ordered approval flows for use by `t7-compliance-workflow`. Each step is a named role/agency gate; all must pass before the determination is `compliant`.

```yaml
- rule_id: walton-co-ldco
  approval_flow:
    - step: 1
      gate: Applicant submits site plan and stormwater calculations to Walton County Planning & Development portal
    - step: 2
      gate: County Environmental Services reviews stormwater management plan against FAC Chapter 62-330 [VERIFY]
    - step: 3
      gate: County Engineer reviews drainage calculations
    - step: 4
      gate: FDEP ERP determination (if activity exceeds state threshold) — routed to expert_review [ATTORNEY REVIEW]
    - step: 5
      gate: Local development order issued by County Zoning Board
  deadline_days: 90
  notes: Clock starts at complete-application acceptance, not submission date.

- rule_id: swcmcd-permit-intake
  approval_flow:
    - step: 1
      gate: District clerk reviews application for completeness
    - step: 2
      gate: District engineer screens for stormwater impact classification
    - step: 3
      gate: Board agenda placement if engineer flags impact > threshold
    - step: 4
      gate: Board vote (if required)
  deadline_days: 30
  notes: Threshold values set by board resolution; verify current resolution version before classifying. [VERIFY]
```

## 5. Worked Example — Stormwater Pre-Screener, South Walton County

**Scenario.** An applicant submits a permit application to the SWCMCD district portal for a 1.2-acre lot clearing on 30A with an associated impervious-surface increase of 0.4 acres. The `stormwater-permit-triage` agent must identify which rules apply.

**Rule activation trace:**

| Input signal | rule_id activated | Why |
|---|---|---|
| FL parcel within Walton County | `walton-co-ldco` | Land development code applies to all Walton County parcels |
| Impervious increase > 0.1 acres | `fdep-stormwater-general` | FAC 62-330 threshold for ERP may be triggered [VERIFY] |
| Submitted to SWCMCD portal | `swcmcd-permit-intake` | District intake procedure applies |
| Output will be a public record | `fl-pub-records-access` | District records are public records under FS Chapter 119 |
| Grant-funded project | `fl-grant-lpa0381` | If funded under LPA0381, grant conditions apply |

**Expert-review trigger.** Because `fdep-stormwater-general` is activated and ERP threshold determination requires engineering and legal interpretation, `expert_review_required` is set to `true` for that rule row, raising an S1 HITL event per `t7-compliance-workflow` before any applicant-facing output is produced. The determination for that rule is logged as `needs-review` until the expert resolves it. `[ATTORNEY REVIEW]`

## 6. Map Maintenance Rules

Rule maps are living artifacts and must not be treated as static documentation.

1. A new `rule_id` must be appended before any compliance determination references it; back-dating is prohibited.
2. `verify_flag: true` rows must be re-confirmed against the primary source at least annually. The confirmation date updates `last_confirmed`; failure to confirm within 14 months triggers automatic downgrade to `confidence_band: low` on any determination citing that rule.
3. Any change to `citation`, `approval_flow`, or `deadline_days` is logged in `t7-rule-change-tracker` as a versioned event.
4. Legislative changes detected by the rule-change tracker create a blocking update task: no new determinations on the affected `rule_id` until the row is updated and a qualified reviewer confirms the new text. `[ATTORNEY REVIEW]`
5. `scope: local` rows are jurisdiction-specific; they must be replaced, not extended, when deploying the compliance workflow to a new jurisdiction. See `t7-multi-municipality-architecture` for the substitution protocol.
