5

Where does the data live?

The chapter about structure. Every operational mess you have ever fought traces back to one root, and once you see it you cannot unsee it.

There was a stretch of time when the same person's contact details existed in three places in my world: my phone, a spreadsheet someone on my team maintained, and the chat history where we actually talked. All three were different. One had an old phone number. One had a misspelled email. One was current. Nobody knew which was which.

That sounds like a small annoyance. Let me show you what it actually cost. Every time my agent needed to reach that person, it had to guess which source to trust. Every project that touched that person started with twenty minutes of "wait, which email is real?" Every system we built on top inherited the confusion, the way a building inherits a crooked foundation. And it was not just contacts. Deal amounts in one place, deal status in another. Tasks tracked in two apps that disagreed. Dates in messages, dates in calendars, dates in heads.

I used to think the fix was discipline. Try harder, update everything everywhere, be more careful. That is fighting the river. The fix, when I finally saw it, was structural and almost embarrassingly simple: every fact gets exactly one home. One place where the truth of it lives. Everything else, every app, every chat, every document, every agent, reads from that home and writes back to it. The other copies stop being rival truths and become what they should have been all along: views. Windows onto the one real thing.

The day we restructured around that idea, an entire category of problem evaporated. Not got better. Evaporated. The agent stopped guessing, because there was nothing to guess. New projects stopped starting with reconciliation, because nothing had drifted. The fights about whose version was right just ended, because "whose version" stopped being a meaningful question.

This is what I mean by taichi with data. Fighting the river is updating five copies and hoping. Redirecting the river is structuring things once, so that staying correct is the path of least resistance. The river still flows, information still moves everywhere it needs to be, but it all flows from one spring.

And here is why this chapter lives in an AI library: an agent is only as good as the ground it stands on. Point an agent at three contradictory spreadsheets and you get a confident machine confidently amplifying contradictions. Give it one source of truth and it becomes precise. Structure is not housekeeping. Structure is what makes delegation safe.

Stop here. Actually sit with this before you scroll on.

If the same fact lives in two places, which one is true?

Try this nowUnder 30 minutes
  1. Pick one mess you actually live with. Contacts, passwords, family dates, project notes, customer info. Pick the one that has burned you most recently.
  2. Map it with your AI. Tell it: "Here is a fact I manage. Help me list every place a version of it lives." You will find more places than you expect.
  3. Choose the one home. Not the fanciest tool. The one you will actually keep open.
  4. Merge with the machine's help. Have it reconcile the versions, flag the conflicts, and produce the single clean record for the home you chose.
  5. Demote everything else to a view. Delete it, or mark it clearly as "copy, do not edit." Notice, over the next week, how a small background hum of anxiety goes quiet.

Two questions before you go

Answer, then say whether you were sure or guessing. Being honest about which is the skill being trained.