--- title: Defense of the Public Domain section: Ora — Foundation arguments status: review description: Why the Foundation stewards its corpus in the public domain — codebase, frameworks, and knowledge library — and what defending that commitment requires. authors: - The Ora Foundation downloads: md: /papers/white/defense-of-the-public-domain.md license: https://creativecommons.org/publicdomain/zero/1.0/ --- # Defense of the Public Domain ## What the Foundation defends The Foundation stewards a public-domain corpus that includes the canonical Ora codebase, the framework library, the knowledge library (continuously updated, provenance-weighted, hosted on decentralized public-domain infrastructure), software-displacement projects produced under Component 7, the founding documents (Founding Philosophy, Statement of Intent, Long-form Launch Essay), and the analytical writing produced by the public-interest advisory function. All released under CC0 1.0 Universal — the strongest public-domain dedication available. The Foundation is steward, not owner. Once dedicated, the artifacts cannot be re-enclosed by any future entity, including the Foundation's successors or anyone who might acquire its assets. The defense is what makes the dedication operative. Public-domain dedication is irreversible by design, but the operative usefulness of the dedication depends on the artifacts remaining demonstrably available, the trademarks protecting the Foundation's name remaining intact, and the prior-art record being fast enough to outpace enclosure attempts. The defense is the work that keeps these conditions in place. ## What the Foundation defends against Three categories of enclosure threat. **Patent enclosure.** A commercial actor obtains a patent that reads on architectural decisions or innovations published in the public domain, then asserts the patent against users or against the Foundation itself. The asserted patent does not have to be valid to be threatening; the cost of defending against an invalid patent is itself a tax on the public-domain commitment. The defense: defensive publication with timestamps, expanding the prior-art record faster than enclosure attempts can occur. Where enclosure is attempted, partner legal organizations engage on the Foundation's behalf. **Trademark enclosure.** A commercial actor registers a trademark on terminology, certification marks, or brand elements that overlap with Foundation work, then claims the right to control how the work is described or referenced. The OSI's failure to trademark "open source" in the late 1990s is the cautionary tale: the term has been claimed and contested by various commercial actors, with the OSI lacking the trademark standing to defend its meaning. The Foundation registers trademarks on its own name and on certification marks at the earliest opportunity post-incorporation. **Distribution enclosure.** Commercial platforms remove, deprioritize, or condition access to public-domain artifacts in ways that effectively restrict their availability. The Foundation's defense is decentralized hosting through volunteer nodes, content-addressed storage that does not depend on a single platform, cryptographic provenance verification that does not require trusting a particular server. The architecture is itself the defense: enclosure attempts would have to compromise enough of the network to render the canonical version inaccessible, which is much harder than compromising a single Foundation server. ## The defense strategy in concrete form ### Trademark practice The Foundation registers trademarks on its name at the earliest opportunity post-incorporation. Trademark rights, where established, are used solely to prevent confusion about the source of artifacts — not to restrict use, modification, or redistribution of the underlying public-domain content. Anyone may state truthfully that their work is derived from or compatible with Foundation-stewarded artifacts; trademark rights would only constrain false implication of endorsement. Certification marks register separately. A certification mark identifies that an artifact is an authentic Foundation release, rather than a fork or a third-party modification. The certification mark's use is governed by the certification standards the Foundation publishes; an artifact that meets the standards may carry the mark; an artifact that does not may not. The mark is the Foundation's signal to users that the artifact they have is the canonical version. The peer-group research is unambiguous on this point: trademark practice is the most effective single defense tool that mission-protected foundations have. Apache Software Foundation has used trademark practice to defend the integrity of Apache projects against attempts to misappropriate the brand. The Foundation adopts the same posture for the same reasons. ### Defensive publication Defensive publication is the practice of timestamping documentation of architectural decisions and innovations into the public record, expanding the prior-art record faster than enclosure attempts can occur. A patent claim that reads on a design pattern published before the patent's priority date is an invalid claim; defensive publication is what creates the publication record that invalidates such claims in advance. The vault is the publication surface. The public sites are the publication surface. The Foundation's git repositories are the publication surface. Every architectural decision, every framework specification, every design pattern, every reverse-engineering result is documented with a timestamp and pushed into version control where the timestamp is independently verifiable. The cadence is continuous, not periodic. Architectural decisions get documented when they are made; specifications get published when they are stabilized; reverse-engineering results get pushed as the work proceeds. The defense is not a project that runs once a year; it is the everyday practice of the Foundation's documentation work. For Stage 2 software-displacement work specifically, defensive documentation is mandatory. Design decisions, format reverse-engineering, and architectural choices are documented with timestamps and contributor attribution as a defense against future trade-secret or copyright claims. The documentation is itself published into the public domain — if the Foundation's reverse-engineering record is public, it cannot be claimed that the work was based on confidential materials. ### Monitoring Patent and trademark monitoring runs continuously. Google Patents alerts surface new patent filings that read on terminology overlapping Foundation work; TESS / USPTO trademark-application monitoring surfaces applications that would compromise the public-domain status of Foundation artifacts. The monitoring runs in partnership with public-interest legal organizations whose mission already includes patent and trademark scrutiny. The Foundation does not maintain an in-house monitoring department; it shares standing relationships with EFF, Software Freedom Conservancy, Software Freedom Law Center, and public-interest IP clinics at law schools, all of whom monitor patent and trademark filings as part of their existing work. When monitoring surfaces a filing that bears watching, the partner organization flags it to the Foundation. The Foundation evaluates whether to act. Some filings will resolve themselves without intervention; others warrant pre-grant submissions of prior art, opposition proceedings, or — in the most serious cases — litigation. The decision to act is the Foundation's; the legal capacity to act comes through the partnerships. ### Litigation capacity The Foundation does not maintain an in-house litigation department. Litigation capacity comes through partnerships with specialized organizations that already exist for this purpose: **Electronic Frontier Foundation.** Civil liberties and digital rights litigation, including AI-related cases. EFF has the infrastructure, the bar admissions, the historical track record, and the standing relationships with judges and policymakers that the Foundation would otherwise have to build from scratch. **Software Freedom Law Center.** Open-source and free-software legal defense. SFLC's mission is exactly the work the Foundation needs done; the partnership is natural. **Software Freedom Conservancy.** Enforcement litigation around software-freedom violations. SFC is the closest peer-group precedent for the Foundation's enforcement posture. **Public-interest IP clinics at law schools.** Stanford, Berkeley, Yale among others. Pro bono representation when full counsel is not warranted. The clinics serve as both legal capacity and as a pipeline for next-generation public-interest IP attorneys whose careers grow alongside the Foundation's mission. The Foundation maintains explicit fiscal capacity for litigation when commons artifacts come under attack. The capacity does not require maintaining a permanent defense fund; it requires maintaining the relationships that can be activated when the situation warrants and the fundraising capability to support the partner organizations doing the work. ### Decentralized hosting (architectural defense) The knowledge library is hosted on distributed infrastructure rather than concentrated on Foundation servers. This is an architectural commitment, not a deployment detail. A library hosted on a single server is a single point of enclosure failure. If the Foundation is captured, defunded, sued out of existence, or simply dissolved, the library disappears with it. A library hosted on distributed infrastructure persists regardless of what happens to the Foundation, which is the public-domain commitment made operational at the data layer. Three established patterns compose: content-addressed storage (IPFS-class infrastructure), distributed hosting through volunteer nodes (partner organizations, volunteer operators, mirror sites at universities and libraries), and cryptographic provenance verification through the P1–P6 hierarchy. The Foundation operates some nodes and coordinates the network; it does not host exclusively. The Foundation's role is signing authority and specification authorship, not hosting infrastructure. The architecture is itself a defense mechanism. Enclosure attempts would have to compromise enough of the network to render the canonical version inaccessible, which is much harder than compromising a single Foundation server. ### Active 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. Apache projects have survived because the contributors did not let them be enclosed; Wikipedia has survived for the same reason; Creative Commons has survived for the same reason. The defense is in the community's continued investment in the corpus, not in any one entity's standing to defend. 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. The Foundation does not promise that the public-domain corpus is permanently safe. It promises that the corpus has been dedicated to the public domain, that the dedication is irreversible by design, that the practical defense is in continuous operation, and that the architecture distributes the defense across a network and a community rather than concentrating it in a single point of failure. The combination is what gives the public-domain commitment its operative force. The honest framing also matters for how the Foundation talks about its work. The Foundation does not claim to be the bulwark against AI enclosure; it claims to be one specific actor doing one specific kind of work, in coordination with partner organizations whose mission overlaps with parts of the Foundation's work, in a community of contributors whose continued investment is what gives the corpus durability. The Foundation is small; the work is bounded; the partnerships are how the work scales. ## What the Foundation does not do The Foundation does not assert copyright claims it does not have. It does not hold copyright in the artifacts it stewards (the artifacts are public-domain), so it cannot bring copyright-infringement claims, and it does not pretend to. The defense is structured around trademark, defensive publication, monitoring, litigation through partners, decentralized hosting, and community cultivation — all of which are tools that work without copyright claims. The Foundation does not police derivatives. A commercial actor that takes a Foundation-stewarded artifact, modifies it, and incorporates it in a closed product is doing something the public-domain dedication permits. The Foundation does not bring action against such uses. The Foundation does not require attribution; it does not require derivatives to be also public-domain; it does not require commercial uses to be reported. The artifacts are free; uses are free. The Foundation does not engage in IP reform advocacy. The Foundation operates under existing IP law. Reforming that law — pushing for shorter patent terms, reduced trademark scope, expanded fair-use provisions — is other organizations' work. The Foundation defends the commons within the law as it exists; the legal-reform work belongs to organizations whose mission is legal reform. The Foundation does not target specific commercial actors out of animosity, political alignment, or personal preference. The selection criteria for what the Foundation pays attention to are principled and public. Vendors meeting the chokepoint criteria are targets for chokepoint-elimination work regardless of their other characteristics; vendors not meeting the criteria are not targets regardless of how anyone feels about them. ## The summary The Foundation defends the public-domain corpus through a layered strategy: trademark practice on the Foundation's name and certification marks, defensive publication as continuous timestamped documentation, patent and trademark monitoring through partner organizations, litigation capacity through standing partnerships, decentralized hosting that distributes the architectural defense, and active cultivation of a contributor community whose continued investment gives the corpus its long-arc durability. The honest acknowledgment is that a 501(c)(3) cannot fully defend against a determined well-funded attempt by itself; what it can do is raise the cost of attempt, distribute the defense across a network, and keep the public-domain version demonstrably available so any enclosure attempt competes against a free working alternative. The defense is the work that keeps the public-domain dedication operative; the dedication itself is irreversible by design.