GovTech Compliance

The Jurisdiction Rule Map is the foundational catalog for any govtech compliance agent.

This spec translates jurisdiction rules cataloged in t7-jurisdiction-rule-map into a deterministic process model: the ordered steps, required documents, review and approval gates, and exception paths that a compliance agent must execute for a given permit or regulatory determination.

Contract: Produces C9 → Provenance

Builds on: t7-jurisdiction-rule-map, e4-workflow-artifacts

The Accountability Layer Policy governs how a govtech compliance agent produces auditable decisions, how those decisions are explained to affected parties, what correction and appeal paths exist, and where human authority is irreducibly required.

Builds on: t7-compliance-workflow, s3-decision-traceability, s2-audit-trail-schema

Deploying a compliance agent across more than one jurisdiction without a principled architecture produces one of two failure modes: a brittle single-tenant build that cannot be adapted without rewriting core logic, or a sprawling one-off-per-jurisdiction implementation where every new municipality is a fresh project.

Builds on: t7-jurisdiction-rule-map, t7-compliance-workflow

[ATTORNEY REVIEW] — This entire playbook is legally operative.

Builds on: t7-compliance-workflow, s1-hitl-review-policy

The Rule Change Tracker is the version-control register for jurisdiction rules used by the compliance workflow.

Builds on: t7-jurisdiction-rule-map, s3-governance-retention-policy

The GovTech Compliance Package is the practitioner's starting kit for deploying a jurisdiction-aware, auditable compliance agent in a public-sector context.

Builds on: t7-accountability-layer, t7-compliance-workflow, t7-jurisdiction-rule-map, t7-multi-municipality-architecture, t7-risk-expert-review-plan, t7-rule-change-tracker