What happens when a jurisdiction isn't claimed

Citizens submit reports against jurisdictions that haven't been claimed by any org all the time. The funnel pattern keeps those reports useful — to the citizens, to the public, and to the eventual claimer.

Reports against an unclaimed jurisdiction:
- Land in `civicReports` exactly the same way as claimed-jurisdiction reports. Status starts at `reported`.
- Are publicly visible at `/report/<id>` and counted in the jurisdiction's stats at `/jurisdiction/<slug>`.
- Stay in `reported` status indefinitely — no triage, no assignment, no resolution. Nobody's been authorized to act on them.
- Are still searchable, upvotable, and discussable.

What the platform does about it:

1. **Weekly digest email** runs every Monday at 9:00 ET (`civicWeeklyDigestUnclaimed` scheduler). For each unclaimed jurisdiction with `openCount > 0` AND a discoverable `publicContactEmail` on file:
- Builds a digest of the 10 most recent open reports.
- Queues an email via the platform's `mail/` collection (Resend pickup).
- Logs a `civicJurisdictionDigests/{slug}_{weekStart}` record so we never send the same week twice.
2. **The digest framing** is direct: "Turtini is tracking <N> unresolved citizen reports in <name> this week:" → bulleted list → "Claim your jurisdiction at turtini.com/jurisdiction/<slug> to triage, assign crews, and respond directly to residents." This is the top-of-funnel sales mechanism — the city gets concrete evidence of demand + a one-click path to claim.
3. **The public scoreboard** at `/jurisdiction/<slug>` shows an amber "This jurisdiction has not yet claimed its scoreboard" banner with the claim CTA. Anyone visiting (including citizens, journalists, council candidates, watchdog groups) sees the unclaimed status — that's intentional pressure.

The `publicContactEmail` field is populated for jurisdictions in the seed manifest where it's discoverable (most US cities, state-level entities) — for the rest, it's blank and the digest skips them. Wally tool `civicReports_jurisdictionStats` returns the field so an admin can backfill via a follow-up tool call.

If you're an authorized representative who wants to claim:
- The claim flow uses DNS-TXT proof on the jurisdiction's domain, the same primitive as Verified-by-Turtini. Walk through it at `/civicreports` → **Claim** tab. Once you claim, ALL the existing reports in the queue land in your workspace immediately — you start with a real backlog, not a blank slate.

If you're a citizen who wishes someone would claim:
- Upvote reports you care about. Upvote counts surface in the eventual claim's first triage view.
- Email your council member with the link to your jurisdiction's scoreboard. The public stats make the case for staffing the function.