NP Nithin Palal

Deepak

He runs the platform team at Priya's company.

Anything later stays hidden. The site also remembers the chapters you open on this device.
File AIPR-019Supporting · Threshold Guardian
Role
Director of platform engineering at Priya's company
Work
Runs the platform team at the software company where Priya works. Later chapters give his title as director of platform engineering.
Habits
Reads attendance as commitment.
First seen
Chapter 12
Appears in
3 of 54 pieces, and is spoken of in 1 more

What drives them

Wants

Reading: fast releases, correct figures, and visible commitment from the people around him.

Stands to lose

Release speed, and the trust of the engineers whose appraisals he controls.

Strength

He knows the records well enough to catch a wrong number from memory, and he writes down the promises that only he can keep.

Flaw

He reads attendance as commitment, and sets a limit nobody has justified.

The question their story asksWill the promise only he can make hold when the appraisals come?

Threshold Guardian. Priya's changes have to get past his scepticism, and his pushback is a check her notebook could not be.

The arc

FromA senior colleague who has not replied to her message.
ToThe sceptic who lets her try, with a condition attached.

Deepak stays what he is: exact, slow to agree, and senior. He catches Priya's error, makes the appraisal promise in writing, takes three weeks to accept her rotating approval and limits her review step to one day.

The journey

  1. Tests and alliesChapter 12

    February 2025. He interrupts Priya's third recommendation, points to page seven and gives the true defect escape rate for the payments module.

  2. MidpointChapter 17

    July 2025. He sends Priya two words, 'Check mobile'. Later he writes into the appraisal guidance that the platform's predictions will not be used to judge individuals, and writes a rule with the team on who may read the activity logs.

  3. ClimaxChapter 33

    2026. He takes three weeks to agree to the rotating approval, asks twice in August where Priya has been, and attaches a one-day limit to her review step.

Choices under pressure

A person is what they choose when it costs them.

Chapter 17

The pull. Leave Arvind's fear to a line on a screen, or bind himself in writing.

The choice. He writes the promise into the team's appraisal guidance, and a rule on the activity logs that only he may change, after telling the team.

The cost. He can now be held to it. In October 2025 it has not yet met an appraisal round.

He accepts that a promise about how figures are used belongs to the one with authority to keep it.

What they learn

  • A promise on a screen needs a rule behind it, made by the person who can keep it. Chapter 17
  • His one-day limit is itself a decision nobody has justified. A check that can find a harm and never delay a release is a report. Chapter 33

In the text

It was 4.1.

People

  • Priya Chandransenior colleague

    She asks him about a change his team is planning; he has not replied.

    He corrects her in front of the room, works with her on Arvind's question, and remains sceptical of her new work.

  • Arvinddirector above him

    His written promise answers Arvind's fear. Whether it will hold at appraisals is open.

What they carry

Deepak shows where authority sits in a company. Some answers are not the builder's to give: how figures are used in appraisals belongs to him. He is also the outside hearer the book says a person needs, someone who can refuse.

Ideasdefect escape rate

Look forPage sevenThe two-word message 'Check mobile'The appraisal guidance and the rule on the activity logs

Where they appear

in the chapter spoken of absent

  • Chapter 9: The Architect MindsetHas not replied to Priya's message.
  • Chapter 12: Becoming AI-LeveragedInterrupts Priya's third recommendation, points to page seven and gives the true figure
  • Chapter 17: Intelligence-Native ProductsOn a Wednesday in July 2025 sends Priya a two-word message. Later writes into the team's appraisal guidance that the platform's predictions will not be used to judge individuals, and writes a rule with the team on who may read activity logs, for what, how long they are kept, and that only he may change it after telling the team.
  • Chapter 33: A 12-Month TransformationTakes three weeks to agree to the rotating approval. In August asks twice where Priya has been. At the quarterly review calls her step another gate before every release, and attaches the condition that it add no more than a day to any release.

All characters →   Story map of AI-Proof →