What Civic Reports is — citizen-side regional issue reporting

Civic Reports is the citizen-side counterpart to Civic. Anyone, anywhere in the world, can submit a geotagged report — pothole, streetlight out, sidewalk damage, water leak, debris, graffiti, hazardous tree, signage, parking violation, etc. Turtini reverse-geocodes the location and routes the report to the responsible city / county / district.

Two surfaces, one module key (`civicReports`):

• **Citizens** — `/report` is public and works without an account. Snap a photo, drop a pin, pick a category, submit. Signed-in users get `/me/reports` as a personal dossier tracking resolution. Anonymous submissions are throttled per IP fingerprint to prevent abuse.
• **Verified entities** — `/civicreports` is the org workspace: Kanban triage board, SLA timers per category, crew assignment, public scoreboard, and outbound integrations to Salesforce, ServiceNow, Cityworks, Accela, generic webhooks, plus a read REST API for your own apps.

How the funnel works:
- Reports for an **unclaimed** jurisdiction stack up publicly at `/jurisdiction/:slug`. A weekly digest email goes to a discoverable public address ("47 unresolved reports in Norfolk this week. Claim your jurisdiction to triage.").
- A verified org claims a jurisdiction by adding a DNS TXT record (same primitive as Verified-by-Turtini and the venue catalog). Once verified, the org owns the workflow.
- Every resolved report mints a Verified-by-Turtini credential proving the city closed the loop. The public scoreboard shows median time-to-close, by-category counts, and recent activity — a built-in trust signal.

This is the citizen-side counterpart to Civic OS. A town body can run both: Civic OS for the council itself, Civic Reports for the constituent issue stream.