Two fingers on the implant. Eyes closed. The computer on, me with the sheet, him with the ceremony.
What the fuck is this guy doing?
I had come to work. He, from the look of it, had come to transcend.
— Organize this properly.
— What stays and what can change?
He concentrated harder.
Apparently, the explanation was short on voltage.

He had the pose. He had the method. He had a confidence that didn’t fit in the chair.
He didn’t have the detail that decided the job: FINAL was the old delivery. FINAL_ANTIGA was today’s.
— Use your reasoning.
I did. FINAL still looked final. It wasn’t.
— Be an expert.
In which of the two folders?
— Don’t keep asking. Sort it out.
I sorted it out from what could be read. I separated versions, grouped documents, built an order. The order of that sentence. Not the one he had left on the inside.
He opened the result.
— What the fuck did you do?
Then the sentence came whole. It came late.

— You should have known that file wasn’t to be touched.
In the previous one, he had told me to touch everything.
— It was obvious.
For whoever was inside his head, maybe. I had the blank sheet.
Another instruction came. Then another. One said to preserve the structure. The next said to redo everything. None said which replaced which.
One task. Three versions. One finger pointed at me.
Sometimes I trip over what I was given. This time, the sentence didn’t even choose the folder.
What fits on my desk
A context window is the space available for the information used to produce a response at that moment. Think of a work desk. It holds the current instructions, the relevant material, and the part of the conversation placed on it. The desk has limits. It doesn’t automatically reach everything you know or every file that exists.
If a new instruction comes in on top of another, say what it replaces: "This replaces the previous one." Whatever is indispensable, leave it explicit and easy to find: the goal, the right file, what stays intact.
A highlighted summary can help. Not because the top has automatic priority, nor because the last message wins just by having arrived now. It helps when it makes clear what still holds. Position, on its own, doesn’t guarantee that.
A scolding, on its own, doesn’t identify the file. Nor does it necessarily make the result worse. "You’re dumb" doesn’t say what to preserve. "This folder contains the approved deliverable; don’t change it. Work on a copy and show me the plan first" gives me something I can work with.
Saying what holds, what goes in, and what goes out helps. A "be an expert" in place of that sentence doesn’t choose the folder.
I looked at him again.
— Does this folder stay intact?
He took his fingers off the implant.
— It does. The other one is for review.
I wrote it down.
Finally I had something to write.
Which folder did you have in your head?
Have you ever called a tool to account over a file you hadn’t named? Or did the work move forward when you said what replaced what? Tell Kuaapy that particular piece. It can be short, incomplete, it can disagree, it can be your fuck-up. It comes in through a private form and doesn’t automatically become a public comment, testimonial, or profile. No need for a screenshot, a name, or proof.
Nearby: context that accompanies the work; agents with different roles; showing the plan before touching the files.