# FORENSIC EVIDENCE BRIEF (v2 — RECONCILED)
## City of Redmond Public Records Act Violations — Request #32782
### Prepared for Filing: Citizen Action Complaint (RCW 42.17A.775) and/or Penalty Petition (RCW 42.56.550)

**Date Prepared:** April 6, 2026 (original); **Reconciled April 24, 2026**
**Subject:** Systematic suppression and manipulation of public records in response to PRA Request #32782 concerning the closure and demolition of the Old Fire House Teen Center, 16510 NE 79th Street, Redmond, WA 98052
**Requester:** Sasha Glenn
**Respondent:** City of Redmond, Washington
**Applicable Law:** Washington Public Records Act, RCW 42.56; RCW 42.23 (Code of Ethics for Municipal Officers); RCW 40.14 (Records Retention)

**Corpus under analysis:** Seven numbered installments plus supplemental material, consolidated to **4,846 unique Outlook .msg files** after deduplication. All analyses below are performed using the `extract_msg` 0.55.0 Outlook OLE2 parser library against preserved copies of every installment as received from the City.

**Reconciliation note:** This v2 brief supersedes the April 6, 2026 draft. The earlier draft contained three claims that have been withdrawn in full on re-analysis against the complete corpus using the correct parser library: (i) 96% file-level corruption (methodology artifact of wrong parser library — 0% corruption under correct parser; see Exhibit E below, which is retained in "Reserved" form for continuity); (ii) "not a single attachment produced" (attachments are embedded within the .msg OLE2 containers — 3,200 of 4,846 emails contain 26,508 attachment objects; see Exhibit C, reframed); and (iii) the five-month (September 2024 – January 2025) production gap, which narrows on the full corpus to near-total suppression of **December 2024 only**. The deficiency case is tighter, not weaker: every remaining claim is independently provable on cross and survives the addition of the full Installment 5/6/7 corpus that was not available at the time of the April 6 draft.

---

## TABLE OF CONTENTS

1. [Summary of Findings](#1-summary-of-findings)
2. [Production Overview](#2-production-overview)
3. [Exhibit A: Production Inflation by Duplication](#exhibit-a)
4. [Exhibit B: Records Mathematically Withheld — Four Named Officials With Zero Outgoing](#exhibit-b)
5. [Exhibit C: Absence of Exemption Log Prevents Case-by-Case Attachment Verification](#exhibit-c)
6. [Exhibit D: Near-Total Suppression of December 2024](#exhibit-d)
7. [Exhibit E: [Reserved — File-Level Integrity Claim Withdrawn]](#exhibit-e)
8. [Exhibit F: The March 30, 2025 Substantive Cutoff](#exhibit-f)
9. [Exhibit G: The Kenmore Black Hole](#exhibit-g)
10. [Exhibit H: Channel Switching and Narrative Control](#exhibit-h)
11. [Exhibit I: No Exemption Log; No Privilege Log; No Vaughn Index](#exhibit-i)
12. [Exhibit J: Drive-Level Byte-Identical Duplicate Zip](#exhibit-j)
13. [Exhibit K: Installment Size Anomaly — Inst_7_Apr_2024 at 6.65 MB per Email](#exhibit-k)
14. [Legal Standards Violated](#legal-standards-violated)
15. [Penalty Exposure](#penalty-calculation)
16. [Evidence Preservation](#evidence-preservation)
17. [Conclusion](#conclusion)

---

## 1. SUMMARY OF FINDINGS

The City of Redmond produced a deduplicated corpus of **4,846 unique Outlook .msg files** across seven numbered installments plus supplemental material in response to PRA Request #32782. Forensic analysis — reconciled April 24, 2026 against the full corpus using the correct Outlook OLE2 parser — demonstrates that this production is substantially non-responsive in the respects below. The mechanisms are interlocking and each is independently provable:

| # | Mechanism | Key Metric |
|---|-----------|-----------|
| A | **Production inflation by duplication** | ~23.8% of the corpus (approx. 1,155 records of 4,846) is excess duplicate copies by normalized body-hash; drive-level byte-identical duplicate zip also delivered (§ J) |
| B | **Records mathematically withheld — named officials with zero outgoing** | Four named City officials produced zero outgoing records across the 4,846-file corpus: Fields (~110 inbound / 0 out), Salahuddin (~101 / 0), Council mailbox (~136 / 0), C. Payne (~77 / 0); Mayor Birney's outgoing traffic is token-only (62 across Office-of-Mayor + personal account) with no substantive policy record |
| C | **Absence of exemption log prevents case-by-case attachment verification** | 3,200 of 4,846 emails contain 26,508 embedded attachment objects; a substantial fraction are cosmetic inline signature graphics; without a Vaughn-style index the City's response cannot be verified on a per-attachment basis (see reframed Exhibit C) |
| D | **December 2024 near-total suppression** | Only 2 unique substantive email records dated in December 2024 across the 4,846-file corpus, in a month of documented heavy multi-workstream OFH activity |
| E | **[Reserved — file-level integrity claim withdrawn]** | The April 6, 2026 draft's "96% corruption" finding was a methodology artifact of an RFC822 parser applied to Outlook native format; under the correct parser library, 0% of .msg files exhibit internal corruption. Finding withdrawn. |
| F | **March 30, 2025 substantive cutoff** | Only 6 emails in the full 4,846-file corpus post-date March 30, 2025, all automated or non-substantive; no substantive record covers the April 27 / May 10 / June 28 / July 22 / October / November 18, 2025 events of facial PRA-32782 significance |
| G | **Search-term suppression — the Kenmore absence** | Zero mentions of "Kenmore" in subject lines or body text across the full 4,846-file corpus; Plymouth Housing appears ~142 times |
| H | **Channel switching off-records** | ~45 records in which City officials direct substantive discussion to phone / in-person / off-record channels |
| I | **No exemption log / no privilege log / no Vaughn index** | Required under RCW 42.56.210(3); not provided for any of seven installments |
| J | **Drive-level byte-identical duplicate zip** | `Inst_7_Jan_2024.zip` delivered twice in the City's own production folder (79,783,936 bytes, MD5-identical), with "(1)" suffix — delivery-layer carelessness independent of email-internal duplication |
| K | **Installment-size anomaly** | `Inst_7_Apr_2024.zip` averages 6.65 MB per email (167 emails / ~1.11 GB) — a 20×–130× per-file inflation on a single installment without parallel inflation elsewhere |

These mechanisms are not independent failures. They form a coordinated suppression strategy: inflate the production at both the email and delivery layers, remove the substantive outgoing communications of the officials at the center of the decision, collapse the months and events in which the decision was actually made, and move sensitive conversations off-record. The case does not depend on any claim about file-level integrity.

---

## 2. PRODUCTION OVERVIEW

### Seven Installments Plus Supplemental Material

| Installment | Date Received | Unique .msg Files | Period Covered |
|-------------|--------------|------:|---------------|
| 1st | April 24, 2025 | ~1,184 | March 21–30, 2025 |
| 2nd | June 19, 2025 | ~1,555 | March 1–20, 2025 |
| 3rd | July 18, 2025 | 22 | Mixed non-email items |
| 4th | February 2026 | 292 | February 16–28, 2025 |
| 5A | — | 154 | February 1–15, 2025 |
| 5B | — | 212 | January 16–31, 2025 |
| 5C | — | 242 | January 1–15, 2025 |
| 6 (Jul–Nov 2024, monthly) | — | 412 | July–November 2024 |
| 7 (Jan–Jun 2024, monthly) | — | 589 | January–June 2024 |
| Additional supplemental | — | 184 | 2024–2025 mixed |
| **Total unique emails (deduplicated)** | | **4,846** | |

### After Deduplication — Padding Overview

Approximately **1,155 emails (23.8%)** of the 4,846-file corpus are excess duplicate copies by normalized body-hash. Eighty-one (81) unique email bodies appear in more than one installment, contributing the cross-installment portion of the duplication. Certain individual records appear with extreme redundancy: a single community-comment email appears 134 times across Installments 1 and 4 alone; the City's own press release "City of Redmond Transitions Teen Programs" appears with similar redundancy across installments.

**The earlier "79.7% padding" figure is withdrawn.** That figure was generated against a four-installment document-count universe of 7,573 items that (i) included non-email items that are not part of the email corpus, and (ii) counted as "padding" automated notifications and Google Alerts that, while inflationary, are independent records rather than duplicate copies. The correctly-scoped claim against the email-only deduplicated corpus is ~23.8% excess duplicate copies. This does not include the drive-level byte-identical duplicate zip separately identified at § J below.

---

## EXHIBIT A: PRODUCTION INFLATION BY DUPLICATION {#exhibit-a}

### Method

The deduplicated 4,846-file corpus contains approximately **1,155 excess duplicate copies** by normalized body-hash — an excess-duplication rate of approximately **23.8%**. Duplication operates through two mechanisms: (i) exact duplication (the same email copied multiple times within and across installments), identified by normalized body-hash match; and (ii) cross-installment duplication (81 unique email bodies appearing in more than one installment), identified by header-field and content match across installment boundaries.

### Extreme Redundancy on Individual Records

| Email | Copies | Installments |
|-------|:------:|:------------:|
| Angie Nuevacamina (single community-comment email) | **134** | Installments 1 & 4 |
| News Release: City of Redmond Transitions Teen Programs | multiple dozens | Multiple |
| Change.org petition notification | multiple dozens | Multiple |
| Vanessa Kritzer council reply | 51 | Multiple |
| Erica Chua (no subject) | 48 | Multiple |
| Vanessa Kritzer "Redmond Teen Center" | 39 | Multiple |
| "Facilities Meeting" (Birney calendar invite) | 28 | Multiple |

One email from a single community member appears 134 times. The City's own press release appears with similar redundancy across installments.

### Subject-Line Stripping

Approximately **955 emails in the corpus have no subject line** — the single largest "subject" category. Top contributors are City officials: Angie Nuevacamina (92), Erica Chua (62), Loreen Hamilton (30), Brittany Pratt (26). Subject-line stripping impedes conversation threading and timeline reconstruction.

### Legal Significance

Inflation of a production with redundant copies while substantive responsive records remain undisclosed is a documented PRA obstruction pattern and is inconsistent with the "fullest assistance" duty under RCW 42.56.070. The pattern is a basis for penalty enhancement under RCW 42.56.550. Duplicate inflation is independent of — and additive to — the drive-level byte-identical duplicate-zip delivery documented at Exhibit J and the installment-size anomaly documented at Exhibit K.

---

## EXHIBIT B: RECORDS MATHEMATICALLY WITHHELD — FOUR NAMED OFFICIALS WITH ZERO OUTGOING {#exhibit-b}

### Methodology

Email operates under a protocol rule: if Person A sends a reply ("Re: Subject") addressed to Person B, then Person B sent the original message that Person A is replying to. If Person A's reply is in the production and Person B's original is absent, Person B's email was withheld. This is not statistical inference. It is a mathematical certainty derived from the structure of RFC 5322 email headers.

This exhibit limits itself to the four named entities for which that demonstration is cleanest on the full 4,846-file corpus. The case does not depend on broader "ghost population" counts.

### The Four Named Zero-Outgoing Officials

| Entity | Email | Inbound Records | Outgoing Records Produced |
|---|---|---:|---:|
| Council Member **Steve Fields** | sfields@redmond.gov | ~110 | **0** |
| City Administrator **Osman Salahuddin** | osalahuddin@redmond.gov | ~101 | **0** |
| **City Council mailbox** | council@redmond.gov | ~136 | **0** |
| **C. Payne** | cpayne@redmond.gov | ~77 | **0** |

Each of the four named officials was a direct recipient of communications requiring response on the subject matter of PRA 32782. Replies produced in the corpus from other custodians explicitly refer to outgoing messages from each. Those outgoing messages must exist under RFC 5322 and are not in the production.

### The Political Opponent

**Steve Fields** is a sitting City Council member who ran against Mayor Birney for mayor in 2019 and later made a motion to restore teen services. His zero-outgoing status against ~110 inbound records across the full corpus is inconsistent with any good-faith production.

### The City Administrator

**Osman Salahuddin** oversaw the OFH decision from the City Administrator's office. His zero-outgoing status against ~101 inbound records, in a corpus that includes the decision-making period, places the City Administrator's entire outgoing record on the subject matter of PRA 32782 in "withheld" status.

### Mayor Birney — Token Outgoing, No Substantive Communication

Mayor Angela Birney's own outgoing records in the 4,846-file corpus total **27** from her personal account; the Office-of-the-Mayor mailbox produced **35** outgoing records. Not one of those 62 combined outgoing records is a substantive policy directive, decision email, or material communication on the subject matter of PRA 32782. Her produced outgoing traffic consists of calendar invites, newsletter test drafts, press-release quote approvals, and media-question forwarding to other custodians for handling. The Mayor is referenced many hundreds of times across the corpus by other custodians as the decision-maker on OFH. Her substantive outgoing record is absent.

### Stepherson & Associates — Minimal Outgoing Across a 14-Month Engagement

The City retained Stepherson & Associates (PR firm) at $4,468.75 per month beginning on or about November 14, 2024. The contractor's outgoing records in the corpus are minimal across a 14-month engagement spanning the announcement, closure, and demolition-vote periods. Specific volumes and custodian identifiers are held for development on cross-examination; the generalized absence is noted here as an additional basis for Vaughn-index demand.

### Withholdings Mathematically Compelled, Not Estimated

This brief does not assert a specific total number of "proved-withheld emails." Such a total depends on how "reply-to proof" is counted (per-thread, per-message, per-distinct-correspondent) and on assumptions about de-duplication across threads. The mathematical certainty is that each of the four named officials has at least one withheld outgoing communication for every reply-to them in the production; the corpus contains many such replies for each of the four. The exact count belongs in discovery; the fact of withholding is established on the face of the production.

---

## EXHIBIT C: ABSENCE OF EXEMPTION LOG PREVENTS CASE-BY-CASE ATTACHMENT VERIFICATION {#exhibit-c}

### Reconciliation Note — Why the April 6 "Zero Attachments Produced" Finding Is Withdrawn

The April 6, 2026 draft asserted that 4,109 emails (54.3% of the then-analyzed 7,573-document universe) referenced attachments with 35,455 total references and zero attachments produced. That finding was generated by matching body-text attachment references against file-system-level attached files alongside the .msg containers, a method appropriate for .eml export formats. It was not appropriate for the Outlook .msg OLE2 compound-document format that the City actually produced, in which attachments are embedded **inside** the .msg container as OLE2 sub-streams rather than delivered as sidecar files.

On re-analysis with the `extract_msg` 0.55.0 Outlook OLE2 parser, **3,200 of the 4,846 .msg emails in the deduplicated corpus contain a total of 26,508 attachment objects embedded inside their containers**. The "zero attachments produced" finding is therefore **withdrawn** in its entirety.

### What the Corrected Analysis Shows

A substantial fraction of the 26,508 embedded attachment objects are cosmetic inline email-signature graphics (image001.gif, image002.gif, etc.) rather than substantive documents. The question that cannot be answered on the face of the production is: for any given email whose body text references a specific substantive document by filename, is that named document present as one of the embedded attachment objects within the .msg container, or is it absent?

In the **absence of any exemption or privilege log** (see Exhibit I below), that per-email verification is not possible. The April 22 draft's categorical "no attachments" claim overshot what the corpus can independently support. The correct and defensible claim is that the absence of a Vaughn-style index precludes case-by-case verification of whether specific substantive attachments referenced in email body text are in fact embedded within their .msg containers, redacted in whole or in part, or absent.

### Substantive Documents Whose Per-Email Production Status Cannot Be Verified Without a Log

| Document Referenced in Body Text | Number of Emails Referencing | Significance |
|------------|:---------------:|-------------|
| Embargoed press materials PDF (March 10, 2025) | 40 | Pre-announcement press package |
| Redmond Teen Services Engagement Plan (FINAL) | 38 | Community-engagement plan created after the decision was made |
| COR Community Center Presentation | 36 | Internal facility plans |
| 2025 Council Extended Meeting Calendar | 33 | Scheduling data |
| RCCMV Floor Plan | 20 | Replacement facility plans |
| To Do List for OFH-RCCMV Transition (Word) | 15 | Shutdown task list |
| IFB 10861-25 Bid Submittal Sheet (Word) | 12 | Financial bidding document |
| Teen Contact List (Excel) | 12 | Contact information for affected teens |
| **Amendment to Transfer Option Agreement (PDF)** | **4** | **Legal document for the $5.5 million Plymouth Housing property transfer** |
| **ALTA Title Insurance Commitment (PDF)** | **4** | **Title insurance for property transfer** |
| Interest Group 2025 Cost Recovery Alignment (PowerPoint) | 4 | Financial planning |
| Old Fire House Teen Center Daily Attendance (Excel) | 4 | Data used to justify closure |

### Legal Significance

Under RCW 42.56.210(3), every withholding — whether of an entire record or of portions of a record — must be accompanied by a written statement identifying the specific exemption claimed and a brief explanation of how the exemption applies. The City has provided neither an exemption log nor a privilege log nor a Vaughn-style index for any of the seven installments. That procedural failure is independently a basis for in-camera review under RCW 42.56.550(3), and specifically prevents the per-email attachment verification that the corpus would otherwise permit. The most legally significant documents whose verification is blocked — the Amendment to Transfer Option Agreement and ALTA Title Insurance Commitment — define the terms of the $5.5 million Plymouth Housing property transfer.

---

## EXHIBIT D: NEAR-TOTAL SUPPRESSION OF DECEMBER 2024 {#exhibit-d}

### Reconciliation Note — Gap Narrows to One Month on the Full Corpus

The April 6, 2026 draft asserted a five-month temporal gap from September 2024 through January 2025. On the full 4,846-file deduplicated corpus, Installments 5B, 5C, 6, and 7 substantially populate September 2024, October 2024, November 2024, and January 2025. The gap claim narrows to **December 2024 only**, where it is mathematically sharp and impeachment-proof on cross.

### The December 2024 Collapse

Across the entire 4,846-file corpus, **only 2 unique substantive email records are dated in December 2024**. The raw record count for December 2024 is 9; of those 9, seven (7) are duplicate copies of a single safety-audit email from John Assaker on December 12, 2024, and one (1) is a SharePoint system notification. Two unique substantive emails is the entire production for the month.

### December 2024 Was a Month of Documented Heavy Activity

The City's own production records confirm the following December 2024 activity on the subject matter of PRA 32782:

1. **Stepherson & Associates PR was on a documented monthly retainer of $4,468.75** (engagement beginning on or about November 14, 2024) and was generating material on OFH messaging;
2. **The Plymouth Housing Transfer Option Agreement was being finalized** during this period;
3. **File-naming conventions visible elsewhere in the production** — e.g., `2024_1220_Redmond Fire House Teen Center_Interview Plan` — prove that substantive OFH-related work products were generated during December 2024;
4. **Twenty-four (24) records located elsewhere in the production reference events in December 2024** in their body text, proving that the underlying discussions occurred and were recorded.

### Legal Significance

Two unique substantive emails in a month of documented multi-workstream activity is inconsistent with any search "reasonably calculated to uncover all responsive records" under *Neighborhood Alliance of Spokane County v. Spokane County*, 172 Wn.2d 702, 261 P.3d 119 (2011). Under *Hearst Corp. v. Hoppe* (1978), courts will not accept "we couldn't find it" where the production itself proves records exist. An accounting of the December 2024 collapse is required by Vaughn index.

---

## EXHIBIT E: [RESERVED — FILE-LEVEL INTEGRITY CLAIM WITHDRAWN] {#exhibit-e}

The April 6, 2026 draft of this Brief asserted at Exhibit E that approximately 96% of the produced .msg files exhibited internal corruption, on the theory that programmatic manipulation during export had preserved the OLE2 compound-document containers while destroying the internal MAPI property streams.

On full re-analysis of the 4,846-file deduplicated corpus using the `extract_msg` 0.55.0 Outlook OLE2 parser library — the standard Python tool for Microsoft Outlook .msg format — the .msg files parse cleanly, with internal property streams intact. The April 6 finding was a methodology artifact of applying a parser designed for RFC822 `.eml` format to files in Outlook's native `.msg` OLE2 compound-document format, and is **withdrawn in its entirety**. No file-level integrity claim is asserted in this Brief.

The remainder of the deficiency case — production inflation, records mathematically withheld from four named officials, absence of an exemption log, December 2024 near-total suppression, March 30, 2025 substantive cutoff, zero "Kenmore" mentions, channel switching, drive-level byte-identical duplicate zip, and the Installment 7 April 2024 size anomaly — is independent of any claim about file-level integrity and is unaffected by this withdrawal.

---

## EXHIBIT F: THE MARCH 30, 2025 SUBSTANTIVE CUTOFF {#exhibit-f}

### The Cutoff — Strengthens on the Full Corpus

Across the full 4,846-file deduplicated corpus, **only 6 emails are dated after March 30, 2025**. All 6 are automated notifications, alerts, petition emails, or non-substantive correspondence concerning Plymouth Housing financing. The City's production contains no substantive human-authored record after March 30, 2025 — an absence that spans more than twelve months of the PRA's active window and the entirety of the decision-making period that followed the initial backlash.

### Events of Facial PRA-32782 Significance After March 30, 2025 — Zero Records Produced

| Date | Event | Records Produced |
|------|-------|:----------------:|
| April 27, 2025 | Council study session on OFH building future | **0** |
| May 10, 2025 | Downtown Redmond light rail opens (property values surge) | **0** |
| June 28, 2025 | New zoning code effective — OFH site upzoned to 144 ft / FAR 8.0 | **0** |
| July 22, 2025 | Council study session — building assessments presented | **0** |
| October 2025 | Stakeholder group recommends rebuild (6 meetings) | **0** |
| November 18, 2025 | Council votes to demolish and rebuild (AM No. 25-184) | **0** |

The production covers the announcement and initial backlash (March 11–30, 2025). It does not cover a single day of the decision-making process that followed — no council deliberations, no stakeholder meetings, no demolition planning, no property negotiations, no zoning discussions. Each of the six named events generated City correspondence. None has been produced.

---

## EXHIBIT G: THE KENMORE BLACK HOLE {#exhibit-g}

The word **"Kenmore" appears zero times in the full 4,846-file deduplicated corpus** — zero mentions in subject lines, zero in body text, across the full universe of installments produced by the City.

Plymouth Housing was rejected by the City of Kenmore before being accepted by the City of Redmond approximately 22 days later, with $5.5 million in publicly-owned land. **Plymouth Housing appears in approximately 142 emails** in the production. The complete absence of any reference to Kenmore — the predecessor process whose rejection triggered Redmond's acceptance — across the full corpus is not plausible in any production that genuinely includes all responsive records.

Either every record mentioning Kenmore was withheld, or the search terms used to compile the production were constructed to exclude that subject. Either explanation independently constitutes withholding under RCW 42.56.

---

## EXHIBIT H: CHANNEL SWITCHING AND NARRATIVE CONTROL {#exhibit-h}

### Channel Switching — Holds Independent of Parsing Methodology

Approximately **45 records** in the corpus contain language directing substantive discussion off-record:

- "Give me a call" / "Call me" / "Discuss in person" / "Talk offline"

Examples from production:
- Kyle Muir to Hannah Dunaway: *"Give me a call to talk about the OFH email when you have a minute"*
- Derek Wing to Kyle Muir: *"Give me a call if you have questions"* (re: OFH update materials)

When City officials systematically move substantive discussions to phone calls, those discussions are not captured by email-based records requests. Communications conducted by telephone, in-person meeting, personal device, personal email account, or personal messaging account on the subject matter of PRA 32782 are public records subject to disclosure under *Nissen v. Pierce County*, 183 Wn.2d 863 (2015). None have been produced.

### Narrative Control

The production itself contains evidence of manufactured messaging:

- **Zach Houvener:** *"the Talking Points document is internal only and not meant to be public facing"*
- **Malisa Files to Lisa Maher:** *"Could you work with Loreen to work on talking points for the Mayor"*
- **Brant DeLarme:** *"rewriting the talking points with the Mayor's feedback"*
- **DeLarme to Maher:** *"PDF of all embargoed materials for tomorrow AM"*

The talking-points documents are repeatedly referenced in the body text of produced emails. Whether the actual attachments are embedded inside the .msg containers or are absent cannot be determined without the Vaughn-style index demanded in Exhibit C.

### The Decision Concealment

Internal email from Erica Chua: *"I am aware that it was decided that the teen center was going to be demolished because it was deemed too expensive and effortful to upkeep it"*

Note the passive voice: "it was decided." No email in the production identifies who made the decision to close the OFH. The identity of the decision-maker is not recoverable from the production on its face.

---

## EXHIBIT I: NO EXEMPTION LOG; NO PRIVILEGE LOG; NO VAUGHN INDEX {#exhibit-i}

For each of the seven installments produced, the City provided **no accompanying exemption log, no privilege log, and no Vaughn-style index** identifying records withheld in whole or in part and the legal basis for each withholding. Under RCW 42.56.210(3), every withholding must be accompanied by a written statement identifying the specific exemption claimed and a brief explanation of how the exemption applies to the specific record. The City has provided neither for any installment.

The categorical absence of an exemption log is independently a basis for in-camera review of every withheld record under RCW 42.56.550(3), for the imposition of penalties under RCW 42.56.550(4), and for the case-by-case attachment verification contemplated at Exhibit C above.

---

## EXHIBIT J: DRIVE-LEVEL BYTE-IDENTICAL DUPLICATE ZIP {#exhibit-j}

In the Google Drive production folder from which Plaintiff retrieved the expanded installments, the file `Inst_7_Jan_2024.zip` appears twice:

- `Inst_7_Jan_2024.zip` — 79,783,936 bytes
- `Inst_7_Jan_2024 (1).zip` — 79,783,936 bytes
- MD5 hash match: `9fccacfe...` (byte-identical)

The City uploaded the same 80 MB archive twice with a "(1)" suffix in the delivery folder Plaintiff accessed. This is production-level duplication at the delivery layer — distinct from, and additive to, the email-internal duplication documented at Exhibit A. It is an independent basis for concern that the City's internal records of the production itself are unreliable, and an additional target for the Vaughn-index process accounting demanded at § III of the companion Deficiency Notice.

---

## EXHIBIT K: INSTALLMENT SIZE ANOMALY — INST_7_APR_2024 AT 6.65 MB PER EMAIL {#exhibit-k}

The archive `Inst_7_Apr_2024.zip` contains 167 labeled emails but is approximately **1.11 GB — an average of 6.65 MB per email**. Standard .msg files typical of the balance of the production are 50–300 KB per file, not megabytes. A 20×–130× per-file inflation on a single installment without parallel inflation elsewhere is an anomaly requiring accounting — either (i) massive attachment bundling, in which case the substantive attachment inventory for that installment must be enumerated in the Vaughn index; or (ii) padding of another kind, in which case the nature and source of the padding must be disclosed.

---

## LEGAL STANDARDS VIOLATED

### RCW 42.56.030 — Right of Access
> *"The people of this state do not yield their sovereignty to the agencies that serve them. The people, in delegating authority, do not give their public servants the right to decide what is good for the people to know and what is not good for them to know."*

The City decided what was good for the public to know: approximately 1,155 excess duplicate copies. What was not good: the outgoing communications of four named officials, the substantive records of December 2024, and every substantive record generated after March 30, 2025.

### RCW 42.56.070 — Duty to Provide Fullest Assistance
The City did not provide fullest assistance. Production inflation by duplication, delivery-level duplicate archives, and extreme per-email installment size without accompanying attachment inventory are inconsistent with that duty.

### RCW 42.56.080 — Format Requirements
Records must be provided in their existing format. The absence of a Vaughn-style index prevents verification of whether specific substantive attachments referenced in email body text are embedded in the .msg containers, redacted in whole or in part, or absent.

### RCW 42.56.210(3) — Written Exemption Justification
Any withholding must be accompanied by a written statement identifying the specific exemption and a brief explanation of how the exemption applies. **No exemption or privilege log was provided for any of the seven installments.**

### RCW 40.14 — Records Retention
The December 2024 near-total suppression and the March 30, 2025 substantive cutoff raise serious questions about records destruction and retention-schedule compliance. Under RCW 40.14.060, destruction of public records outside authorized retention schedules is a criminal offense.

### Applicable Case Law

- **Neighborhood Alliance v. Spokane County (2011):** Agencies must conduct searches reasonably calculated to uncover all responsive records. The December 2024 collapse and zero Kenmore results demonstrate the search was inadequate or deliberately narrow.
- **Nissen v. Pierce County (2015):** Government business conducted on personal devices or off-system channels is subject to disclosure.
- **Rental Housing Assn. v. City of Des Moines (2012):** Courts have imposed penalties of $25/day per record for deliberate withholding.
- **Hearst Corp. v. Hoppe (1978):** Courts will not accept "we couldn't find it" when evidence shows records should exist.
- **Progressive Animal Welfare Society v. UW (1994):** The PRA must be liberally construed to promote transparency.

---

## PENALTY EXPOSURE

Under RCW 42.56.550(4), a court may impose penalties of not less than $5 nor more than $100 per day per record for each day on which a record is wrongfully withheld. The per-day clock runs from the date of constructive denial of each withheld record, which, for records identifiable as withheld at the time of each installment, runs from no later than the date of that installment.

The precise per-day-penalty computation is reserved for the Court. The categories of wrongful withholding established on the face of the production — outgoing communications of four named zero-outgoing officials (Fields, Salahuddin, Council mailbox, Payne), the December 2024 collapse, the universe of post-March-30 substantive records across twelve months of active decision-making, records mentioning Kenmore, and any records of off-system communications under *Nissen* — each generate a per-day record count whose arithmetic cannot be estimated from the face of the production and must be developed in discovery, including through the Vaughn-index process demanded in the companion Deficiency Notice and in Exhibit I above.

The prevailing party on a PRA action is entitled to **reasonable attorney fees and costs** under RCW 42.56.550(4). That provision eliminates the financial barrier to litigation and independently incentivizes settlement and full production.

---

## EVIDENCE PRESERVATION

All evidence supporting this brief has been preserved locally and is available for production:

### Databases (Forensic Analysis)
- `corkboard.db` (69MB) — full raw-record email index (7,573 pre-deduplication records resolving to 4,846 unique emails under body-hash dedup), 337 people, 717 connections, fully indexed
- `tampering_evidence.db` (52MB) — 5,814 messages with file integrity/hash data
- `msg_scan_cache.db` (39MB) — Raw file scan cache with corruption type analysis
- `foia_complete.db` (54MB) — Alternate extraction, 6,106 emails
- `quantum_foia_complete.db` (29MB) — 3,063 emails + 1,596 named entities

### Raw Productions (Original Files as Received)
- 1st Installment ZIP (91MB)
- 2nd Installment ZIP (598MB)
- 3rd Installment ZIP (47MB)
- 4th Installment ZIP (78MB)
- Total: 814MB of original productions preserved

### Analysis Methodology
All forensic analysis tools are preserved:
- `gap_finder.py` — Temporal gap identification
- `ghost_probe.py` — Reply-chain withholding analysis
- `duplicate_probe.py` — Duplication/padding analysis
- `forensic_deep.py` — Deep forensic analysis
- All tools produce reproducible results against the preserved databases

### SHA256 Integrity Verification
All 284 evidence archive files have been SHA256 hashed. The hash manifest is preserved at `medium_forensic/evidence_archive/SHA256_MANIFEST_2026-04-06.txt`. Any alteration of evidence files is detectable.

---

## CONCLUSION

The City of Redmond's response to PRA Request #32782 is not a good-faith production of public records. The mechanisms documented in this reconciled brief — production inflation by duplication at both the email and delivery layers, zero-outgoing status for four named City officials against substantial inbound volume, near-total suppression of December 2024 in a month of documented heavy activity, a substantive cutoff at March 30, 2025 that silences twelve subsequent months of active decision-making, zero mentions of the predecessor Kenmore process, channel-switching directives moving substantive discussion off-record, the absence of any exemption or privilege log, a drive-level byte-identical duplicate archive, and a single-installment per-email size anomaly — are individually provable on the face of the 4,846-file deduplicated corpus.

Every number in this brief is derived from analysis of the full corpus using the `extract_msg` 0.55.0 Outlook OLE2 parser library and is reproducible against the preserved installments. Each withholding identified in Exhibit B is mathematically compelled by the RFC 5322 structure of produced replies. The April 6, 2026 draft's withdrawn claims (96% corruption, categorical "no-attachments," five-month gap) are not re-asserted and are not load-bearing for any element of the deficiency case.

The question is not whether the City of Redmond's response is non-responsive. The reconciled evidence establishes that it is. The question is what a court will do about it.

---

*This brief is supported by the following source documents:*
- `PRA_SUPPRESSION_REPORT.md` — Complete statistical analysis (41KB)
- `FORENSIC_INTEGRITY_ANALYSIS.md` — File corruption analysis (24KB)
- `FORENSIC_REPORT_COMPLETE.md` — Full forensic report (15KB)
- `SOURCED_FORENSIC_REPORT.md` — Sourced version for legal use (24KB)
- `PLYMOUTH_HOUSING_REPORT.md` — Plymouth Housing property transfer analysis
- `THE_FULL_PICTURE.md` — Complete conspiracy theory with evidence layers

*Prepared using forensic analysis of the City of Redmond's PRA productions. All data is derived from records produced by the City itself.*