Defense of the Public Domain

Maintaining the canonical Ora codebase, accepting contributions, ensuring the public-domain status persists, and actively defending against enclosure attempts. The Foundation also stewards the broader public-domain corpus produced under its mission — frameworks, software-displacement projects, and any other public-domain artifacts the Foundation or its community produces — under the same defense framework.

The strategy

The peer-group research on mission defense is unambiguous: trademark defense has been the most effective tool, followed by litigation by specialized organizations (Software Freedom Conservancy, EFF), then advocacy. Patent pools and defensive publication are essentially absent from the peer group's toolkit, but they are appropriate tools for the Foundation's specific work. The Foundation's defense strategy combines:

Trademark on the Foundation's name and on any distinctive mark used to certify public-domain status of artifacts. The OSI's failure to trademark "open source" in the late 1990s is the cautionary tale; the Foundation does not repeat it.
Defensive publication as ongoing practice — documenting architectural decisions and innovations with clear timestamps to expand prior art faster than enclosure can occur.
Monitoring for patent filings and trademark applications that would compromise public-domain status, with response capacity through partnerships with public-interest legal organizations.
Explicit fiscal and legal capacity for litigation if commons artifacts come under attack.
A clear public statement that the Foundation does not hold copyright in stewarded public-domain artifacts. The Foundation's role is steward, not owner. (See Public Domain Status.)

The combined model is closer to Apache (active trademark practice) plus Software Freedom Conservancy (active enforcement litigation) than to any single peer organization.

Open-source community cultivation

A specific dimension of public-domain defense is the active cultivation of an open-source contributor community. The Foundation does not merely accept contributions — it actively supports the community of people developing and maintaining public-domain alternatives across the cognitive tools layer, because community resilience is what makes the public-domain commitment effective in practice rather than only in form. A foundation alone cannot defend a public-domain corpus from determined enclosure attempts; a community of contributors who depend on and improve the corpus can.

Community-cultivation work spans both the framework library (Component 3) and the broader software-displacement work (Component 7). It includes specification publication, contributor documentation and contribution guidelines, recognition and visibility for contributors, coordination among contributors working on related projects, legal-discipline support and review for clean-room work, and distribution infrastructure for completed work.

What the Foundation does not do: pay contributors as employees (most contributions are voluntary), direct contributors' work (contributors choose what they want to work on), exclude alternative implementations (multiple projects addressing the same need are welcomed), or require contributions to be assigned to the Foundation (work is contributed directly to the public domain).

Honest acknowledgment

A 501(c)(3) cannot fully defend against a determined, well-funded enclosure attempt by itself. What it can do is make enclosure more expensive than worthwhile, slow down attempts, attract allies when attempts happen, and ensure the public-domain version remains demonstrably available so that any enclosure attempt competes against a free working alternative. That is the realistic posture, and it is enough.

Partnerships

Legal defense capacity comes through partnerships with public-interest legal organizations:

Electronic Frontier Foundation (EFF)
Software Freedom Law Center
Software Freedom Conservancy
Public-interest IP clinics at law schools — Stanford, Berkeley, Yale among others

These partnerships are pre-engagement at present; the Foundation establishes awareness now and activates legal-defense capacity when a defense need arises.