# Reader briefing (shared by all bundle readers)

## Context
Better Plan BVSD is a parent/community coalition in the Boulder Valley School District (Colorado). The BVSD Board votes on **Sept 22, 2026** on the superintendent's "Resilient Schools" proposal, which closes/consolidates elementary schools because of declining enrollment. The coalition asks the board to vote NO and come back with a complete plan. Schools named in the debate include Flatirons, Douglass, Mesa, Birch (Broomfield), Whittier, Fireside, Centennial, Columbine, Eldorado, Heatherwood, Gold Hill, Community Montessori, and others.

Boulder Reporting Lab (reporter Jenna Sampson) filed Colorado Open Records Act (CORA) requests with BVSD for emails/calendar items of Superintendent Rob Anderson, Chief Communications Officer Randy Barber, Chief Operations Officer Rob Price, and Laura Shafer, concerning school closure/consolidation, facility reuse/lease/sale, and related terms. The district's production (397 files, mostly emails rendered to PDF, plus a few attachments) has been shared with the coalition. Our job: understand what is in it and what matters for the closure debate.

## Your bundle
You are given one bundle text file. It concatenates many extracted documents. Each document starts with a line `=== FILE: <name>` and threads are grouped under `### THREAD: <subject>`. Emails in a thread often quote earlier emails, so later files repeat earlier content; do not re-summarize repeated content, but DO note when a later reply adds something. Some files are marked `[DUPLICATE of ...]`; skip those. Attachments (contracts, decks, spreadsheets) appear as their own FILE entries.

Read the WHOLE bundle. It is large; use the Read tool with offset/limit and page through it completely. Do not stop early. Do not skim the second half.

## Deliverable
Write a markdown file at the path given in your task. Structure:

### 1. Thread-by-thread digest
For EVERY thread in the bundle (use the `### THREAD:` headings), one entry:
- **Subject** | date range | participants with role/org where known (e.g. "Randy Barber, BVSD Chief Comms Officer"; "Amy Bounds, Daily Camera reporter") | files (list the FILE names, abbreviated is fine)
- **What it is:** 2-4 sentences, plain English.
- **Key facts / quotes:** bullets. Include specific numbers, dates, dollar amounts, names of schools, and short verbatim quotes (under 40 words each) that are notable. Cite the FILE name for each quote.
- **Relevance to the closure debate:** High / Medium / Low, with one sentence why.
- **Tags:** pick from: PROCESS, CONSULTANTS, FINANCES, FACILITIES-REUSE, HOUSING, COMMUNICATIONS-PR, COMMUNITY-INPUT, PRESS, HISTORY, DATA, BOARD, STAFF-HR, SCHOOL:<name> (one per school mentioned substantively), NOISE.

### 2. Top findings in this bundle
The 5-15 most newsworthy, surprising, or strategically useful things for a coalition arguing the plan is incomplete or the process was flawed, OR things that cut the other way (evidence the district's case is solid). Be fair and factual. Each: one paragraph, cite files.

### 3. Timeline entries
Dated events found in this bundle, one per line: `YYYY-MM-DD — event — (file)`. Include meetings, decisions, contract signings, presentations, press events, deadlines.

### 4. People directory
`Name — role/org — how they appear in this bundle`. Only people who appear substantively.

### 5. Numbers and claims worth checking
Any figure the district or others state (savings, enrollment, capacity, costs, class sizes, timelines) with the file it comes from.

## Rules
- Facts only; quote verbatim where it matters; never invent. If a document is a form letter or auto-notification, say so in one line.
- Note redactions or withheld attachments when you see them.
- Do not editorialize beyond the "relevance" and "top findings" sections.
- Aim for completeness over brevity; this file is the coalition's index to the bundle. 3,000-8,000 words is expected.
