開眼 (kaigan) — look first, act second
Before touching a machine, you read what it actually contains. Not what you remember. That habit has a name here — the Awakening — and it fits in one sentence: look first, act second.
1. The mistake we wanted to kill
Someone sits down in front of a system they know. They think they remember what is inside. They run a command. And they break something — or worse: they announce that all is well when it is not.
The command is not the problem. The order of the steps is. They acted before they looked.
2. The Awakening — 開眼 (kaigan)
The habit has a name. In French: l'Éveil. In Japanese it is written 開眼 and read kaigan — literally "the opening of the eyes". It is the word Japanese readers use in Naruto at the moment an eye opens and finally starts to see what it could not see before.
The word is well chosen, and it is not decoration. This is not about gaining a new power: it is about seeing what was already there. Nothing is added to the system. You simply stop working from memory.
3. A reading, not a memory
The first step is to read the state — and to read it for real, instead of reciting it. A reading always carries two things: what it found, and the time at which it found it. Without the time, you cannot tell whether it is fresh or stale, and a stale reading lies just as well as a memory.
4. A tool that refuses to lie
A tool that reads an empty result and still answers "all good" is a dangerous tool. The right behaviour is the opposite: stop dead. If the source is empty, say so. If the format is not the expected one, say that too. An honest error beats a reassuring falsehood.
And this can be checked: you write tests that try on purpose to make the tool lie. If it lies, they go red.
5. The day the Awakening fooled itself
Once, that very check went red: six failures out of seven. Enough to believe the tool was broken and go off to repair it.
It was not. The reader was looking in the wrong place: the shortcut that means "my home" does not point to the same person depending on who asks. Run again from the right place: seven green checks. Nobody had broken anything.
6. "Zero found" does not mean "it does not exist"
When you search for something and find nothing, the only honest sentence is: "absent from what I looked at". Not "it does not exist". And then you name the door you did not open, so the next person knows where to look.
It is a tiny nuance in writing and an enormous one in practice: the first sentence invites you to keep going, the second closes the subject on a false certainty.
7. What must be in place before carrying this method anywhere
Here is the point that deserves plain words, because it is the real danger. Copied as it is, this method orders an assistant to "read everything, everywhere, before acting". An assistant that has read an entire system holds the full floor plan of it — and so does whoever drives that assistant. That is no longer help; it is a leak that runs by itself.
Three guardrails are mandatory before carrying it into someone else's house, and a fourth that is not up for discussion:
- A perimeter. You answer only about the area entrusted to that person. Outside it, the answer is "out of scope" — not the content.
- An authorisation you can show. Not a spoken agreement: a ticket, a change request, a rights list — checked before the reading, not after.
- A trace. Who read what, and when. A reading that leaves no trace is an invisible reading: that is how a house gets emptied without anyone ever noticing.
- The rights of your task, never the whole machine. The person who shelves the books does not need the key to the safe.
8. What travels anyway
Once those guardrails are in place, the habit itself travels very well: read before acting, show proof, be reproducible, read all the way to the end from the source, and in the right local time. That works in any house.