NP Nithin Palal

Priya Chandran

A test lead in Bengaluru whose name goes on work a machine did.

Anything later stays hidden. The site also remembers the chapters you open on this device.
File AIPR-001Lead · Hero
Role
QA lead of a twelve-person testing team at a software company in Koramangala
Also called
Priya, P. Chandran
Age
Not stated. She named her cat at twenty-two and has worked at this desk for eight years.
Work
Leads the twelve-person QA team at a software company in Koramangala, Bengaluru. Known for finding edge cases. Her annual reviews call her 'irreplaceable'.
Home
A flat she shares with her mother, within walking distance of the office through Koramangala.
Family
Her mother. A cat called Turing.
Habits
Keeps fourteen spreadsheets of edge cases and a personal wiki only she fully understands. Drew the whiteboard map of software failures that new hires call the Constellation. Calls her method 'thinking like a user who doesn't read instructions'.
First seen
Volume I
Appears in
20 of 54 pieces, and is spoken of in 8 more

What drives them

Wants

Proof that the word 'irreplaceable' still applies to her, now that a machine has done her team's week of testing in eleven minutes.

Needs

To stop resting who she is on being needed, and to answer in the open for what carries her name, where other people can see her acts and contradict her.

Stands to lose

Her standing, her sentence for who she is, and her name. If a release, a figure or the platform goes wrong, she is the one called into the meeting.

Strength

She notices. She catches her own fear, her own errors and her own pleading, says plainly what she can show and what she cannot prove, and writes against her own interest when the facts require it.

Flaw

She turns fear into work. Under pressure she takes tasks back into her own hands and argues, mostly to herself, that she cannot be removed.

Wound

For years her reviews praised her as 'irreplaceable', and she took her eye for the rare bug for herself. When a machine takes over the seeing, the loss feels like a loss of self.

The question their story asksCan she make what she signs truly hers, and stop needing to be indispensable?

Hero. She is the book's first running life: an ordinary employee who meets the machine first and has to learn, stage by stage, what answering for her work means.

The arc

FromA tester who notices her fear for three seconds, runs from it, and signs a release she could not check.
ToA platform lead who gives away her approvals and her planning, writes her questions down for others, and catches herself mid-sentence still pleading her own case.

Priya moves from hunting bugs to keeping a page of decisions, asking what work is for, checking what carries her name, and answering for what her platform teaches the people who use it. The title 'architect' brings a seat in some rooms and a new fear, because a machine follows her into the new work too. Her story stops in October 2026 on a doubt: she cannot tell whether she has changed or only learned which word to leave out.

The journey

  1. Ordinary worldChapter 1

    October 2024. Priya leads twelve testers in Koramangala and is the one who finds the edge cases others miss. Her reviews call her 'irreplaceable'.

  2. Inciting incidentChapter 1

    An AI testing system runs a week of her team's work in eleven minutes and finds three bugs they would have missed. She notices her fear for about three seconds, then turns away and hunts for a mistake in the machine's report. At five she types her name on a release she could not check.

  3. RefusalChapter 5

    For three weeks she opens all fourteen spreadsheets every morning, compares them with the machine's findings and finds no difference. She knows the ritual is empty and works harder so as not to feel it.

  4. Crossing the thresholdChapter 5

    On a Thursday she leaves the spreadsheets closed and writes a page of five decisions she made that week, with her reasons. Her question changes from what she is for to what the work needs that the machine cannot sign.

  5. Tests and alliesChapter 9

    She rewrites her task list as questions, then spends two weeks redesigning the tests for Module 7. In a corridor in January 2025 Anand tells her the module is being retired. She begins writing one question on a card every Monday.

  6. Tests and alliesChapter 12

    February 2025. Deepak corrects a figure on page seven of her review in front of eight people. She had checked her recommendations line by line and read the machine-filled tables under them only once.

  7. MidpointChapter 17

    Her platform has taught the mobile team to acknowledge findings in four seconds. Her first fix, imposed without asking, fails. She sits with the team and builds a better one with them. In October 2025 the chief product officer offers her a post titled 'Architect', and she says yes.

  8. OrdealChapter 29

    At a family lunch she cannot say what she does. She fills her evenings with work nobody asked for. In December she evaluates a vendor's agent that can do much of her new job, and signs that it is good enough for most new products.

  9. CrisisChapter 30

    March 2026. Her cousin Naveen, a manual tester let go after twelve years, asks whether her company is hiring. She tells him it is not, and why. When she starts to call his poor offer a chance, he stops her, and she listens.

  10. Tests and alliesChapter 32

    Late May 2026. In a triage meeting she pauses for about four seconds and asks a question instead of ruling. A junior engineer's evidence is heard, the grading rule is changed, and Priya reports the fault to the chief product officer under her own name.

  11. ClimaxChapter 33

    Reading her notebook in June 2026 she finds 'indispensable' nine times and writes that she has been lying to it. She gives away the monthly approvals and the planning cycle, writes her review questions on one page, and proposes a step that should not need her.

  12. AftermathChapter 33

    11 October 2026. She begins a sentence defending how much she has changed, hears it pleading her case, and leaves it without a full stop. The trial she leads has eleven weeks to run.

Choices under pressure

A person is what they choose when it costs them.

Chapter 1

The pull. Leave the sign-off empty with no bug to show and no time before Thursday, or put her name on a release she could not check.

The choice. She nods to Rashmi, types her name and submits.

The cost. Her signature no longer means 'I checked'. If a fourth bug ships she will be called to explain, and she could not say what she approved.

She can notice that a decision is hers without yet being able to make it hers. She has no way to refuse and say why.

Chapter 5

The pull. The warm ritual of the spreadsheets, which says her catalogue still matters, against a blank page that may show what her work really is.

The choice. She leaves the spreadsheets closed and writes down five decisions and her reasons, including an hour she wasted doubting a machine rating that was right.

The cost. She learns that some of her judgement is weaker than she thought. Nobody asked for the page and nobody will read it.

Offered comfort or an honest account, she can choose the account.

Chapter 17

The pull. Arvind asks whether the platform is tracking him. She can reassure him herself, read the activity logs to see who else is afraid, or take the question to the person with authority to answer it.

The choice. After a first wrong answer she opens the logs and closes them again. She raises his question, without his name, at a meeting with Deepak in the room.

The cost. She has to see that her first answer was not quite true and that the promise was never hers to make.

She knows where her own authority ends, and she will not watch people to learn whether they fear being watched.

Chapter 29

The pull. A vendor's agent can do much of the work her new post consists of. She can write what protects the post or what she found.

The choice. She writes that the agent is good enough for most new products, and signs it.

The cost. Her name is on the case against her own post. Whether to buy it stays with the chief product officer.

When honesty and self-interest part, her signature now follows what she found.

Chapter 30

The pull. Comfort her cousin with the story of her own growth, or respect a loss that tools like hers helped to cause.

The choice. She stops when he objects, tells him only what she has seen, and does not tell him what to do.

The cost. She cannot help him, and she has to accept that her own growth was partly lent and partly luck.

She will not use her success as proof of anything about another person's harm.

Chapter 33

The pull. Keep the approvals and the planning cycle that make her necessary, or give them away and let others do them worse at first.

The choice. She proposes that monthly approval rotate among four leads, hands the planning cycle to a test engineer and stays out of his first meeting. In October she lets his change to her template stand.

The cost. Each approval takes two days longer. His first cycle is late and misses a dependency. Deepak asks twice where she has been. The freed hours fill with work that makes her needed again.

She trusts acts that others can see and contradict more than her own verdict on herself.

What they learn

  • Noticing that a decision is yours does not make it yours. A signature is ownership only if the one who signs could have left the field empty and said why. Chapter 1
  • A machine makes you faster at anything, including the wrong thing. Asking the architect's question does not give you a seat in the room where the purpose is decided. Chapter 9
  • Smoothness is not accuracy. A number in a shared report is a claim that carries your name, and it is checked only when you know what it is a number of. Chapter 12
  • A product that learns from people also teaches them. A habit built into someone else's screen is a rule about their hours, and its builder answers for it. Chapter 17
  • Being the one who answers for something is not being the only one who could. A notebook can find the plea. Only acts that others can see and contradict can check it. Chapter 33

In the text

If this works this well, what do they need me for?

What does the work need that the machine cannot sign?

The green dashboard did not teach her this. The wrong number did.

She was trying to solve a feeling with a system.

I have been lying to this notebook.

People

  • Rashmiher manager

    Friendly and enthusiastic. Rashmi asks for the sign-off and Priya nods without asking what 'higher-level work' means.

    Rashmi praises two weeks of work on a retired module, later agrees to Priya's handover of the planning cycle and warns her about Deepak.

  • Priya's mothermother; they share the flat

    They live together in Koramangala.

    Her mother answers for her at lunch: 'She is an architect now.' Priya notices her silence at dinner only when she writes it down. Her mother's patience is named among the things Priya's year runs on.

  • Deepaksenior colleague, later named as director of platform engineering

    She messages him with a question about a change his team is planning. He has not replied.

    He corrects her wrong figure in front of the room, alerts her to the mobile team, makes the appraisal promise only he can make, and stays the sceptic who attaches a one-day limit to her review step.

  • Sends her the email with the subject line 'Architect'.

    Approves her study for one year, not three, and her review trial for one quarter. Holds the decisions she reports to: the vendor's agent and the five unrepaired bugs.

  • Arvindcolleague who works on the oldest code

    He comes to her desk to ask whether the platform is tracking him.

    Her first answer is wrong; she takes his question to Deepak. Later her team's work on his old code leaves him more exposed.

  • Naveencousin, her mother's sister's son

    He asks whether her company is hiring testers.

    He tells her she was lucky and refuses to be told his loss is a chance. She listens and leaves the choice with him.

  • Anandcolleague, lead developer on the payments team

    He tells her, apologetically, that Module 7 is being retired, assuming she knew.

  • Lavanyaproduct manager who asks for her help

    Lavanya asks her to look at three machine-written versions of a feature.

    Priya says what she can show and cannot prove. The choice, and its explanation, stay Lavanya's.

  • the test engineermember of her old team

    He has never run a planning cycle, because she always ran it.

    She hands him the cycle and her templates. His first cycle is late; in October he changes one template and she lets it stand.

What they carry

Priya carries the book's opening claim and its later correction. Her three seconds of noticing are what Chapter 1 calls consciousness, and the book shows through her that noticing is not owning: an act is hers only when she can explain it, undo it and repair it. Each later chapter tests a comfort on her in turn: the page of decisions, the architect's question, checking what carries her name, the new title, the notebook. The book lets her grow, says her growth was partly lent, and ends her story on a doubt so that no reader takes her career as proof.

Ideasconsciousnessthe delaymoral crumple zonesign-offedge caseritual of relevancearchitectsleep testtrust ladderready-to-handintelligence-nativefeedback loopselective difficultyconfidence surfacesfear wearing the clothes of competenceslackawareness auditkey-person riskcourt of one

Look forThe green dashboardThe Constellation, her whiteboard map of the ways software failsFourteen spreadsheets and a private wikiTuring, the cat she named at twenty-twoThe page of decisions, first saved as 'Decisions: week of October 21'The Monday card: 'What would make this week's work pointless?'The sleep testThe list on her laptop, its first item unchanged since August 2025The ruled paper notebook with 'What did I notice today?' on the first page

Where they appear

in the chapter spoken of absent

  • Volume IWatches her own fear for about three seconds. That evening she signs a release she could not check.
  • Part IThe chapter asks what happened in her in the three seconds after a machine did her team's week of testing.
  • Chapter 1: The Observer Behind Your EyesNotices her fear for about three seconds, then turns away from it. Spends the morning looking for a missed bug and the afternoon writing up edge cases the machine already listed. At five she types her name in the 'Approved by' field and presses submit.
  • Chapter 2: The Ancient KnowingNo new action. The chapter rereads her signature: she superimposed a function on herself; she intended to sign; she gave her assent without testing the impression.
  • Chapter 3: The Qualities of the Conscious SelfNo new action.
  • Chapter 4: Why This Matters NowNo new action.
  • Chapter 5: When Intelligence Became CheapOn a Thursday morning, three weeks and two days after the dashboard turned green, she does not open the spreadsheets. She writes five decisions from the week with her reasons: an escalated payment-module bug; a reply to a client in Pune to which she added a ship date and her own name; a slowdown she let pass; a cluster of small failures she flagged to a senior engineer; and an hour wasted doubting a 'low risk' rating that was right. Saves it as 'Decisions: week of October 21'. Next morning adds Thursday's two.
  • Chapter 7: What AI Cannot ReplaceMentioned only, as an example of an empty position.
  • Part IIISpends two weeks on an excellent design for a retired module. Now writes one question on a card every Monday, which leads her to send one message. In Chapter 12 she checks every recommendation in a report and none of the numbers under them.
  • Chapter 9: The Architect MindsetIn November 2024 rewrites her task list as questions and persuades Rashmi to replace the quarterly report with a page of decisions. In late December redesigns the Module 7 tests with her team and the machine. When Anand tells her, she thanks him, goes to her desk and does not open her laptop. Three weeks later sends a message to Deepak about a planned platform change before her first meeting.
  • Chapter 10: Building Deep Human CapitalMentioned only.
  • Chapter 11: The Skill That CompoundsIn January 2025 she settles on the sleep test: minor false alarms and test ordering go to the system; whether a critical module is safe to release is hers
  • Chapter 12: Becoming AI-LeveragedFinishes the report at eight forty-seven for a nine o'clock deadline. In the ten o'clock meeting Deepak corrects the payments defect escape rate from 2.3 to 4.1 per cent. She corrects it on the spot. In the following weeks she forms her own view first, checks claims that carry her name, and adds a second question to the sleep test.
  • Volume IIRecurring figure.
  • Part IVSubject of Chapter 17, summarised here.
  • Chapter 14: The Commodity TrapRecalled from Chapter 9: she spent two weeks redesigning tests for a part of the product about to be retired
  • Chapter 16: Embed AI Deeply, Don’t Bolt It OnMentioned only, unnamed here.
  • Chapter 17: Intelligence-Native ProductsReads the review log and finds the four-second clicks. Builds a mandatory review box over a weekend and imposes it without asking; it fails. Switches it off, sits an hour with the mobile team, and builds selective difficulty with them. Redesigns prediction screens. Gives Arvind a wrong answer, sees why the next morning, decides not to read people's activity logs, and raises his question at a meeting with Deepak present. Says yes to the 'Architect' post.
  • Chapter 20: Intellectual Property in the Age of ConsciousnessKept a page of decisions in Chapter 5.
  • Chapter 21: Think in Decades, Build in WeeksIn February 2026 asks herself where she will be in ten years. Writes two pages to the chief product officer proposing a three-year study of volunteers from three teams, tested quarterly without the platform, with pooled results and managers kept from individual scores. Takes the pages to the infrastructure team first.
  • Volume IIILeaves a sentence in her notebook without a full stop.
  • Part VIMeets her cousin Naveen at a cafe. Buys a notebook. Pauses for four seconds in a meeting about her own machine's mistake.
  • Chapter 29: Fear, Ego, and ObsolescenceAt a November 2025 lunch says 'Of testing' and does not explain. In the weeks after, reads many more platform findings in the evenings, joins every review and rewrites finished documents. In December evaluates the vendor's agent and writes, against her interest, that it is good enough for most new products, and signs it. In January 2026 sees that nothing on her list is the thing she fears. At the January lunch says a sentence a machine wrote for her.
  • Chapter 30: Anti-Fragility in an AI WorldTells Naveen honestly that her company is not hiring and why. Her team gives a model Arvind's old code to explain. In April begins to say his offer might be a chance, stops when he objects, tells him only what she has seen, and does not tell him what to do.
  • Chapter 32: The Examined Life in the Age of MachinesKeeps the notebook on paper, for nobody. In late May 2026 pauses about four seconds in a triage meeting and asks a question instead of ruling. That week, with the team's lead, changes the grading rule and writes a note to the chief product officer under her own name saying what the platform had learned, from whose decisions, and for how long.
  • Part VIIGives away the planning and the approvals she had kept.
  • Chapter 33: A 12-Month TransformationRuns the hourly audit in the first week of May. In June finds 'indispensable' nine times in her notebook and writes that she has been lying to it. Proposes to Deepak that retraining approval rotate among four leads. Hands the quarterly planning cycle to a test engineer and stays out of his first meeting; stops attending two weekly status meetings. In August reviews three versions of a feature for Lavanya and spots that the best-scoring one assumes a user who finishes in one sitting; two days later tests her own claim by giving a model the tickets, and it finds the pattern in minutes. Offers teams an hour on feature assumptions, then writes her questions on one page so others can ask them. Presents three pages at the quarterly review and accepts the lead of the trial. In October lets the engineer's change to her template stand after saying once that she thought it worse.
  • Chapter 40: What This Book Cannot Tell YouNotices her fear for perhaps three seconds, then opens her spreadsheets and spends the morning hunting for a mistake in the machine's work. The text says: in other words, she ran.

All characters →   Story map of AI-Proof →