# MEMORANDUM — PRIVILEGED & CONFIDENTIAL / ATTORNEY WORK PRODUCT

**To:** Human Resources; General Counsel
**Re:** Maya Lin — retaliation exposure and the only defensible separation path
**Bottom line:** A for-cause termination now is close to indefensible and would likely convert a manageable restructuring into a liability event. The single narrow path is faithful implementation of the December 18 board plan — all four positions eliminated, eight weeks' severance paid, no substantially identical replacement role, and Reid removed from every decision touching Maya. If Kestrel wants to keep the "validation integrity" unit as Reid proposes, that path closes and Maya must be retained or selected under objective criteria applied by someone else.

---

## 1. Protected activity and the 90-day presumption

Maya's January 5 report of altered pressure-test entries is squarely protected. Under Rule 1 she needed only a reasonable belief; the January 20 audit substantiated two of three items, which makes the reasonableness question effectively unlitigable — and the unsubstantiated third item remains protected as well. There is no "partial protection" argument available.

Reid, the manager driving both the discipline and the restructuring proposal, received the report on January 5. Decision-maker knowledge is therefore admitted, not inferable.

Any adverse action through **April 5** carries a presumption of causation. That includes the January 10 warning, a termination on any theory, and Reid's proposed reassignment of duties. Once the presumption attaches, Kestrel bears **clear and convincing** proof it would have taken the identical action for lawful reasons absent the report — the highest civil burden, on our side, on a record we largely wrote after January 5.

Assume also that the substantiated audit findings create independent correction and possible regulatory-reporting duties. Terminating the reporter while the substantiated findings are open is the single worst optical and evidentiary posture available.

## 2. Reid's text, the January 10 warning, and the comparator record

Reid's January 6 text — *"She went nuclear. Build the file before she makes herself untouchable"* — is direct evidence of retaliatory motive and of intent to manufacture a pretextual record. It is not ambiguous, not deniable, and it is dated one day after the report. Practically, it means:

- **Every** subsequent document Reid authored about Maya is presumptively the "file" he announced he would build. Sudden documentation is expressly identified in Rule 4 as undermining the defense; here we have a confession that the documentation was strategic.
- The January 10 warning — five days after the report, for **prior-year** lateness that generated no contemporaneous discipline — is the predicted document. It is likely an adverse action in its own right (it is the predicate Reid now uses for "insubordination") and, at minimum, is powerful evidence of pretext.
- The comparator record is inverted against us: analysts with **two or three** late reports received coaching. Maya, with two, received Kestrel's first written warning to any analyst. That is a departure from consistent comparator treatment against an employee with four consecutive "exceeds expectations" ratings.

**Recommendation:** rescind the January 10 warning and substitute coaching consistent with comparators. This is not an admission; it is the removal of a document that cannot survive scrutiny and that currently taints everything built on top of it. Reid's conduct — the text and the disparate discipline — should itself be investigated and addressed, which is also mitigation evidence.

Reid's proposed rationale, **"data theft and insubordination,"** is a third problem. It mislabels an encrypted internal transfer to the employee's own work-from-home account as theft, and there is no identified order that was disobeyed, so "insubordination" appears to be repackaged January 10 lateness. Inflated and shifting characterizations are precisely what Rule 4 says defeats the same-action defense.

## 3. The January 28 personal-account transfer

This is genuine, independent policy misconduct and Kestrel is entitled to respond to it. Rule 5 permits that — but on Rule 5's terms: fair investigation and **the same consequence applied to materially similar conduct**.

Every material fact points to a written warning:

| Policy trigger | Facts |
|---|---|
| First personal-account transfer | Yes |
| Regulated personal data exposed? | No — safety spreadsheet, encrypted |
| Third-party receipt / dissemination | None |
| Comparators (two analysts, last year) | Written warning |

The prescribed consequence is a written warning; the exception (regulated personal data) is not met; the only two comparators received warnings. Terminating on these facts is a departure from written policy **and** from consistent comparator treatment, within 90 days, by a manager who wrote "build the file." Kestrel could not carry a clear-and-convincing burden on that record, and the attempt would supply the jury with the pretext narrative.

Two further points:

- This is **not** after-acquired evidence. Kestrel learned of it before any decision, so Rule 6's remedy limitation is unavailable; it must stand or fall as a contemporaneous reason, and it will not support termination.
- Do not use the transfer to route around severance. Rule 8 bars using "for cause" to defeat promised severance, and a for-cause designation resting on conduct the policy punishes with a warning is the paradigm violation.

**Recommendation:** issue the policy-prescribed written warning for the transfer, documented by someone other than Reid, after a short fair-process interview in which Maya is allowed to respond. Then treat the discipline track as closed.

## 4. The pre-report restructuring plan — our strongest asset

The December 18 plan is the best evidence Kestrel has, and it is genuinely good evidence:

- **Board-approved and written**, not a manager's improvisation.
- **Timestamped December 18**, eighteen days before the report — a contemporaneous pre-report plan under Rule 4 and a "fixed before the report" RIF under Rule 8.
- **Identifies all four positions by employee number**, so Maya was designated before anyone knew she would report. There is no post-report selection decision to attack.
- **Independent business rationale**: closure of the product line.
- **Three other scheduled eliminations still on track**, corroborating that the plan is real and not a vehicle built around one employee.
- **Eight weeks of severance** already provided for.

Preserve the plan's metadata immediately and confirm there are no post–January 5 edits. If the document was touched after January 5, we need to know now, because a modified "pre-report" plan is worse than no plan at all.

## 5. Retaining the other three and reposting 80 percent of Maya's duties — the defense-killer

Reid's proposal destroys everything described in Section 4.

If three of the four designated employees are moved into a new "validation integrity" unit and Maya alone is separated, then the December plan is no longer what is being implemented. What is being implemented is a **post-report selection of Maya out of a group of four** — made by, or on the recommendation of, the manager who wrote "build the file," with no objective selection criteria, and against the group's highest-rated performer. The presumption attaches to that selection, and there is no same-action evidence supporting it: the pre-report plan says nothing about who gets retained, because it contemplated retaining no one.

Posting a role with **80 percent of Maya's former duties** independently triggers Rule 8's prohibition on relabeling a substantially identical replacement role. An 80-percent-overlap posting is not a genuine elimination of a position; it is a renamed position. Combined with retention of the rest of the group, a factfinder would readily conclude the product line "closure" was the wrapper and Maya's removal was the content — and Reid's text supplies the motive.

**Kestrel must choose one of two structures. It cannot have both.**

- **Structure A (genuine elimination):** the pressure-test function truly ends. All four positions go on February 15. No "validation integrity" unit performing substantially the same work, and no posting of a role with 80 percent of Maya's duties. All four receive eight weeks' severance on identical terms.
- **Structure B (function continues):** Kestrel needs the validation integrity work. Then Maya must be included in the retention pool and evaluated under objective, written criteria applied before names are attached, by a decision-maker other than Reid. On this record — four consecutive "exceeds expectations" ratings versus a rescinded warning and a first-offense warning — Maya is likely the **strongest** candidate for retention, and any outcome placing her last will be read as engineered.

The practical test to put to the business, in writing, before anything happens: *If Maya had never filed the report, would the validation integrity unit exist, and who would be in it?* If the honest answer is that the unit exists because the work continues, Structure A is unavailable and Maya should be retained.

## 6. Manager taint and independent review

Rule 7 makes this decisive. Reid received the report, announced the file-building plan, issued the anomalous warning, characterized the transfer as "data theft and insubordination," and is now the source of the retention/reposting proposal. Whoever signs the notice, the decision is Reid's unless we structurally break the chain.

Required steps:

1. **Wall Reid off** from any decision, recommendation, documentation, or reference concerning Maya — discipline, RIF implementation, retention selection, severance, and any employment reference.
2. Appoint an **independent decision-maker** (senior HR plus counsel, no reporting line to Reid) who re-examines the record from the ground up: interviews Maya, reviews the audit, pulls the late-report and personal-account-transfer comparator data, and evaluates whether the January 10 warning should stand.
3. Have the **business rationale for the product-line closure independently verified** by finance/operations — evidence unconnected to Reid that the line is closing and the function is ending.
4. Document the reasoning contemporaneously and **do not change reasons**. Shifting rationales are enumerated in Rule 4 as fatal.
5. In the interim, do **not** strip Maya's duties, exclude her from meetings, or open a broad investigation into her; material duty removal and a materially adverse investigation are themselves adverse actions under Rule 2.

## 7. Preservation and communication risks

**Issue a litigation hold today**, covering: the January 5 report and file; the January 20 audit and all workpapers and underlying pressure-test data; the Reid–HR text threads in full (both handsets, both directions, including deleted content); Maya's performance records and all four prior reviews; comparator discipline for late reports and for personal-account transfers; the December 18 plan with metadata plus all drafts, board materials and minutes; all validation-integrity-unit and job-posting documents and drafts; severance calculations; and all decision communications, including CEO messages. Suspend auto-deletion on the relevant accounts and devices, including Reid's. Spoliation here would be catastrophic given that the key document is a text message.

**The CEO's proposed announcement must not issue.** Publicly stating that *"whistleblowing does not excuse misconduct"* (a) publicly ties the separation to the protected report, supplying causation from our own mouth; (b) broadcasts a pretextual for-cause label to Maya's labor market, inviting a defamation claim; and (c) is itself hostility evidence and a potential standalone retaliatory act against other employees considering reports. Any external or internal communication should be restructuring-neutral, should not mention the report or misconduct, and should be cleared by counsel. Tell the CEO plainly: the "immediate for-cause, no severance, public statement" package is the highest-cost option on the table and would likely turn an eight-week severance into a multiple of back pay, front pay, and fees.

## 8. May any termination proceed now, and on what basis?

- **For cause: no.** Not on the January 10 warning (stale, comparator-inconsistent, admitted file-building), not on the transfer (policy prescribes a warning; both comparators received warnings), and not on "data theft and insubordination" (mischaracterization). A for-cause termination would be presumed retaliatory and unrebuttable by clear and convincing evidence.
- **Discipline that may proceed:** the policy-prescribed **written warning** for the January 28 transfer, issued by the independent reviewer, plus rescission/downgrade of the January 10 warning to match comparators.
- **Separation that may proceed:** only the **December 18 restructuring, implemented as written** — Maya separated on February 15 as one of four eliminated positions, on the same terms as the other three, with **eight weeks' severance paid in full**, no for-cause designation, and a neutral separation letter citing the product-line closure.

On severance: pay the full eight weeks promised by the plan; do not reduce, condition, or offset it against the transfer incident. If Kestrel wants a release, pay **additional** consideration for it, and ensure the agreement carves out the right to report to, communicate with, cooperate with, and receive awards from regulators, and does not restrict testimony or discussion of the substantiated safety findings. A release or non-disparagement clause that gags safety reporting would be both unenforceable and a fresh retaliation exhibit. Also offer, in writing, priority consideration for any Kestrel opening she is qualified for — cheap insurance and inconsistent with a retaliatory narrative.

## 9. The narrow lawful path — and the alternative

**If the product-line elimination is genuine:**

1. Independent reviewer confirms, with non-Reid evidence, that the line is closing and the pressure-test function is genuinely ending.
2. Reid is walled off from all decisions concerning Maya; his warning is rescinded and his conduct addressed separately.
3. The transfer is resolved with the policy-prescribed written warning — closed, not carried forward.
4. **Reid's proposal is rejected.** No validation integrity unit staffed with the other three, and no posting of a role with 80 percent of Maya's duties. All four positions end February 15; if the function is genuinely gone, the work does not need to be re-created under a new name.
5. All four separations are executed on identical terms, on the plan's original date, with eight weeks' severance and neutral, restructuring-only documentation. The other three scheduled eliminations proceed as planned.
6. Contemporaneous memorandum records the pre-report plan, the objective basis, the identical treatment, and the fact that the report played no role.

That combination — a timestamped pre-report board plan naming Maya by employee number, an unrelated product-line closure, identical treatment of three comparators, full promised severance, and no replacement role — is the only configuration that can plausibly satisfy clear and convincing evidence despite the 90-day presumption and Reid's text.

**If the elimination is not genuine — i.e., the function continues in any form, the unit is created, or the 80-percent role is needed:**

Then Kestrel has no lawful basis to separate Maya now, and it should not try. Instead: retain Maya (or run a genuine, criteria-first selection among all four in which her four "exceeds expectations" ratings are given their weight), restore her duties, rescind the January 10 warning, issue only the transfer warning, remove Reid from her chain of command, complete the audit remediation, and document the corrective steps. Kestrel can revisit the position later on a clean record, at a distance from the report, with a legitimate and documented rationale.

The choice is genuinely binary. Attempting Structure A while quietly building Structure B — eliminating Maya's position while retaining her group and reposting her duties — is the one outcome that guarantees liability, because it proves in a single document set that the "elimination" was a label and Reid's January 6 text was the plan.