Transformation Under Scale — Part III: Read the Estate

Thu, 17 Sep 2026 00:00:00 +0000

Part II settled who owns what, and it settled it by accountability rather than by merit. That ruling names an owner for each capability, but it does not tell you what is running underneath the claim. An owner can be named for a capability that turns out to be four separate systems, or for a fact that is written in a hundred places. Naming the owner does not surface either one. The only way to know what you actually own is to read the estate.

You cannot bound what you have not read. Part I turned objectives into constraints and held them over the estate, and a constraint is only as honest as the reading behind it. Reading honestly means ranking what you find. Evidence is what the builders left behind: the schemas, the foreign keys between them, a count of what is actually deployed. Inference is everything said about that: the diagrams, the names, the stories teams tell. When the two disagree the evidence wins, and an inference with nothing under it is a finding to chase, not a conclusion to build on.

Even ranked, evidence has to be read at the right depth. Reading where the calls go is one depth; whether the data’s meaning has traveled with them is another, and the second can reverse the first. Stop at the first and the plan you write is confident, survives review, and solves a problem the estate does not have. The reading has to go deep enough that the plan is sized to what is actually there. Reading at that depth is half the work. The other half is laying the operating model you decided in Part II over what you read, and that is what the rest of this essay is about.

Technical Discovery on Andrew Hunter — Systems, Architecture, and Engineering Governance

Transformation Under Scale — Part III: Read the Estate