The era of infinite software
For the whole history of computing, software was scarce. It cost specialist time, it waited in a queue, it needed budget. Scarcity was annoying. But it was also governance in practice: almost nothing got built without someone approving it.
That is over. An analyst describes what she wants to Cursor, Claude or Lovable and gets a working app in an afternoon. She doesn't ask permission, because she no longer needs to. The capacity to produce software stopped being the bottleneck.
When software is infinite, what becomes scarce is order.
Sprawl
A city that grows without a master plan doesn't become a metropolis. It becomes a sprawl: streets that don't connect, buildings on someone else's lot, nobody knows what exists. That is what happens to a company's software infrastructure when building becomes free. Duplicate apps with no owner. Copies of data that outlive the revocation of access to their source. Personal data flowing through tools nobody approved. Cloud and AI bills with no budget.
It isn't bad faith. It is the Dunning-Kruger effect with the power to execute. AI answers fluently regardless of whether the person asking understands the architecture, the official sources or the risks. Before, those who knew little merely thought they knew. Now they act as if they did, and the result looks right. And it works.
In February 2026 a team at Amazon wrote in an internal memo that AI was making the company's tool-duplication problem worse: more created faster, fewer removed. Shadow AI rose to 43% of AI-related breaches worldwide. By the time IT finds out, the company already depends on it.
The wrong reaction
The usual reaction is to ban. Banning kills the productivity the company just gained and pushes construction off the radar. The sprawl doesn't disappear. It becomes invisible.
The other usual reaction is to write a policy. Policy depends on people remembering it. AI doesn't read the wiki.
The choice is not between speed and control. Whoever picks one of the two loses.
Master plan
A city needs a map, zoning, permits and a registry. Not to stop building. So that more gets built, and the result lasts. The same holds for a company: know what exists and who is responsible for each piece; define what each person and each agent can see and change; release construction inside the perimeter, without a queue; register what is born, with an address, an owner and a history.
That is governance. But governance that lets you build more, not governance that makes you build less. It is the difference between a security tool and a scaling tool.
Before the agents
The next phase is agents: AI that doesn't just write code but executes. Queries databases, calls APIs, changes records, deploys. No company is ready for that while its data, systems, permissions and rules are readable only by people.
Before having autonomous agents, a company needs to be readable by agents. We don't sell an agent. We sell the ground prepared for every agent to come.
Kirya is Hebrew for city. In modern Hebrew, it is the urban core that was born with a plan. It is the name we chose for the layer that does this: governance before construction, without a queue before construction.
Kognita, September 2026