Page under construction.
The underlying logic
Commercial software exists because some user somewhere had a need that the software addressed. The need precedes the software. When the cost of producing software approaches the cost of writing a detailed specification — which is what cognitive automation is doing in real time — the economic moat around commercial software at the consumer-facing layer collapses.
The foundation does not seek to "destroy commercial software." It seeks to dissolve specific chokepoints where commercial actors are extracting value substantially in excess of what they deliver, by producing free public-domain alternatives that fulfill the underlying need users actually have. The framing is value return to customers, not punishment of incumbents. Vendors who earn margins close to their delivered value are not the foundation's concern; competitive markets are not chokepoints.
The Stage 1 / Stage 2 / Stage 3 methodology
The methodology applies in three stages, in order:
Stage 1 — Framework absorption. For any commercial software product identified as a candidate, ask first: what underlying need does this fulfill, and can a framework operating through Ora fulfill the same need? If yes, build the framework. The Intuit suite (TurboTax, QuickBooks, Quicken, Mint) is the paradigm case. Most consumer software in the productivity, finance, planning, and information-organization categories falls into Stage 1.
Stage 2 — Targeted clean-room cloning. For software that cannot be reduced to frameworks — typically because the task requires sustained interactive workflows, specialized formats, persistent application state, or domain-specific tooling — evaluate whether the chokepoint impact justifies the cloning effort. Where the answer is yes, develop a clean-room public-domain functional alternative under strict legal discipline. AutoCAD and the broader CAD monopoly is the clearest Stage 2 example.
Stage 3 — Forbearance. For software that cannot be reduced to frameworks and where the chokepoint impact does not justify cloning effort, the foundation does nothing. Most commercial software falls into Stage 3. Stage 3 is a deliberate boundary, not a deferred commitment.
Selection criteria for Stage 2 cloning
A software product enters Stage 2 consideration only when all of the following are true: framework infeasibility (Stage 1 has been considered and rejected with a specific articulated reason); high extracted-to-delivered value ratio (the vendor extracts margin substantially in excess of value delivered); high user impact (the number of users affected and the financial impact on those users together justify the foundation's investment); chokepoint structure rather than competitive position (the vendor's position rests on structural advantages — format lock-in, network effects, regulatory capture, distribution control — rather than on continuing to deliver superior value); and no existing public-domain alternative meets the need.
Legal discipline for Stage 2 cloning
Clean-room implementation is mandatory and non-negotiable. The methodology follows the discipline established by LibreOffice's relationship to Microsoft Office and GIMP's relationship to Photoshop: no code copying, no UI imitation beyond functional equivalence, file format compatibility through reverse engineering only, no use of leaked source code or internal documentation or trade secrets, and defensive documentation of all design decisions, format reverse-engineering, and architectural choices with timestamps and contributor attribution.
Community contribution, not centralized development
Both the framework library (Stage 1) and the cloning work (Stage 2) operate through community contribution rather than centralized foundation development. The foundation actively cultivates an open-source community of contributors developing public-domain alternatives at the cognitive tools layer. This is the only way the work is achievable — no single foundation can produce the breadth of work that an active community can.
The foundation's role is specification, coordination, and legal-discipline enforcement. The community produces the implementations; the foundation maintains the public-domain status and the discipline.
Active Stage 2 candidates
AutoCAD and the broader CAD ecosystem is the clearest Stage 2 example: industry-wide format dependency (DWG), proprietary file structure, sustained interactive 2D/3D modeling workflow, and chokepoint pricing that prices entire professions out of the tool. The Foundation's posture is support, not duplicate — existing open-source CAD projects (FreeCAD, LibreCAD, GNU LibreDWG) are partners, and the Foundation's contribution is targeting the specific gaps to professional viability rather than starting a parallel project. DWG round-trip fidelity is the load-bearing problem; a documented, public-domain DWG specification is the first concrete deliverable.
Other candidates beyond AutoCAD are post-launch identification work conducted with community input, not from inside the Foundation.
What this is not
Not anti-commercial. Not unlimited. Not punitive. Not enterprise-focused. Not infrastructure. Not a software industry replacement. The foundation operates at the consumer-facing and small-business layer where chokepoints affect ordinary people. Enterprise software, network infrastructure, and specialized industrial systems are outside the foundation's scope.