Open Source Intelligence

Open source has a problem everyone knows about and nobody has solved: the people who create the most value capture the least.

A single developer maintains a library used by half the internet. Companies worth billions depend on it. The developer earns nothing, burns out, and the library falls into disrepair. We have watched this story play out with OpenSSL, core-js, Babel, and dozens of others. The incentive structure is broken. Contribution is altruistic. Consumption is free. The economics do not work.

Constructs might be the first digital artifact where open source and compensation are not in tension.

Why Software Failed

Open source software is infinitely copyable at zero marginal cost. Once a library is published, anyone can use it without paying or even acknowledging the author. This is a feature, not a bug — it is why open source won. But it is also why open source authors go unpaid.

Every attempt to fix this has struggled with the same friction: payment adds a transaction cost that slows adoption. Dual licensing creates confusion. Open core frustrates the community. Sponsorship depends on corporate goodwill. None of these models align the incentive of the creator (get paid) with the incentive of the user (get the best tool for free).

The fundamental problem: in open source software, the value chain is invisible. A developer uses React, which uses a scheduler, which uses a reconciler, which uses a fiber architecture — and none of those internal layers can capture value from the applications built on top of them.

Why Constructs Are Different

Constructs have a property that software libraries do not: visible, traceable lineage through forking.

When someone forks a construct, the relationship is permanent and public. The fork knows who its parent is. The parent knows it was forked. The entire ancestry is recorded. This is true of Git repositories too, but with one critical difference: constructs have a built-in transaction layer.

When a forked construct is sold, the platform can automatically split the revenue. The seller gets their share. The original author gets a royalty. No negotiation, no invoicing, no goodwill required. The payment flows through the same infrastructure that hosts the construct. It is not a donation. It is not a sponsorship. It is a royalty — automatic, proportional, and permanent.

The Royalty Flywheel

This changes the incentive structure in a way that no previous model has achieved. Consider the dynamics:

Publishing free constructs becomes an investment. If you publish a high-quality free construct and it gets forked, improved, and sold by someone else, you earn money from their sale. The better your free construct, the more forks it attracts, the more likely one of those forks becomes a paid product, and the more royalty income you earn. Generosity is directly monetizable.

Improvement is incentivized. The person who forks and improves a construct can sell it without guilt. They added value. The original author is automatically compensated. There is no ethical tension between “I built on your work” and “I want to get paid for my contribution.” Both can happen simultaneously.

Quality compounds. Each fork makes the original more valuable, because each fork is a potential revenue source. The best constructs attract the most forks, which generate the most royalties, which incentivize the original author to maintain and improve the base construct, which attracts more forks. This is a flywheel. Open source software has never had one.

The License Innovation

The mechanism that enables this is a license type that did not exist before: MIT + Royalty. It says: you can use this freely, fork it freely, modify it freely, distribute it freely. But if you sell a derivative, the original author receives a percentage.

This is not Creative Commons Non-Commercial, which prohibits commercial use entirely. It is not a proprietary license, which restricts modification. It is a license that explicitly encourages commercial use while ensuring the original creator benefits from it. It aligns the interests of every participant in the value chain.

The open source community has spent decades debating whether permissive licenses (MIT, Apache) or copyleft licenses (GPL, AGPL) better serve creators. MIT + Royalty sidesteps the debate entirely. It is as permissive as MIT for usage and as protective as copyleft for compensation. The construct is free. The commerce is shared.

Why It Works for Constructs

This model works for constructs in a way it could not work for traditional software, for three reasons:

Constructs are standalone artifacts. A construct is a self-contained document, not a library with dependencies. There is no build system, no package manager, no transitive dependency graph. The unit of value is the file itself. This makes tracking lineage and splitting revenue trivially simple compared to software.

The platform controls the transaction. Because constructs are discovered, purchased, and downloaded through the platform, the platform can enforce the royalty split at the point of sale. There is no way to “use the construct without paying” for paid constructs, because the content is gated. And there is no way to “sell a fork without paying the royalty,” because the platform processes the payment.

The value is in the judgment. You cannot mechanically extract the valuable parts of a construct the way you can extract a utility function from a library. The value is in the holistic design — the combination of identity, principles, workflow, and boundaries that produces a specific behavior. You either use the construct or you do not. There is no way to “vendored-in” the valuable parts while avoiding the license.

What This Means

If fork royalties work — and it is too early to say they will — they represent a resolution to a problem the technology industry has struggled with since Richard Stallman wrote the GPL in 1989. Not by restricting freedom, but by aligning economics with contribution.

The retired surgeon who writes a medical triage construct and publishes it for free is not being altruistic in the traditional open source sense. She is planting a seed. Every fork that specializes her construct for a specific hospital system, a specific regulatory environment, a specific patient population — every one of those forks, if sold, sends her a royalty. Her expertise does not need to be monetized directly. It monetizes through the ecosystem it enables.

Open source intelligence. Not intelligence that is merely available for free, but intelligence that rewards the people who made it possible.

Related: The Fork Graph explores how constructs branch and evolve through forking. The Construct Economy, 2030 imagines the long-term economic impact of fork royalties.