Gmail-style render packet
PLSAS Emailed Again. The Receipt Got Preserved First.
Public-redacted fake-native Gmail renders preserving the June 25 PLSAS message and the same-thread response draft.

PLSAS
Suspected suppression of maltreatment reporting, bad-faith Title IX investigative posture, and suspected record access and classification violations.
Some private identifying information has been redacted. Our redactions appear in red and are indexed inside each document. Any other redactions shown are part of the record as it was provided.
Redacted materials only. Native originals stay off the public table.
Updated June 26, 2026
Amazingly, PLSAS emailed us today. Not surprisingly, it was Mr. Robert Cothern. His prior responses have created a recurring accuracy problem, and the unresolved records universe made this one worth preserving before anyone had to spend the evening with it.
Here is the bet I would have been comfortable making before opening it:
We are in too good of a mood to deal with him right now, so we preserved the Gmail-thread source, built public-redacted fake-native renders, and bundled the district message with the same-thread response draft. Tomorrow we can compare the record against actual reality. Tonight, Compliance Theater built the PDF and the receipt can speak for itself.
Start here
Gmail-style render packet
Public-redacted fake-native Gmail renders preserving the June 25 PLSAS message and the same-thread response draft.
Board email
A warning that the investigation record universe was collapsing under its own contradictions, paired with board receipt proof.
Attached packet
Source records, finality claims, and Title IX posture all meet in the same dark hallway.
Board email
The board was told the maintained records could not all be true at once, and the receipt trail says the message arrived.
Attached packet
The board was put on notice that the district's represented record universe appears to contain mutually incompatible facts.
Board email
A simple question with ugly implications: who accessed student records, under what posted category, and where is the basis?
Attached packet
A notice asking the district to identify the actual FERPA/MGDPA category mapping it relied on before records kept moving.
Board email
Contractor, counsel, FERPA, and disclosure-log reliance all collide in one tidy little governance headache.
Attached packet
A disclosure-log and access-basis problem dressed up as routine contractor/counsel handling.
Board email
A June 11 records response becomes a board-level problem once the district is held to the universe it represented.
Attached packet
A response-role accountability notice for the part where the district's data-practices posture needed adult supervision.
Clarification record
A cure path was offered. The paper trail is quieter than one would hope after that.
Attached packet
The pending/timing half of the status tracker, redacted for child PII and sensitive assault-context references.
Attached packet
The active elapsed-status guide from the June 23 tracker, using red-box PDF redactions for postable release.
Annotated investigation records
The District investigated itself, preserved the redactions, and somehow the black boxes are not the worst part.
Release packet
Training, correction, and response records showing how basic Title IX and maltreatment obligations got treated as optional paperwork.
Emily bundle
The record is accurate, everything responsive has been provided, the complaint is dismissed. Nothing to see here, apparently.
Attached packet
Our current pending PLSAS request list. Each row is either a correction request or a small, scoped records request, and for most rows the expected answer may simply be a request-specific no-records response.