NP Nithin Palal

Meera Reddy

An operations chief who maps every handoff and learns what maps miss.

Anything later stays hidden. The site also remembers the chapters you open on this device.
File AIPR-004Lead · Hero
Role
Vice-president of operations at NovaChem's Hyderabad site
Also called
Meera
Work
Vice-president of operations at the Hyderabad site of NovaChem Pharmaceuticals, a drug company with its head office in Basel. In 2023 she has worked there twelve years, the last four as vice-president.
Home
Hyderabad. Her office is on the seventh floor of the site in Genome Valley.
Family
Aunt of Diya
Habits
Draws how work moves through the site on her whiteboard in four marker colours: blue for data, green for decisions, red for failures, black for handoffs. Colleagues call them Meera maps.
First seen
Volume II
Appears in
16 of 54 pieces, and is spoken of in 1 more

What drives them

Wants

To deliver the AI work her managing director has asked for, and to make it run as cleanly as one of her maps.

Needs

To see that the people inside the work must be asked, that her own frames are a form of control, and that her signature is worth only the reading behind it.

Stands to lose

Her standing with Basel, her budget, the trust of about four hundred people, and the patients and applicants her signatures reach.

Strength

She sees systems whole, writes things down, and says what her own part was before anyone asks.

Flaw

She trusts structure. She solves problems with maps, forms, trackers and rules, and each one extends her control while she believes she is giving it away.

Wound

In 2023 she initialled a form for a hiring screen without asking what it measured. Nobody went back to the hundreds of applicants it turned away.

The question their story asksCan someone who answers for a whole site's machines keep her name honest when no one person can read everything she signs?

Hero. She holds real power and is tested, chapter after chapter, on whether she will use it to answer for harms she did not intend.

The arc

FromA controller who believes a correct map and a careful signature are enough.
ToA leader who signs few things and reads each in full, names what she cannot prove, and says whose decision each one is.

A chemist's sentence, 'not ours', starts Meera on three years of rebuilding. Each fix exposes the next gap: fit without voice, voice without someone who answers, freedom without a centre, fairness tests that miss where traits meet. She ends by admitting she has signed reviews she never read, setting terms she can keep, and defending a hand reading that keeps another person's signature meaningful.

The journey

  1. Ordinary worldChapter 16

    In March 2023 the managing director for India asks her to lead the site's AI work and wants something to show by the end of the year. She maps every department and approves four tools from four vendors.

  2. Inciting incidentChapter 16

    By September 2023 she knows the overlay has failed and says nothing for two months. In November Padma tells her in a corridor that the system is not wrong, it is just not theirs.

  3. Crossing the thresholdChapter 16

    She rebuilds the systems around the work and removes the hiring screen in July 2024. By 28 March 2025 everything connects, the teams comply and offer nothing, and she suspects the quiet is resignation.

  4. Tests and alliesChapter 18

    In April 2025 she gives each team three questions and four months to redesign its own work. Shalini asks who answers when a team's design goes wrong, and Meera has no answer. From August she puts one named person on every handoff.

  5. Tests and alliesChapter 19

    Basel's form asks for one of four futures for every role. She pencils 'will struggle' beside Usha Iyer's name, then asks each manager instead. In January 2026 Usha tells her she has not stopped controlling her managers, and Meera changes the terms.

  6. Tests and alliesChapter 19

    On a drug-safety model she asks whether all patients are being treated equally, takes the question to Basel, and proposes an independent governance team.

  7. MidpointChapter 30

    In January 2026 two sound decisions by two managers collide and a German distributor writes in fury. She finds the fault in what her own rules left out, names one person for customer dates and brings back a weekly meeting.

  8. OrdealChapter 31

    In late July 2026 Revathi's eleven pages show that the hiring system she signed for marks down applicants where three ordinary traits meet. She cannot stop it herself. She states her own part and asks for every rejected application in the overlap to be read again.

  9. OrdealChapter 31

    In September 2026, 123 letters go out with the plain sentence she asked for. She reads one, to a woman in Madurai, before the envelopes are sealed.

  10. CrisisChapter 36

    In February 2026 she takes her site's written practices to the plant near Lyon and the pilot fails. In Basel she tells Friedrich she can give others the questions and cannot give them the eyes, and admits she signed a review in March without reading it.

  11. ClimaxChapter 37

    In October 2026 she writes to the governance team, copied to Basel, that she will sign fewer reviews and read each in full. She spends an afternoon and two evening hours on a forty-page review, asks one question in the margin, and signs.

  12. ReturnEpilogue

    At the budget meeting the managing director asks whether the hand reading of one batch record in twenty can be automated. She answers that it can and should not be, says what she cannot prove, and says the decision is his.

Choices under pressure

A person is what they choose when it costs them.

Chapter 16

The pull. Protect a plan she approved and her superior announced, or admit it has failed.

The choice. She delays for two months, then rebuilds after Padma's remark.

The cost. A year spent on the failed overlay, and hours the chemists were never staffed to give.

She is honest in the end, and slow when honesty means reporting failure upward.

Chapter 19

The pull. Send Basel's form with her own judgement of each manager, or ask them first.

The choice. She holds the form back and sits with each manager. After Usha's sentence she loosens her tracker and says the new terms aloud.

The cost. Slower deviation closing in the monthly report to Basel.

She can hear that her care was control. Her pencil note proves wrong.

Chapter 31

The pull. The lawyers' fear of an admission and the absence of any legal duty, against people already turned away.

The choice. She tells the head of human resources what her own part was and asks for the re-reading and a plain sentence in the letters.

The cost. She owns that she walked less carefully than was possible. The filled posts cannot be given back and nearly four hundred people get no letter.

For her, knowing creates a debt to the people judged, whatever the law requires.

Chapter 36

The pull. Basel's plan to cut Shalini's team to about a third, against a forecast she cannot prove.

The choice. She argues from her map and pays from her own budget to keep the agents on routine calls for a year.

The cost. She cannot fund a second safety-report reviewer in 2027, so another team carries those hours. She may have eased a louder harm by accepting a quieter one.

She will spend her own resources on a judgement and name what the money will not buy.

Chapter 37

The pull. Keep her name on every review, which looks like care, or sign only what she can read.

The choice. She admits the unread signatures in writing and sets new terms.

The cost. Fewer signatures in Basel's report, a thinner planning calendar, and a change that goes live two days late.

She would sooner look less careful than sign what she has not read.

Epilogue

The pull. A saving the evidence supports, against a practice whose value she cannot prove.

The choice. She says the reading can be automated and should not be, and leaves the decision with the managing director.

The cost. If the reading stays, its hours are hers to explain month by month to Basel.

She separates what will work from what is right, and does not claim a decision that is not hers.

What they learn

  • Fit is not the same as being asked. A machine should go only as deep as the people who answer for the work can still see it, check it, refuse it and take it out. Chapter 16
  • Participation gives a voice and does not say who answers. Chapter 18
  • Asking people what they need inside a frame you still control is still control. The growing belongs to the one growing. Chapter 19
  • Good intentions settle a builder's motive and nothing about her debt. Knowing is where responsibility begins. Chapter 31
  • An organisation knows only what its people have learned is worth telling it. Chapter 36
  • A signature can carry only as much as the reading behind it. Chapter 37

In the text

She draws the workflows again. Every line is right. She has no colour for what is missing.

Are we treating all patients equally?

We are not required. But we know. And once you know, the choice is no longer between acting and not acting. It is between acting and choosing not to act.

I can give them the questions. I cannot give them the eyes.

“You can,” she says. “You should not.”

People

  • Padmachemist in the quality control laboratory

    Padma has tested medicines there since 2005 and seldom says what she thinks to vice-presidents.

    Her one sentence, 'not ours', becomes the measure Meera returns to for three years.

  • He hands her the AI work with a deadline and no budget for connecting systems.

    She delays telling him the overlay failed. His targets bound what her teams can change. At the end the budget decision on the hand reading is his, and he says he will think about it.

  • Shalinicustomer service director reporting to her

    Shalini asks who answers when her team's design goes wrong.

    Meera names her for the routing rule, argues her team's case in Basel and carries her request for a written account. The question still has no full answer.

  • Usha Iyerquality manager reporting to her

    Meera pencils 'will struggle' beside her name.

    Usha is the one who tells Meera what her tracker is. Meera gives her different terms, and the pencil note proves wrong.

  • Madhavi Krishnamurthyquality assurance manager reporting to her

    Meera has every unprovable flag Madhavi raises followed up for a quarter.

    Meera names her as operator of the batch-record system and defends the hand reading that keeps her able to sign.

  • Revathidata scientist on the site's governance team

    Revathi joins the governance team Meera proposed.

    Revathi brings her the finding about the hiring system and argues against stopping it. They disagree openly and each is half right.

  • Friedrichglobal chief executive in Basel

    He calls her to Basel to spread what Hyderabad has done.

    She tells him she cannot do it the way she did it at home and admits the unread signatures. He decides partly in her favour.

  • Isabelle Moreausite director at the plant near Lyon

    Meera brings her a finished document to pilot.

    After the pilot fails, Meera telephones and asks what Isabelle's people already notice, which leads to the night shift.

  • Diyaniece

    Watching Diya one afternoon, Meera sees she could not have shown the child how to look first.

What they carry

Meera carries the book's argument about organisations. A machine belongs in the work only when the people who answer for it were asked and can still see, check, refuse and remove it. Through her the book shows the problem of many hands: a builder answers for what she looked for and failed to look for, and a signature means only what was read behind it.

Ideasnot oursoverlayMeera mapsmany handsbuilderdeployerhuman in the loopfrom controller to cultivatorintelligent accountabilitythe one who answersoperator

Look forThe whiteboard and four marker colours (Meera maps)Her office on the seventh floorThe form with four boxes and the pencil note 'will struggle'The form she signed in June 2025The letter to MaduraiThe forty-page review and the question in its marginOne batch record in twenty, read by hand

Where they appear

in the chapter spoken of absent

  • Volume IIRecurring figure, first appearing in this volume.
  • Part IVHer company bolts four AI tools onto old processes, hears a chemist call them 'not ours', and rebuilds. Later she gets a form from head office with four futures for every role.
  • Chapter 16: Embed AI Deeply, Don’t Bolt It OnMaps every department, hires Mumbai consultants, and approves four tools from four vendors. Knows by September 2023 the overlay has failed but delays two months. After Padma's remark she rebuilds. Removes the hiring screen in July 2024. Audits every machine checkpoint in late 2024. Tries a procurement research agent in early 2025 but does not let it email suppliers or place orders. Starts worst-case and expert reviews, and writes down what stays unexplained.
  • Chapter 18: The AI-Native OrganisationIn April 2025 gives each team three questions and four months to redesign its own work. Approves Shalini's team's routing rule. From August 2025 adds one named person to every handoff.
  • Chapter 19: Rethinking Roles and StructureFills in the form in a week and pencils 'will struggle' beside Usha Iyer's name. Does not send it; sits with each manager in October 2025 and asks one question. Rebuilds the roles with a tracker. Tests Madhavi's flags for a quarter. After Usha's sentence gives her different terms, said out loud. Approves the analysts' training hours and writes down why. Moves two managers to technical posts and tells each herself. On the safety model asks 'Are we treating all patients equally?', takes it to Basel, and proposes an independent governance team.
  • Part VHer company is the case through which the laws for machines, as of October 2026, are mapped.
  • Chapter 25: Reading the Regulatory MapAsks which of the five the Act covers. Gives a model the text of Annex III and a page on each system; it finds none listed and flags the call-routing model as a hard case. Basel's lawyers agree in May. In October she writes Madhavi Krishnamurthy's name in the batch-record system's intended use and orders one batch record in twenty read by hand in full, with a monthly comparison, then sends the request to Basel.
  • Volume IIISigns for a hiring system, takes her site's practices to a plant near Lyon, and finds she has signed reviews she never read. Later reads about forty pages in full before she signs.
  • Part VIReads one letter before the envelopes are sealed. The search for the system's next bias is already running.
  • Chapter 30: Anti-Fragility in an AI WorldAfter a German distributor's furious email in January 2026, reads the record, finds no fault in either manager within the rules she wrote, writes to the distributor herself, and makes a new rule with one named person for customer dates and a weekly half-hour meeting for conflicts between teams.
  • Chapter 31: The Moral Responsibility of BuildersReads the eleven pages. Wants to stop the system at once but cannot. Tells the head of human resources, before anyone asks, what her own part was: she signed on tests of one trait at a time and did not ask about combinations. Asks for a re-reading of every rejected application in the overlap, and for one plain sentence to be added to the letters. Reads one letter, to a woman in Madurai, before the envelopes are sealed.
  • Part VIIIn February 2026 she takes her Hyderabad site's written practices to her company's plant near Lyon, where they fail.
  • Chapter 36: The Conscious OrganisationPresents the document at Lyon in February 2026. After the pilot fails, telephones Isabelle and asks what her people already notice. In Basel tells Friedrich she cannot do what he asks 'the way I did it in Hyderabad', gives the drug-safety example, confesses she signed a review in March without reading it, makes her two requests, and argues from her map against the voice-agent plan. Puts Shalini's request for a written account to Basel. Names in writing what the money for keeping the agents will not buy.
  • Part VIIISets new terms for what she will sign, then spends a whole afternoon and two hours of the evening reading one review in full before signing.
  • Chapter 37: The Amplified HumanWatches Diya in silence. In the week of 12 October writes to the governance team, copied to Basel, admitting what went wrong and setting new terms. Reads a forty-page review of the procurement agent's repeat-order change in full over an afternoon and two evening hours, finds no error, writes one margin question (who telephones the supplier when an order goes wrong), gets a written reply naming a buyer, and signs.
  • Chapter 40: What This Book Cannot Tell YouMentioned as an example in section 40.4.
  • EpilogueEarly in October names Madhavi Krishnamurthy as the system's operator and asks for the hand reading. At the mid-October budget meeting answers the managing director. Says what she cannot prove and what the reading cannot do. Says whose decision it is.

All characters →   Story map of AI-Proof →