Nadia Brooks
Evan's controls-engineering manager, whose team receives a genuine safety and schedule benefit from his release method; she becomes its sincere institutional advocate.
Consolidated from the development brief (§8.4). The brief is the canonical source: story/development-brief.md.
Working design (brief §8.4)
A friend, partner, colleague, patient, or online collaborator experiences a genuine benefit from the machine: relief from anxiety, cognitive clarity, or a brief return of memory. They become the sincere advocate who scales the effect. This person is not a fool or cultist. Their benefit is real, which makes their support dangerous and prevents the conflict from collapsing into “sensible people versus mad scientist.” The role can merge with the collaborator or remain distinct depending on cast size.
Related conflict pressure (brief §9)
Interpersonal: the collaborator demands restraint, the relative resists being optimized, and followers sincerely want continued access.
Established continuity (Chapters 7 and 14)
- Nadia manages six controls engineers, tests Evan's work at the motor bench, and gives him technical ownership of a five-gate release recovery after his dual-hypothesis estimator solves a dangerous zero-speed failure.
- The recovery finishes early, passes qualification, eliminates unsafe torque spikes, and cancels a weekend shift. Her support follows results she and her team can independently inspect, not direct exposure to the projector.
- She independently uses Evan's unspoken phrase "permission not to choose" and recasts the five gates as a general decision structure that preserves alternatives until measurement resolves them.
- She initiates a company-wide pilot because the method is useful. Her voluntary, evidence-based advocacy becomes the first institutional scaling path for the projector's broader causal capture.
Established continuity (Chapter 16)
- Nadia isolates the motor bench after Lin finds rank collapse across independently clocked channels during live accepted corrections.
- She blocks the new supervisor from customer deployment, preserves hard trips, and refuses to restore the older unsafe release merely because the safer implementation produces an unexplained effect.
- She retains control of the bench, authorizes a restricted evidence comparison, and accepts Lena's blinded topology-intervention protocol without returning operational authority to Evan.
Established continuity (Chapter 17)
- Nadia subjects the useful motor implementation to an externally mapped attribution study across independent code, hardware, topology, operator, and consequence-depth factors.
- She recognizes the result as distributed work by Marcus, Lin, the clean-room team, operators, and reviewers rather than personal vindication for Evan.
- She accepts independent change control and Evan's removal from operation while preserving the safer estimator and suspending institutional consequence gates.
Established continuity (Chapter 18)
- Nadia encounters a valid current governance history that makes the five-gate method an older corporate standard while the signed pilot slide still names Evan and repository history still shows the recovery team creating it.
- She does not invent a reconciliation. She retains the useful recovery and the consortium restrictions while stating only what the current record supports.