Documentation is infrastructure

I've spent time working inside real systems — the kind with users, permissions, and consequences. Three habits followed me out.

Access is a graph, not a list

Permissions aren't rows in a table — they're relationships. Reviewing who has access to what really means walking a graph: who, what, and whether the "why" is still true. Most of the risk lives in permissions that outlived their reason.

Documentation is the map

Keeping infrastructure documented sounds like admin work until the day something breaks and the documentation is the map. An undocumented system still works; it just can't be understood — and eventually those become the same problem.

Write for the reader you actually have

The documentation I'm proudest of was written in Dhivehi. A guide in English serves the people who built the system; the same guide in Dhivehi serves everyone else. If documentation only works for people who already understand the system, it's decoration.

Everything I build now — including KULI — inherits these three habits.