Glossary: the vocabulary of The Amplifier

The Amplifier

A person who uses AI to extend what they already do well while staying in charge of the thinking. Not someone who is good at AI — someone who thinks clearly and uses AI inside that clarity. Also the title of the book and the name of the framework.

The Dependent

A person who outsources their thinking to AI: asks the tool, accepts the answer, ships the output. Looks productive, cannot defend the work, and does not notice until the questions get hard.

The Avoider

A person who refuses to engage with AI, usually from a real value — craft, quality, ethics — that has hardened into a reflex. Keeps the self intact and loses relevance; with authority, imposes the cost on everyone underneath.

The Dependency Trap

The mechanism by which dependency forms: one good outcome at a time, with a fast praise loop and no negative signal, until the tool is the default and the thinking comes second, if at all.

The Avoidance Trap

The mechanism by which a valid first refusal becomes a permanent posture. The person still feels they are protecting the original value; they have calcified around it.

The asymmetry

The Dependent hollows the self and the damage is contained. The Avoider, given any authority, hollows the world around them — their team, students, reports. Avoidance alone is a personal choice; with anyone reporting to you it becomes a tax on everyone underneath.

The Amplifier Framework

The book's eight-step method for integrating AI into any task: Define the End State, Map the Flow, Assign Tasks, Select the Tool, Prepare and Direct, Execute, Evaluate, Integrate and Stress-Test. Named only this way — no acronym.

End State

Step 1. What success looks like, written alone, without AI, in paragraphs not bullets, with the audiences named specifically and the texture of the outcome described. The one step nobody else can do for you.

Map the Flow

Step 2, in three phases: you list and sequence the tasks yourself (A), AI reviews the list for gaps (B), and you brainstorm each gap before deciding (C). Human leads, AI validates, human decides.

The Decision Filter

The four questions of Step 3 for assigning a task to a human or to AI: Does it need context only in your head? Is the output verifiable? Is it generating options or choosing between them? Is the cost of being wrong high or low? Mixed answers mean the task is too coarse — decompose it.

Tool Selection Logic

The five characteristics of Step 4: nature of input and output, context requirement, conversation or single output, accuracy requirement, and frequency. Categories matter more than brand names.

Two-step prompting

Step 5's method: brief the AI in plain language as you would a smart new colleague, then ask it to turn your briefing into an optimised prompt and use that. You bring clarity; the tool brings technical optimisation. Amplification, not prompt engineering.

Success criteria

The standard you write down before you see any output, so that polish cannot seduce you into calling something good. The Dependent's missing muscle.

Small fix

A local, self-contained correction that breaks nothing else: a renamed function, a typo, a missing buffer. You spot it, you fix it, you move on.

Structural problem

A problem where fixing one thing cascades into others. Patching does not work; you trace it back to the step where it was born — often Step 1 (end state too vague), Step 2 or 3 (the plan conflicts with itself), Step 4 or 5 (wrong tool or poor direction).

The Amplifier Stack

The three-layer model for mid-career professionals: domain expertise at the bottom (years to build, irreplaceable), AI fluency in the middle (months if the foundation exists), human skills on top (judgement, taste, ethics, relationships — the differentiator). Don't reinvent; stack.

Shadow versus capacity

In education, the grade is a shadow of the underlying capacity. When the shadow can be produced without the capacity — when AI can write the assignment — the system breaks, and the student must build their own signal.

Tutor, not substitute

The student's version of amplification: ask AI to teach you how, not to do it for you. Use it to make the climb faster, not to skip the climb.

The intern, not the artist

Kavya's line: hand the tool the drowning — budgets, research, schedules, first drafts — and keep the art. The difference between the people who use these tools well and the people who get used by them.

The girl at the gate

Kavya's end state for her festival: one specific person, walking out of the college gate on the last night, thinking there might be a place in here for her too. Everything else was in service of that.

Changing or just moving

Vivek's first question to Arjun at the coffee machine. Trying is not the same as changing.

AMQ (Amplifier Quotient)

The free self-assessment on this site. Places you in a category (Dependent, Avoider, Amplifier) and a band within it, names the risks that travel with your placement, and gives a roadmap. Descriptive, not prescriptive; designed to be retaken every six months.

Band

One of three positions within each AMQ category. For the Dependent and the Avoider, bands track depth of the trap (Drifter, Habitual, Convinced; Postponer, Principled, Structural). For the Amplifier, bands track maturity of practice (Apprentice, Practitioner, Mentor).

Named risk

A specific hazard the AMQ attaches to a placement — for example the Avoider Shadow, the Convert's Risk, or Framework as Friction for a new Amplifier. Two or three are shown; you work on one at a time.

The Convert's Risk

The recently arrived Amplifier's temptation to evangelise — to see Dependents and Avoiders everywhere and offer the framework to people who have not asked. The discipline is to wait to be asked.

Passing it on

The book's closing thesis. The framework was given to Arjun by a stranger; he gives it to his sister; one day she will give it to someone at a coffee machine. Not a promotion — a debt payable only forward.

Terminology first published in The Amplifier by Nandan Gijare, 2026. "The Amplifier Framework" is the only name for the framework; it has no acronym.