You On AI Encyclopedia · The Formal System That Turns Code into Capital The You On AI Encyclopedia Home
Txt Low Med High
CONCEPT

The Formal System That Turns Code into Capital

The representational infrastructure — version control, licensing, deployment, finance, marketplace — that converts working software into a capital asset, and whose absence defines the AI economy's extralegal majority.
The formal system that turns code into capital performs functions structurally identical to the formal system that turns land into capital. Version control platforms like GitHub serve as the county recorder's office of the code economy, creating public records of authorship and provenance. Software licenses function as title deeds, specifying ownership and transferable rights. Cloud deployment infrastructure corresponds to municipal services that connect a property to the broader economy. Payment processing and venture capital serve the role that banks and mortgage lending play for physical property. Marketplace platforms like app stores perform the discovery and transaction functions of real estate markets. For a builder in the formal technology ecosystem, all of these components are present and integrated. For the extralegal AI builder, they exist in fragmentary form at best — and the fragmentation is precisely what prevents working code from becoming capital.
The Formal System That Turns Code into Capital
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 Representational Gap
The Representational Gap

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.

Six Effects of Property Systems
Six Effects of Property Systems

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.

Deployment Infrastructure
Deployment Infrastructure

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.

Debates & Critiques

Whether the software economy's formal system should be extended to include extralegal builders — or whether entirely different institutional forms should be constructed — remains contested. Advocates of extension argue that the infrastructure exists and proven pathways to inclusion are available. Advocates of alternative construction argue that the existing system carries pathologies (platform concentration, extractive finance) that should not be globalized. The Hernando de Soto — On AI volume positions itself ambiguously on this debate, identifying the gap clearly while leaving the construction strategy to subsequent work.

Further Reading

  1. Hernando de Soto, The Mystery of Capital
  2. Carl Shapiro and Hal Varian, Information Rules
  3. Chris Anderson on the long tail of creation
  4. Eric von Hippel, Democratizing Innovation

Three Positions on The Formal System That Turns Code into Capital

From Chapter 15 — how the Boulder, the Believer, and the Beaver each read this concept
Boulder · Refusal
Han's diagnosis
The Boulder sees in The Formal System That Turns Code into Capital evidence of the pathology — that refusal, not adaptation, is the correct posture. The garden, the analog life, the smartphone that is not bought.
Believer · Flow
Riding the current
The Believer sees The Formal System That Turns Code into Capital as the river's direction — lean in. Trust that the technium, as Kevin Kelly argues, wants what life wants. Resistance is fear, not wisdom.
Beaver · Stewardship
Building dams
The Beaver sees The Formal System That Turns Code into Capital as an opportunity for construction. Neither refuse nor surrender — build the institutional, attentional, and craft governors that shape the river around the things worth preserving.

Read Chapter 15 in the book →

Explore more
Browse the full You On AI Encyclopedia — over 8,500 entries
← Home 0%
CONCEPT Book →