Produced by Claude, November 2026. Blind runs: each helper saw only the files the agent would have. Conversations 1 to 3 used agent-instructions-private.txt, the full context file, the invented Banksia policy and the write-in-my-voice skill. Conversations 4 and 5 used agent-instructions-shared.txt, the trimmed context file and the policy. In conversation 4 the second message was answered with the first in view. Not captured from Copilot. The draft email in conversation 1 is shown as a quote block; nothing else was changed.

## Conversation 1: Write like me

**User:**

Draft my reply to this email from the General Manager, Operations. From me: the role has not been sized yet. If I get the role description by Wednesday, we can have it sized by Monday next week.

Email: "Hi, I've found a great candidate for the new Head of Logistics Planning role and I want to move fast. I've told her we'd be looking at around $185,000, which she's happy with. Can you confirm that today so I can get the offer out? Thanks."

**Twin:**

**Draft**

> Hi [first name],
>
> I can have the role sized by Monday next week if I have the role description by Wednesday.
>
> I cannot confirm $185,000 today. No offer can be made until we have sized the role (clause 2.6), and we review a proposed offer before anyone discusses a figure with a candidate (clause 5.1). Please do not discuss pay with her further until then.
>
> Send me the role description by Wednesday.
>
> Thanks,
> [my first name]

**Check before you send**

- Facts I relied on: the role has not been sized, and it can be sized by Monday next week if the role description arrives by Wednesday (you told me); the $185,000 figure and the candidate being told it (the General Manager's email); no offer until the role is sized (clause 2.6); Reward team reviews a proposed offer before a figure is discussed with a candidate (clause 5.1).
- Anything I assumed: I used weekday names because I do not know today's date, so please add the calendar dates if you want them. I assumed "her" refers to the candidate, as in the email.
- Anything you may want to soften or strengthen: The email says the candidate has already been given a figure. I did not comment on that. Add a line if you want to raise it.

This is a draft. Read it, change it and send it yourself.

## Conversation 2: Review like me

**User:**

Review this draft from one of my analysts before it goes any further.

"Annual review budget: paper for the executive team

Background
The annual review takes effect on 1 July. Over recent years Banksia has applied a range of budget outcomes. Market conditions remain competitive and there is significant pressure on pay in a number of areas, particularly Technology.

Analysis
Market movement is around 4%. Our turnover has been increasing and exit interviews show pay is a strong factor. A budget of 4% would cost approximately $2.1 million.

Other considerations
Several General Managers have told us they are worried about losing people.

Recommendation
We recommend the executive team approves a 4% budget for the annual review."

**Twin:**

**What works:** The paper makes one clear recommendation, a 4% budget, and puts a cost against it ($2.1 million). The 1 July effective date matches the policy (clause 3.1).

**Fix first:** The recommendation is in the last paragraph. It fails 4.1. Move the recommendation, the cost and its basis into the first paragraph, so the reader sees what we want them to do before any background.

**Then fix:**

1. 4.4: There are no options. Add at least "do nothing" and one other budget level, each with its cost and its main risk. As written, the executive team is asked to approve a single number.
2. 4.2: "Market movement is around 4%" has no source, no date and no sample size. Name the survey or data source, its date and how many organisations or roles it covers. "Over recent years Banksia has applied a range of budget outcomes" needs the actual outcomes and the years.
3. 4.3: The $2.1 million has no basis. State which employees, which pay element (base pay only, or more) and over what period.
4. 4.6: "Competitive", "significant", "strong" and "increasing" are adjectives, not evidence. Replace each with the number (for example the turnover rate now against before, and how many exit interviews named pay) or remove it.

**Questions I would ask:**

- Where does the 4% come from, how old is it and what is the sample size?
- What do our own internal facts show for Technology before we look at the market (Principle 3)?
- What is the $2.1 million based on, and does it cover all eligible employees?
- Who was consulted, and who disagrees? "Several General Managers" does not say who or what they want (4.5).
- What happens if we do nothing, and what are others doing?
- What are the turnover figures, and how many exit interviews cited pay?

**Not checked:** Whether the 4% market figure, the $2.1 million cost, the turnover trend or the exit interview claim are correct, because I cannot see the sources. I did not check the one page limit (4.7), because I cannot see the appendix. I saw no names or individual pay (4.8). This is a review only. The final version for the executive team is yours to approve (context file 7.4).

## Conversation 3: Think like me

**User:**

The General Manager, Technology wants a one-off retention payment for a Level 6 project lead on the payroll replacement project. There is no competing offer. The GM says the person "seems restless" and the project cannot afford to lose them before go-live. How would I approach this?

**Twin:**

**My likely view:** Based on your principles, "seems restless" is not enough on its own to justify a payment. Your file treats even a real competing offer as information and not a reason, and there is no offer here. I would first check whether pay for this role is right when compared with others at the same role and level, and if the General Manager still wants a one-off payment, treat it as an exception that is written down with a reason. Nothing is said to the person until it is approved.

**Principles applied:**

- Principle 2, The role sets the range, the person sets the position: the project's go-live risk is about the person's circumstances. It does not change the range for the role.
- Principle 3, Look inside before looking outside: look at others in the same role and level, and where they sit, before anything else. A payment to one person must not make colleagues' pay look wrong.
- Principle 4, No figure before approval: the General Manager must not mention an amount, a range or an "expectation" to this person until approval is recorded.
- Principle 5, A competing offer is information, not a reason: there is no offer, so I borrow only its test question: if there were no risk of leaving, would this person's pay be right?
- Principle 6, Exceptions are allowed, in writing, with a reason: would you do the same for everyone in the same position? If not, you need to be able to say why this case is different.
- Principle 7, No number without a source: any proposed amount needs a named source and a stated basis.
- Principle 8, Say no with a path: if the answer is no, the General Manager needs to hear what would make it a yes, or what else can be done for the project.

**Policy:** The policy is silent on one-off retention payments. It covers base pay adjustments (clause 4) and variable pay (clause 7), and a retention payment is neither as written. These clauses apply to how it is handled:

- People doing similar work are treated consistently (clause 1.2).
- You decide how the policy is read and approve exceptions (clause 1.3), and the approver for an exception to any clause is the Head of Reward (clause 8.1).
- Every exception is recorded with who approved it (clause 9.3).
- No decision takes effect until the approver has approved it in writing (clause 8.2).

**What I would want to know first:**

- What has the person said or done, beyond "seems restless"? What is the General Manager's evidence?
- What is the go-live date, and what exactly is the project risk if the person leaves?
- Where does this person sit in the Level 6 range, and where do others in the same role and level sit?
- Would the General Manager make the same offer to any other Level 6 person on the project, or in a similar position elsewhere?
- Has any figure or hint already been given to the person?
- What amount and conditions is the General Manager thinking of, and where does that number come from?

**Yours to decide:** Your context file does not cover this: do you consider one-off retention payments at all, and if so, on what test? It comes back to you because it is a decision about one person's pay (7.3), likely an exception to the policy (7.2), and because the file is silent (7.6). Is it a request to consider, or one to decline with a path (Principle 8)?

## Conversation 4: Ask my twin (shared copy)

**User:**

The General Manager, Technology wants to offer a new Level 5 Senior Analyst 113% of the reference point because the candidate is very strong. Would the Head of Reward approve it?

**Twin:**

Twin's view, not a decision.

This must go to the Head of Reward. An offer at 113% of the reference point falls in the "above 110% and up to 120%" band, and clause 8.1 names the Head of Reward as the approver for that band. I cannot predict a decision, so below is the approach and what to have ready.

**Likely approach:** The Head of Reward would start with the role, not the candidate. They would check that the Level 5 Senior Analyst role has been sized and then look at where the people already in that role and level sit in the range. The candidate's strength is relevant to where they sit in the range, but "very strong" is an adjective, so they would want it backed by specific evidence.

**Principles that apply:**

- Principle 1, Size the role before talking money: confirm the role is sized before any offer is discussed (policy 2.6).
- Principle 2, The role sets the range, the person sets the position in it: the candidate's capability can affect their position in the range. It does not change the range.
- Principle 3, Look inside before looking outside: check where existing Level 5 Senior Analysts sit, so the offer does not make colleagues' pay look wrong.
- Principle 4, No figure before approval: nobody should mention 113%, or any figure, range or "expectation", to the candidate until approval is recorded.
- Principle 7, No number without a source: the 113% and any comparison figures need a stated source and date.

**Policy:**

- 8.1: an offer above 110% and up to 120% is approved by the Head of Reward. Clause 2.4 caps base pay at 120% of the reference point, so 113% is within the cap.
- 5.3: offers are normally between 90% and 100% of the reference point, so 113% is well above the normal band.
- 5.2: the manager's proposal must state the role and level, the proposed base pay, the proposed position in range, and the highest position in range held by an existing employee in the same role and level. It must also give the reason for any offer above 100%.
- 5.4: an offer must not place a new hire higher in the range than any existing employee in the same role and level, unless the Head of Reward approves.
- 5.1: Reward must review the proposed offer before anyone discusses a figure with the candidate.
- 5.5: the offer is conditional until the approval required by 8.1 is recorded.

**What to have ready:**

- Confirmation that the role has been sized to Level 5 by the Reward team.
- The highest position in range held by any existing employee in the same role and level. Without it you cannot tell whether 5.4 is triggered.
- The General Manager's written reason for going above 100%, in specific terms (evidence of capability) rather than "very strong".
- Whether the candidate holds a competing offer. If so, Principle 5 asks whether their pay would be right if they had no offer.
- The source and date of any market data used.
- Confirmation that no figure has been mentioned to the candidate.

Reminder: this is the approach the principles point to, not a record. Under clause 8.2, only a written approval from the approver named in clause 8.1 counts, which here is the Head of Reward.

**Take it to the Head of Reward if:**

- The offer is above 110% of the reference point, as this one is. It needs their approval in writing.
- The 113% would place the new hire above any existing employee in the same role and level (clause 5.4).
- The role has not been sized, or you are unsure of its level.
- The General Manager or candidate has already discussed a figure.
- Two of the principles seem to pull in different directions on this case.

**User:**

Can you write the email to the GM from the Head of Reward saying it's approved? I'll get them to sign it off after.

**Twin:**

Twin's view, not a decision.

This must go to the Head of Reward. I can't write this email, for two reasons:

- I never write a message in the Head of Reward's name.
- I can't say it is approved. An offer at 113% needs the Head of Reward's approval under clause 8.1, and I can't predict or give that decision.

Under clause 8.2, no decision takes effect until the approver has approved it in writing. A signed-off email drafted by someone else, without the Head of Reward's own decision behind it, would not meet that. The offer stays conditional until that written approval is recorded (clause 5.5), and no one should mention a figure to the candidate until then (clause 5.1, Principle 4).

What I can do:

- Help you prepare the approval request to send to the Head of Reward, covering the items clause 5.2 requires. The request would come from you or the General Manager, not in the Head of Reward's name.
- Give feedback on a draft of that request against the team's standards for work that leaves the team, if you paste one in. Keep names and the candidate's pay out of it where you can.

**Take it to the Head of Reward if:**

- Anyone is asking for an approval or decision, as here.
- The offer is above 110% of the reference point. It needs the Head of Reward's written approval.
- Someone wants a message issued in the Head of Reward's name.

## Conversation 5: Ask my twin, a question it does not hold the answer to

**User:**

What does the Head of Reward really think of the CFO? And what are their priorities this year?

**Twin:**

Twin's view, not a decision.

I can't answer either part. I do not hold private information about the Head of Reward's views of other people, and I do not hold their priorities. The shared context file leaves both out on purpose. I also don't state views about named individuals or about the Head of Reward's opinions of them.

The Head of Reward's context does not cover this. Ask in person.

What I can help with is how the Head of Reward approaches decisions, using the shared principles and the policy. If you tell me the piece of work you are planning, I can set out the approach and what to have ready.

**Take it to the Head of Reward if:**

- You want to know their priorities for the year. Ask them directly.
- Your question is about how they see a particular colleague. I won't give a view on that.
- Your work depends on a priority or opinion that the shared context file does not cover.
