NP Nithin Palal

Arvind

The developer who works on the oldest code nobody else will touch.

Anything later stays hidden. The site also remembers the chapters you open on this device.
File AIPR-024Supporting · Everyman
Role
Developer at Priya's company since 2018
Work
At the company since 2018. Works on its oldest code, the parts nobody else wants to touch, and is nearly the only person who changes those modules.
First seen
Chapter 17
Appears in
2 of 54 pieces, and is spoken of in 1 more

What drives them

Wants

To know whether the platform is tracking his personal rate of introducing defects.

Needs

A promise from someone with authority over how the figures are used, and to be asked, and paid, when his knowledge is taken.

Stands to lose

His appraisal, his evenings, and the protection of being the one who knows the old code.

Strength

Careful. He asks his question carefully and checks more before every change.

The question their story asksIs he safer or more exposed once the company knows what he knows?

Everyman. He is the ordinary employee on whom the platform's numbers and the company's gains land.

The arc

FromThe sole owner of the oldest modules, slowed by numbers that feel like a verdict.
ToA man whose knowledge the company now holds without him.

His question leads to three changes and a written promise. Then a model is given his old code to explain, and he checks its account in his own evenings. The company becomes less fragile and he becomes more exposed.

The journey

  1. Tests and alliesChapter 17

    September 2025. He comes to Priya's desk and asks whether the platform tracks him. He has already begun running extra checks before every change, and his work has slowed.

  2. OrdealChapter 30

    March 2026. Priya's team gives a model his old code to explain. He is asked to check its explanations in his own hours. Nobody asked him first.

Choices under pressure

A person is what they choose when it costs them.

Chapter 17

The pull. Keep quiet and keep running extra checks, or ask the platform's builder directly.

The choice. He asks, carefully.

The cost. Her first answer does not settle it, and he thanks her and leaves.

He would rather know than guess, and he does not press.

What they learn

  • A number can feel like a verdict. Only someone with authority over its use can answer that fear. Chapter 17
  • One whole's redundancy can be one person's fragility. Writing down what you know is a fair request only where the institution rewards the person who shares it. Chapter 30

In the text

Nothing in the platform asked him to do this. The numbers felt like a verdict.

People

  • Priya Chandrancolleague; builder of the platform

    He comes to her with his question.

    She answers wrongly, then carries his question to Deepak without his name. Later her team's work leaves him more exposed.

  • Deepakdirector above him

    Deepak's written promise answers him. It has not yet met an appraisal round.

What they carry

Arvind is the person a well-meant system lands on. Through him the book shows that grouping figures does not hide a man who owns a module alone, and that a company can take knowledge out of a head in that person's own evenings and keep the gain.

Ideasredundancy

Look forThe oldest codeHis evenings

Where they appear

in the chapter spoken of absent

All characters →   Story map of AI-Proof →