InfraLoka AcademyPathwayAI
PathwayAI

Module 8 · You decide

People decide

4 min read5 min readReviewed 26 October 2026

In short

AI may prepare; people decide, especially about people, money, law and health. Deciding means really checking, not pressing approve. Record what the AI produced and what you checked.

After this lesson you can

  • Decide which decisions must be made by a person
  • Record the AI's part in a decision so it can be explained
  • Review an AI suggestion properly before approving it

Terms in this lesson

Understand

Throughout this course we keep returning to one principle: human in the loop. AI may read, summarise, draft, calculate and suggest. The decision stays with a person who can be held accountable. The question is, which decisions?

These decisions are always made by people:

  • About people: accepting or rejecting applicants, assessing performance, imposing sanctions, deciding who gets help or a service.
  • About money: approving payments, granting discounts, rejecting claims.
  • About law and health: interpreting rules for a real case, deciding on medical action.
  • That cannot be undone: public statements, official letters, deleting data.

In all of these, AI may help prepare material. But there is a subtle trap: once AI gives a neat, confident suggestion, we tend to approve it. This tendency is called automation bias, the habit of trusting a machine's suggestion over the evidence in front of us. It turns "human in the loop" into a human who only presses a button.

Real review has clear signs. You open the original data, not just the AI summary. You look for at least one reason against the suggestion. You can explain your decision to the person affected without the words "because the system said so". And you are genuinely ready to decide differently from the AI. If in a month you never once disagreed with the AI, that is not a sign the AI is perfect; it is a sign your review needs reviewing.

Decisions helped by AI need to be explainable, by you now and by a colleague six months from now. So record the AI's part briefly, in the same place as the decision record. Five lines are enough:

  1. Decision: what was decided, by whom, when.
  2. AI material: what the AI produced (summary, score, draft, suggestion) and which tool was used.
  3. Source data: what data the AI read, and whether it was masked.
  4. Human review: what you checked yourself and what you changed.
  5. Reason: why the decision is what it is, in your own words.

This record is a simple audit log. It helps when there is a question, an objection, or an error to trace. People's right to object to automated decisions is covered in the next lesson.

Be careful with what the record itself holds. Do not copy passwords, tokens or unneeded personal data into a log; write a reference to where that data is kept. A log full of secrets only moves the problem somewhere new.

The same principle applies when the worker is not a chatbot but an AI agent that can use tools and run several steps by itself. An agent may gather material, draft, even prepare actions, but decisions about people, money, law or health still stop at a person's desk. Design the agent to wait for approval at that point, to show what it is about to do and on what data, and to log each step. If an agent cannot explain what it will do before doing it, it is not ready to be given authority over such decisions.

Worked example

Before

The prompt

Here are three candidate summaries for the warehouse coordinator role. Who is the best fit? I will invite them straight away.

What came back

Candidate B is the best fit because their experience is most relevant and their leadership is strong. I suggest inviting Candidate B straight away.

After

The prompt

I am the recruiter for the warehouse coordinator role. The decision on whom to invite is mine. I need material to decide, not a ready choice. Criteria from the job description: (1) at least two years managing stock, (2) has led a team, (3) used to stock-recording systems. For each candidate (codes C-1 to C-3, data masked), make a table: criterion, evidence from the candidate's material with a short quote, and "no evidence" if the material does not mention it. Do not rank or recommend. [summaries of C-1, C-2, C-3]

What came back

C-1 | 2 years stock: "managed central warehouse stock since 2023" | Led a team: no evidence | Stock system: "used a daily stock-recording app" C-2 | 2 years stock: "4 years as inventory staff" | Led a team: "shift lead for 6 people" | Stock system: no evidence C-3 | ... Note: C-2's material does not mention a recording system; this can be asked at interview.

What changed

  • The first version gives a conclusion with no evidence you can check, and pushes you to act at once.
  • The decision is broken into criteria with quotes, so you do the weighing yourself.
  • "No evidence" does not mean "does not have": it is an interview question, not a reason to reject.

Common mistake

Mistake
Approving an AI suggestion about a person within seconds because "the AI already read all the data".
Why it hurts
In name a person decided, but in substance it was an automated decision. AI errors pass through uncaught, the people affected get no real consideration, and the organisation cannot explain the decision when asked.
Do this instead
Before approving: open the original data, find one reason against the suggestion, and write your reason in your own words. If there is no time to do that, postpone the decision.

Try

Sorting card

Who decides?

  1. Approving a discount for a large customer

  2. Giving an employee's final performance rating

  3. Formatting meeting minutes as bullet points

  4. Translating an internal notice into English for checking

  5. Grouping customer feedback by topic

  6. Deciding who goes through to interview

6 cards left

You rejected an expense claim after the AI flagged it "not in line with policy". Which record is most useful to trace later?

Take home

Before approving an AI suggestion

  • I know whether this is a decision about people, money, law or health
  • I opened the original data, not just the AI summary
  • I looked for at least one reason against the suggestion
  • I can explain this decision without saying "because the system said so"
  • The AI's part and my review are recorded, without secrets or unneeded data

What went wrong for us

How we work

Infrastructure plan files are not committed

Context
When infrastructure is managed as code, the tool writes plan files before changes are applied. They feel like temporary output.
What tends to go wrong
Plan files can hold the secrets fed to the tool, such as passwords and tokens, in plain text. If they are committed, those secrets enter the git history.
What it costs if ignored
Anyone who can read the repository, now or later, can read those secrets. Deleting the file in a later commit does not remove it from history.
Root cause
Git ignore patterns are written for files people already know about, and tool output is rarely inspected.
How we do it
Plan files are in the git ignore list and never committed. If a secret ever enters the history, we revoke and rotate it at once, then clean the history.
The rule we keep
Secrets are never written to files git tracks, and the ignore list covers all infrastructure tool output.

The lessonTool output can hold the secrets you fed in; check it before you store it.

What it means for your workOutput files and notes can hold passwords or personal data you once entered. Check what is in them before saving or sharing.