--- id: t7-rule-change-tracker title: Rule Change Tracker module: GROW-S6 module_slug: grow-s6-govtech-compliance cluster: Trust type: register version: v0.1.0 status: Gate-reviewed tier: membership contract_role: "" canonical_url: "https://grow.goodcombinator.ai/library/registry/t7-rule-change-tracker" download_url: "https://grow.goodcombinator.ai/library/registry/t7-rule-change-tracker.md" license: CC-BY-4.0 (proposed — owner confirmation required) source: GROW by Good Combinator retrieved_at: 2026-05-29 --- # Rule Change Tracker The Rule Change Tracker is the version-control register for jurisdiction rules used by the compliance workflow. Its job is narrow and critical: detect when a governing rule, statute, ordinance, or form has changed; version the compliance logic that depends on it; flag active determinations that relied on the stale version; and block new determinations from using an un-reviewed rule until the update is confirmed. Any agent operating in a public-sector context faces a steady stream of rule changes — legislative sessions, agency rulemaking, ordinance amendments, form revisions — and the agent's safety guarantee degrades the moment the rule catalog diverges from the live regulatory environment. The tracker closes that loop. It reuses retention rules from `s3-governance-retention-policy` (`civic-7yr` for all public-sector compliance records). ## 1. Register Schema ```yaml - change_id: rule_id: jurisdiction_id: change_type: prior_citation: new_citation: effective_date: detected_date: detection_source: severity: # reuses glossary severity enum status: blocking: # true means no new determinations on this rule_id until status = incorporated affected_determinations: [] reviewer_role: confirmed_by_role: confirmed_date: compliance_logic_version_before: compliance_logic_version_after: retention_class: civic-7yr # locked per s3-governance-retention-policy notes: ``` ## 2. Severity Classification The `severity` field uses the GROW glossary enum and governs urgency of response. | Severity | Meaning in rule-change context | Default response SLA | |---|---|---| | `critical` | Change invalidates a prior `compliant` determination or creates a hard new legal obligation effective immediately. Safety/legal/irreversible-impact class. | Block new determinations on same day detected; expert review within 2 business days. `[ATTORNEY REVIEW]` | | `high` | Change alters thresholds, deadlines, or forms in a way that materially affects routing. Prior determinations may be wrong. | Block new determinations within 24 hours; review within 5 business days. | | `medium` | Change affects instructions, clarifications, or non-threshold procedural items. Prior determinations likely still valid. | Non-blocking flag; review within 30 days. | | `low` | Formatting, agency contact info, cross-reference numbering. No substantive change. | Non-blocking; incorporate in next scheduled review cycle. | | `info` | Monitoring signal; no rule impact confirmed yet. | Log and watch; no action required. | ## 3. Detection Sources and Reliability Not all detection sources are equally reliable. The tracker must record where a change was detected because that affects how quickly the `blocking` flag should be set and whether an attorney-review HITL gate must be raised immediately. | Source | Reliability | Blocking auto-trigger | |---|---|---| | Official agency gazette / Federal Register | High — authoritative | Yes, on confirmed text change | | Agency website (posted rule text) | Medium — may lag gazette; cross-check required | Yes, but with `[VERIFY]` flag | | Attorney memo or counsel advisory | High — qualified professional signal | Yes | | Practitioner notice (peer govtech network) | Medium — may be interpretive | Flag for review; no auto-block | | Automated text-scan (diff against prior snapshot) | Low — text change detected but significance unknown | Flag for review; human classifies severity | ## 4. Stale-Rule Escalation Rules The following automatic escalations apply regardless of whether an explicit change has been detected. These enforce the currency guarantee independently of the detection mechanism. 1. Any rule row with `last_confirmed` older than 12 months automatically triggers a `change_id` of type `info` with status `detected`. The rule is not blocked immediately but is flagged for quarterly review. 2. Any rule row with `last_confirmed` older than 18 months is automatically set to `blocking: true` pending re-confirmation. New determinations on that `rule_id` are blocked until a qualified reviewer confirms the rule is still current and updates `last_confirmed`. `[ATTORNEY REVIEW]` 3. A legislative session close (FL: typically June and March) triggers a batch review of all `fl-state` jurisdiction rules, regardless of individual `last_confirmed` dates. ## 5. Compliance Logic Versioning The tracker connects rule-text changes to compliance-logic versions. When a rule change is incorporated: 1. The `t7-compliance-workflow` artifact is bumped to a new semver. The bump is MINOR for threshold or procedure adjustments; MAJOR if the determination enum changes, a new phase is required, or the HITL trigger conditions change. 2. The tracker record `compliance_logic_version_after` is updated. 3. Any in-flight application that was evaluated against the prior version is flagged with a `stale-rule` event in `s3-provenance-metadata-schema` (reusing the `stale-data` failure mode from `s1-failure-mode-register`). 4. The prior version of `t7-compliance-workflow` is archived; determinations made against it remain valid under the version that was current at determination time, unless the change is retroactive. Retroactive changes require `[ATTORNEY REVIEW]`. ## 6. Register — Active Tracked Changes (South Walton County) This section contains known open tracking items as of the build date. All items carry `[VERIFY]` because their current status must be confirmed against primary sources before any determination relies on them. ```yaml - change_id: rc-2026-0001 rule_id: fdep-stormwater-general jurisdiction_id: fl-state change_type: threshold-change prior_citation: FAC Chapter 62-330 (pre-2024 thresholds) [VERIFY] new_citation: FAC Chapter 62-330 (2024 amendments pending codification) [VERIFY] effective_date: unknown detected_date: 2026-05-01 detection_source: practitioner-notice severity: high status: under-review blocking: true affected_determinations: [none-logged] reviewer_role: licensed-environmental-engineer confirmed_by_role: pending confirmed_date: pending compliance_logic_version_before: 0.1.0 compliance_logic_version_after: pending retention_class: civic-7yr notes: Practitioner reports threshold for de minimis ERP exemption may have changed; confirm against official FAC text before using in determinations. [VERIFY] [ATTORNEY REVIEW] - change_id: rc-2026-0002 rule_id: walton-co-ldco jurisdiction_id: fl-walton-county change_type: text-amendment prior_citation: Walton County LDC Chapter 5 (pre-2025 version) [VERIFY] new_citation: Walton County LDC Chapter 5 (2025 amendment, pending county website update) [VERIFY] effective_date: 2025-10-01 detected_date: 2026-04-15 detection_source: attorney-memo severity: medium status: under-review blocking: false affected_determinations: [none-logged] reviewer_role: county-planning-staff confirmed_by_role: pending confirmed_date: pending compliance_logic_version_before: 0.1.0 compliance_logic_version_after: pending retention_class: civic-7yr notes: Amendment reportedly clarifies impervious-surface calculation method; no threshold change. Confirm with county planning staff before next quarterly review. [VERIFY] - change_id: rc-2026-0003 rule_id: fl-pub-records-access jurisdiction_id: fl-state change_type: new-rule prior_citation: FS Chapter 119 (pre-AI-records guidance) [VERIFY] new_citation: FS Chapter 119 + FL Attorney General advisory on AI-generated public records (if issued) [VERIFY] effective_date: unknown detected_date: 2026-05-20 detection_source: practitioner-notice severity: high status: detected blocking: false affected_determinations: [none-logged] reviewer_role: district-counsel confirmed_by_role: pending confirmed_date: pending compliance_logic_version_before: 0.1.0 compliance_logic_version_after: pending retention_class: civic-7yr notes: Unconfirmed signal that FL AG may issue guidance on whether AI agent outputs constitute public records under FS Chapter 119. Monitor FL AG website and FL Association of Special Districts (FASD) alerts. [VERIFY] [ATTORNEY REVIEW] ``` ## 7. Review Cadence and Retention Per `s3-governance-retention-policy`, all change-tracker records carry `retention_class: civic-7yr`. Review cadence: - **Monthly.** Scan all `blocking: true` records for resolution; escalate any that have exceeded the severity-class SLA without expert confirmation. - **Quarterly.** Batch review of all `info`-severity stale-rule triggers; confirm or retire `detected` items older than 90 days. - **Annual.** Full map review against primary sources for all `fl-state` and `fl-walton-county` rules; reset `last_confirmed` for confirmed-current rows; route stale rows to `blocking` state. - **Triggered.** Florida legislative session close, FDEP rulemaking notice, or district counsel advisory triggers an immediate out-of-cycle review of affected rules. `[ATTORNEY REVIEW]` ## 8. Worked Example — Detecting a Threshold Change **Scenario.** A GROW-monitoring agent scans the FDEP rulemaking notices RSS feed and detects a change to FAC Chapter 62-330 impervious-surface thresholds. The scan fires at 2026-06-01 14:00 UTC. **Tracker response:** 1. A new `change_id` is created (`rc-2026-0004`) with `detection_source: automated-scan`, `severity: info` (initial; not yet classified), and `status: detected`. 2. Because the source is `automated-scan` (Low reliability), the system does not auto-set `blocking: true`. Instead, it raises an `info`-class escalation to the `licensed-environmental-engineer` role for classification. 3. The engineer reviews the rulemaking notice within 24 hours and classifies severity as `high` (threshold change). Status advances to `under-review`; `blocking` is set to `true`. 4. No new determinations using `fdep-stormwater-general` may be issued until the engineer confirms the new text and the compliance workflow is updated. 5. In-flight applications evaluated before the detection date receive a `stale-rule` flag in their provenance records. 6. Once confirmed, `compliance_logic_version_after` is updated to `0.2.0`, blocking is lifted, and the tracker record moves to `incorporated`. Retention clock starts at `incorporated` date under `civic-7yr`.