The Firehose
From CivicTide
Sample edition · live database not yet wired · receipts are demo

About

A weekly civic dispatch on Seattle City Council.

We track legislation from introduction to committee to final vote, explain it in plain-English, and give you three one-click ways to act. Receipts, not vibes.

Published by CivicTide, a project of SeaFor, a Washington 501(c)(4) social welfare organization. Free to read. Anonymous to read. Email is the only thing we ask for, and only if you want the dispatch delivered.

§ 01 · Mission

Why we exist.

Seattle is governed by an active City Council that introduces, amends, and votes on legislation every week. Most of that work happens in committee, before anything reaches a televised vote. Most of it does not get covered.

The news covers the final vote. The action goes down in committee, where three votes can hijack a bill's policy intent. Poison-pill amendments, self-canceling carve-outs, off-script comments that reveal a member's hidden agenda. We cover the juicy bits before they get cooked.

The Firehose covers it. Every Friday at 6am Pacific, we publish a short dispatch of what came out of committee last week, who sponsored, and where the fiscal note shifted. We link directly to bill and amendment text, sponsor offices, committee video, and Council vote tallies. We try to use plain English and keep the editorial voice out of the receipts.

The premise is simple. If a reader spends 30 seconds with a dispatch, they should walk away knowing more about what their City Council just did than if they spent 30 minutes on social media.

Editorial illustration: an open reporter's notebook with a fountain pen, brass compass, fanned legislative documents with red and blue tabs, and a cut-paper silhouette of Seattle City Hall and Smith Tower
Committee to council. Receipts, not vibes.

§ 02 · What we cover

Five beats. Council and Council-adjacent.

The Firehose stays narrow on purpose. The five beats below cover the policy areas where Seattle City Council action has the largest direct effect on residents and where ordinary readers are most often out-paced by the legislative calendar. If a bill, hearing, or vote does not touch one of these beats, we generally do not cover it in v1.

  1. i.

    Public safety

    SPD staffing, alternative response, surveillance authorizations, prosecutorial coordination.

  2. ii.

    Homelessness

    KCRHA contracts, shelter capacity, encampment policy, behavioral health beds.

  3. iii.

    Housing

    MHA, zoning, comprehensive plan updates, tenant relocation, permitting reform.

  4. iv.

    Taxes & business climate

    JumpStart, B&O, capital gains downstream effects, vacancy taxes, fiscal notes.

  5. v.

    Addiction response

    Public-use ordinances, treatment funding, fentanyl response, harm reduction policy.

Editorial illustration: an overhead view of a desk with three checklists, a magnifying glass, a coffee mug, a red rubber stamp, and a fanned stack of file folders
One reviewable artifact per stage. No auto-publish.

§ 03 · How we publish

Methodology, in six lines.

Committee first.

We track bills from introduction through committee, where most of the substantive work happens, not just at the televised final vote.

Receipts first.

Every claim links to a primary source: bill text, fiscal note, sponsor office, Council vote tally, or committee video timestamp.

Plain English.

Legislative jargon gets a one-line translation. If we use an acronym, we define it. If we cite a code section, we summarize it.

Human in the loop.

We use automation to watch and detect. We do not auto-publish. Every dispatch is reviewed and signed by a named editor before it goes out.

One source of truth.

Every dispatch is built from the Office of the City Clerk record of bills, amendments, and votes and publicly available reporting. The archive matches what readers received.

Corrections in public.

If we get something wrong, the correction lives in the dispatch and the archive, with a dated note. We do not silently edit history.

§ 04 · The firewall

Why this is a 501(c)(4), not a campaign.

The Firehose is published by CivicTide, a project of SeaFor, a Washington 501(c)(4) social welfare organization. That tax status is not branding. It defines what the Firehose is allowed to do and what it is not.

What the Firehose does: nonpartisan accountability journalism focused on the legislative process of Seattle City Council. Coverage of policy, votes, fiscal impact, and committee dynamics. Receipts and source links so readers can verify the work themselves.

What the Firehose does not do: endorse candidates, oppose candidates, coordinate with any campaign, political party, or political committee, or spend on independent expenditures. Even when a Council member is also a candidate in an active race, the Firehose covers their votes and their bills, not their campaign.

CivicTide may, in the future, support a separately incorporated and separately funded political committee for distinct activities. If that happens, it will operate on different infrastructure, with different staff, different funding sources, and at a different domain. The Firehose's reader list, analytics, and editorial workflow will not be shared with any such committee. This is infrastructure, not policy.

  • No endorsements. The Firehose does not endorse, oppose, or rate candidates in any active race.
  • No coordination. Editorial decisions are not shared with any campaign, party, or political committee.
  • No shared lists. Reader email addresses are never transferred, sold, or shared with any political committee.
  • No shared infrastructure. Any future political committee operates on separate accounts, separate domains, separate analytics, separate everything.
  • Electioneering review. Coverage adjacent to an active race is held for legal review before publication.
Editorial illustration: a tall brick wall down the center separating a journalist's desk on one side from an empty campaign rally room with a podium and folding chairs on the other
Editorial workflow on one side. Anything campaign-shaped on the other.

§ 05 · Privacy

What we collect. What we don't.

The reader side of the Firehose is anonymous by default. No accounts. No comments. No profiles. No saved items. No paywalls. No login. If you are reading this page, we do not know who you are.

The only piece of personal information we ever store is an email address, and only if you choose to subscribe to the dispatch. We do not run any third-party trackers on the reader site: no Google Analytics, no Meta pixel, no session replay, no ad tags. Operational metrics come from first-party server logs.

Email only.

The single piece of reader PII we collect. Used to deliver the weekly dispatch. Nothing else.

Encrypted at rest.

Subscriber emails are encrypted at rest in our database, with access limited to the editorial system.

Hard delete on unsubscribe.

One-click unsubscribe in every dispatch. Hard-deleted 30 days after unsubscribe, not soft-flagged.

No third-party trackers.

Zero analytics scripts, pixels, or ad tags on the reader site. First-party server-side metrics only.

For the full text, see the privacy policy and the 501(c)(4) disclosure.

§ 06 · Team

Who runs it.

The Firehose is run by a small editorial team. Every dispatch carries a named editor's byline. We expand this section as the masthead grows.

Founder & Publisher

TK

Sets editorial direction. Approves every dispatch as a whole before it is delivered.

Editor

TK

Owns the byline on each dispatch. Final review of receipts, fiscal notes, and vote tallies.

Contributors

TK

Beat reporting and source verification across public safety, housing, homelessness, taxes, and addiction response.

Editorial inquiries, tips, and corrections: press@civictide.org. We answer.

§ 07 · Parent organization

CivicTide.

The Firehose is the flagship public product of CivicTide, the public brand of SeaFor, a Washington 501(c)(4) social welfare organization. CivicTide focuses on accountability journalism and civic infrastructure for the Seattle region.

CivicTide

Donor inquiries, partnership questions, and anything outside the editorial scope of the Firehose are handled at the CivicTide organization site.

civictide.org