Cherreads

Chapter 72 - CHAPTER 72. The Leak

Mara wakes before dawn because the habit of being on call never quite leaves you. She brews coffee, opens her laptop, and reads the thread one more time—not to rehearse grievance but to make sure the facts are right. Her post has been up for a day: a careful account of what it felt like to be a verifier, the small, accumulating burdens, the moments when repair felt insufficient. She did not want to shame anyone; she wanted to name labor. The comments are a mix of gratitude, skepticism, and the predictable moralizing that follows any public airing. Mara scrolls, corrects a typo, and then closes the laptop. There are things she will say in public; there are things she will keep private. She has learned the difference.

Across town, a reporter at the regional paper reads Mara's post and sees a pattern that fits the piece she's been drafting about the pilot's public profile. The harbor pause, the council forum, the foundation's deadline—these are not isolated incidents. They are a story about a practice moving from rehearsal rooms into public life without a fully formed infrastructure for the people who hold it. She emails Theo with a list of questions and asks for documents: the case study, the stipend schedule, and any onboarding materials. Her tone is professional; her curiosity is sharp. She is not looking for scandal; she is looking for clarity.

On the tour, Priya wakes to a message from a company director: a local blog has republished a clip with a new, angrier caption. The director is worried about ticket sales and about the actors who are tired of being discussed in comment threads. Priya forwards the message to Julian and Theo and then calls a quick meeting in the hotel lobby. They talk through the immediate steps—an updated public statement, an offer to host a community conversation in the town, and a reminder to the company that the pilot's repair protocol is available if anyone wants a private check‑in. The conversation is brisk and practical; it is also the kind of triage that has become routine.

Back at the conservatory, Theo reads the reporter's email and Mara's post in the same sitting. The two documents sit like different kinds of pressure: one asks for legibility, the other asks for justice. He calls a meeting and lays both on the table. "We invited scrutiny," he says. "Now we have to answer it without defensiveness." Julian nods. Priya rubs her temples. Lena asks whether they should bring in an external mediator to help frame the listening sessions. Theo thinks of the verifier who stepped down and of the actor who left the stage in tears. He thinks of the parent who had said, Be clearer. He thinks of Mara's line about labor. "Yes," he says. "We bring in a mediator. And we open the listening sessions to former verifiers."

Mara's public piece has a consequence the team had not fully anticipated: a former verifier emails a draft of an internal handbook—an early, candid version that includes rehearsal notes, blunt reminders about tone, and a few lines that read like private coaching. The draft was never intended for public eyes. It lands on the listserv and then on a blog. The excerpt is not damning, but it reads raw; readers unfamiliar with rehearsal language interpret it as evidence of casualness. The leak forces a new conversation about internal language and public perception.

The reporter's piece runs with a headline that balances curiosity and caution. She quotes Mara, a community partner, and a parent who had attended the school residency. She also quotes a critic who asks whether theatrical rehearsal is an appropriate method for teaching consent. The article does not decide; it frames. But the framing is enough to prompt a call from the foundation's program officer. The officer asks for a meeting and for a copy of the case study earlier than planned. The deadline, already tight, tightens.

Theo spends the afternoon drafting a response that is both candid and procedural. He offers the case study, the stipend appendix, and an invitation to the listening sessions. He writes in the plain language he uses in meetings: no spin, no flourish. He sends the packet and then, because he knows transparency is not a one‑way street, he calls Mara and asks if she will join a moderated listening session with current verifiers and the foundation's representative. Mara hesitates for a beat and then agrees. "I'll come," she says. "But I want it to be real."

The listening session is scheduled for a week out and the team spends the days before it preparing in a new way. They do not only rehearse demonstrations; they rehearse how to listen. Priya works with a mediator to draft a short script for opening the room: a statement of purpose, a set of confidentiality norms, and a clear invitation for critique. Julian prepares a transparent budget appendix that shows stipend lines, travel reimbursements, and the counseling referral fund. Lena prepares translations and a plain‑language FAQ for community partners. Bash organizes a small ritual of thanks—handwritten notes and fox puzzles—for verifiers who have carried extra weight.

On the morning of the session, the conservatory's small studio is arranged like a civic room rather than a rehearsal space: chairs in a circle, water on a table, a whiteboard with the session's goals. Mara arrives early and sits quietly, watching people come in. A former verifier she knows slips her a note: Thank you. Theo sits across from her and feels the familiar tug of responsibility and the new, sharper tug of accountability. He opens the session with a short statement: the pilot's aims, the harbor incident, the leak, and the foundation's deadline. He names the limits they have discovered and the changes they have already made. Then he invites Mara to speak.

Mara's testimony is precise and humane. She describes the work's value—the moments when a private check‑in prevented harm—and she names the costs: late emails, unpaid travel, the emotional labor of holding other people's feelings. She does not ask for blame; she asks for structures. She suggests a rotating on‑call schedule, clearer hour expectations, and a modest onboarding stipend. She asks for a transparent timeline for stipend payments. The room listens. Some people nod; others write notes. A current verifier speaks about the difficulty of balancing empathy with boundaries. A community partner describes the relief of a clear preface for mixed audiences. The mediator keeps the conversation focused and practical.

After the session, the team drafts an action plan in real time: immediate stipend timeline, a pilot of a rotating on‑call schedule, a revised onboarding checklist, and a public addendum to the case study that acknowledges the leak and explains the iterative nature of the handbook. Julian emails the foundation with the plan and asks for a short extension on the public brief so they can include the listening session's outcomes. The foundation replies within the day: they will consider the extension but want a clear timeline. The deadline remains a pressure, but the team has turned critique into a set of concrete steps.

The leak's public ripples do not end. A local council member posts a short note thanking the pilot for appearing at the forum and for the listening session; a few skeptical alumni post sharp replies. The reporter writes a follow‑up that highlights the listening session and quotes Mara's practical suggestions. The tone of the coverage shifts from suspicion to engaged scrutiny. It is not vindication; it is a different kind of attention—one that asks for evidence of change rather than spectacle.

That night, Theo walks across the campus with Amelia. The air is cool and the conservatory lights are low. He tells her about the session—what was said, what they decided, and how Mara's testimony landed. She listens and then, with the steadiness that has become her signature, asks the question he has been avoiding: "What will you do if the foundation still wants measurable outcomes that don't capture labor?"

He thinks of the verifier who had stepped down, of Mara's careful list, and of the parent who had asked for clarity. He thinks of the pilot's ethics: co‑design, stipends, and repair. "We'll push back," he says. "We'll argue that labor is an outcome. We'll show them the listening session and the action plan. And if they still want numbers, we'll give them numbers that include hours, stipends, and counseling referrals—not just attendance."

Amelia squeezes his hand. "Then say that," she says.

Theo writes a line in his notebook that night, not as a neat ending but as a ledger entry: "Leaks force us to translate private practice into public policy; the work is to make the translation honest." He underlines it once and then, because the day has been long, closes the book.

The leak has changed the pilot's trajectory. It has made labor legible, it has forced the team to formalize what had been tacit, and it has shifted the public conversation from spectacle to structure. The foundation's deadline still stands; the public record still exists; the evaluation will be rigorous. But the listening session has given the team a new resource: a set of concrete steps that respond to critique rather than deflect it. They have not solved everything. They have, for the first time in a while, a map for the next work.

More Chapters