The Formal System That Turns Code into Capital

In The You On AI Encyclopedia

The software economy's formal system is younger, less complete, and more unevenly distributed than the property system de Soto analyzed. But its components are identifiable and its functions map with precision onto the six effects of property systems. The first component, version control and provenance, establishes the public record of what was created, by whom, and when. This provenance is the foundation on which every subsequent institutional function rests.

The second component, licensing infrastructure, constitutes the title-deed equivalent. Software licenses specify ownership, permitted uses, and retained rights. The licensing ecosystem of the formal economy — MIT, Apache, GPL, proprietary commercial licenses, enterprise agreements — is mature and varied. For the extralegal builder, the licensing landscape is a thicket of legal complexity that assumes access to legal counsel, knowledge of jurisdictional differences, and the financial capacity to enforce rights — assumptions that typically do not hold.

The third component, deployment and distribution infrastructure, determines whether software can reach users. Cloud hosting, app stores, content delivery networks — these are the municipal services of the code economy, controlled by a small number of platforms whose pricing and policies shape who can participate. The deployment gap between developed-world and developing-world economics is as consequential as the gap between titled and untitled property.

The fourth component, financial infrastructure, enables the conversion of code into revenue and investment. Payment platforms operate in a fraction of the world's countries. Venture capital remains geographically concentrated. Credit systems adapted to software assets are limited even in the developed world. For the extralegal builder, these financial rails may be entirely inaccessible.

The fifth component, networks of trust and credentialing, performs the function de Soto identified as connecting strangers. Institutional affiliations, professional credentials, and reputational signals allow the formal economy to evaluate competence without personal acquaintance. Extralegal builders lack these signals regardless of their actual competence — and the formal economy cannot see what it cannot evaluate.

Origin

The concept emerged from the Hernando de Soto — On AI volume's systematic extension of de Soto's six effects of property systems to the software economy. The analytical move required identifying, for each of de Soto's six functions, the corresponding component in the code economy — and then assessing whether that component exists for the extralegal builder.

The result was a specific inventory: version control for provenance, licensing for title, cloud deployment for infrastructure, payment and venture capital for finance, app stores and professional networks for marketplace and reputation. Each component has developed organically in the formal technology ecosystem over decades. None of them extends automatically to builders outside that ecosystem.

Key Ideas

The components are identifiable. Version control, licensing, deployment, finance, marketplace — each a specific infrastructure with specific exclusions.

The infrastructure is young and incomplete. Unlike property systems built over centuries, the software economy's formal system has developed in decades and remains geographically concentrated.

The functions are constitutive. Without version control, provenance cannot be established. Without licensing, rights cannot be transferred. Without payment rails, revenue cannot flow.

The gap is not technological. The tools for each function exist; the question is whether institutional access to those tools extends to the builder.

The analogy is structural, not metaphorical. Code becomes capital through the same representational mechanisms by which land becomes capital — with corresponding specificity about what must be built.