# Audit. Addit. Edit. > Three compact operating loops for changing what exists, understanding what is unclear, and entering unknown ground. Three ways I have learned to look before I move: Audit. Addit. Edit.; Analyze. Realize. Actualize.; and Detect. Decide. Draft. **Published:** 2026-09-24 **Tags:** AI, agents, design, systems thinking, workflow, human agency **Canonical URL:** https://blog.nikdesign.ca/posts/audit-addit-edit --- *Three ways I have learned to look before I move* I made up a word because the existing ones were not doing enough. The word is **Addit**. It sounds like *add it*. It contains *add* and leans toward *edit*. It is awkward in exactly the way I need it to be. You notice it. You have to ask what it means. The word emerged during a conversation about how I wanted an AI agent to work. I did not want it to arrive, generate a pile of new things, and call that improvement. I wanted it to understand what already existed, identify what was actually missing, and change the whole with care. We landed on three words: **Audit. Addit. Edit.** That started as an instruction for working with software. I quickly realized it described much more than software. ## The first loop An audit begins with respect for reality. Before changing a document, a product, a workflow, or an idea, look at the thing that is already there. Find out what it does, how it came to be, what still works, where it fails, and which strange-looking parts are carrying more history than you can see. Auditing is a form of attention. It asks you to resist the pleasure of the blank canvas for long enough to understand the marks already on it. Then comes Addit. My working definition is: > **Addit** *(verb)*: to improve an existing work by adding what its audit reveals is missing. The audit earns the addition. You are not adding because production feels like progress. You are adding because you found a gap, a weakness, an unrealized possibility, or a piece that would let the rest work better. Then you edit. This is the part that prevents an addition from becoming accumulation. Anything new changes the relationship between everything around it. Add a feature and the interface changes. Add a person and the team changes. Add a belief and the story you tell about yourself changes. You cannot always place the new thing on top and leave the rest untouched. You have to look again. Integrate it. Remove the duplication it created. Simplify what has become too heavy. Let the whole become a new whole. That gives the loop its real shape: **See things as they are. Bring what is missing. Make the whole better.** ## The second loop A few days later, I added another phrase: **Analyze. Realize. Actualize.** It looks similar. It does different work. Audit. Addit. Edit. begins with something that already exists and needs to change. Analyze. Realize. Actualize. begins with a question whose meaning is still unclear. To **analyze** is to examine evidence, patterns, contradictions, and competing explanations. It is the patient work of finding out what may be happening. To **realize** is to understand what the analysis means. That middle word matters. Analysis can continue forever. More material arrives, more tabs open, more distinctions become possible. Realization is the moment the information changes your understanding. It is where observation becomes insight. To **actualize** is to give that insight a useful form. A decision. A prototype. A sentence. An experiment. A conversation. Sometimes the right form is simply a better question, now sharp enough to guide the next investigation. Analysis gathers the pieces. Realization finds the pattern. Actualization lets the pattern enter the world. ## A third loop appeared when the ground was unknown The third phrase arrived while I was thinking about a very practical problem. I wanted Codex to enter a local computer, inspect its hardware and software, find the models and tools already running there, judge which work could sensibly stay local, and produce an integration plan. A good plan could not come first. The machine had facts of its own. That became: **Detect. Decide. Draft.** To **detect** is to meet an unfamiliar environment through observation and testing. What is installed? What is connected? What is running? What is assumed? What can actually be verified? To **decide** is to give those findings direction. Which facts matter to the goal? What deserves attention now? What should be left alone? To **draft** is to make the next move inspectable. It may be a plan or an implementation, but it should say which one it is. A draft gives thought a form that another person can examine, correct, and continue. The sequence sounds obvious after it has been named. Many useful ideas do. Before it was named, I could still feel how often people and machines reversed it: draft something plausible, decide it must be useful, then detect the reality it was supposed to fit. ## Three entrances Eventually I understood that I had not made one nine-step system. I had found three entrances. When I am changing something that already exists, I enter through **Audit. Addit. Edit.** When I am exploring an open question, I enter through **Analyze. Realize. Actualize.** When I am facing an unfamiliar environment, I enter through **Detect. Decide. Draft.** The paths can meet. Detecting an unfamiliar codebase may reveal an existing system that now needs to be audited. An audit may uncover a question that needs analysis. An experiment may actualize an insight and produce something that must then be edited. The point is to know where I am entering. That small distinction changes the first obligation. An existing work asks for attention. An open question asks for understanding. An unknown environment asks for evidence. ## Words as interfaces I like these phrases because they are compact enough to remember and specific enough to affect behaviour. Three verbs can carry an operating agreement between people. They can also carry one between a person and an agent. They say where to begin, what movement should follow, and what kind of result belongs at the end. They also expose certain failures quickly. Did we add before we audited? Did we analyze without ever stating what we realized? Did we draft a plan for an environment we never detected? Did we add something useful and forget to edit the system around it? Those questions apply to products and projects. They also apply to a life. We inherit routines, relationships, beliefs, rooms, tools, habits, and versions of ourselves. Some still serve us. Some became invisible through repetition. Some need something added. Some need to be edited after the addition changes their meaning. A life can be revised without being treated as a mistake. That may be what I like most about **Audit. Addit. Edit.** It assumes there is already something worth understanding. It permits change without demanding erasure. It treats improvement as an act of attention, addition, and renewed judgment. I do not expect these phrases to remain unchanged. That would violate the first one. When they stop helping, I will audit them. If something is missing, I will add it. Then I will edit the whole.