Define explicit open-source licensing and trademark boundaries

LICENSE

@@ -0,0 +1,202 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+

LICENSING.md

@@ -1,8 +1,25 @@
-# IPI Licensing Policy
+# IPI Licensing and Attribution Policy
 
 Open source requires an explicit license. Public visibility alone does not grant
 permission to use, modify, or redistribute a repository.
 
+## Licenses in this repository
+
+- Software, automation, and general community documentation are licensed under
+  [Apache License 2.0](LICENSE).
+- IPI Improvement Proposals and templates under [`ipi/`](ipi/) are dedicated
+  to the public domain under [CC0 1.0 Universal](ipi/LICENSE), so independent
+  implementations can reproduce and implement the specifications.
+- Historical legal documents under [`statements/`](statements/) and
+  [`translations/`](translations/) are excluded from those grants and remain
+  all rights reserved unless a file explicitly states otherwise. See
+  [statements/README.md](statements/README.md).
+- Project names, logos, domains, and other marks are governed separately by
+  [TRADEMARKS.md](TRADEMARKS.md).
+
+The repository [NOTICE](NOTICE) records this scope. A directory-level license
+or notice takes precedence for the material in that directory.
+
 ## Repository requirements
 
 Before an IPI repository is described as open source, it must:
@@ -25,11 +42,22 @@ and release notes. A fork must not be presented as original IPI work.
 
 ## Original IPI work
 
-The license for original code and specifications must be selected deliberately
-by the relevant rights holders. Code, protocol specifications, documentation,
-brands, and media may require different licenses. Until those decisions are
-recorded, no automated process should add a blanket license across existing
-repositories.
+The license for original work must be selected deliberately by the relevant
+rights holders. IPI's default for new original software repositories is
+Apache-2.0. The default for new IPI proposals is CC0-1.0. A repository may use
+a different OSI-approved license when compatibility, upstream provenance, or a
+recorded project decision requires it.
+
+Code, specifications, documentation, brands, media, data, and legal documents
+may require different treatment. Automated changes must not overwrite an
+upstream license or relicense existing material without documented authority.
+
+## Contributions
+
+Contributions are submitted under the license that covers the destination
+file or directory. Contributors must have the right to submit their work and
+must preserve third-party attribution. A contribution that cannot meet those
+conditions must not be merged until the rights are resolved.
 
 License questions should be raised publicly as issues unless they contain
-private legal or contributor information.
+private legal, security, or contributor information.

NOTICE

@@ -0,0 +1,22 @@
+IPI community standards
+Copyright 2026 IPI contributors
+
+Unless a file or directory states otherwise, the software, automation, and
+community documentation in this repository are licensed under the Apache
+License 2.0 in LICENSE.
+
+IPI Improvement Proposals and their templates under ipi/ are dedicated to the
+public domain under CC0 1.0 Universal in ipi/LICENSE. This is intended to make
+protocol specifications freely implementable, quoteable, and portable across
+independent implementations.
+
+The historical legal documents under statements/ and translations/ are not
+covered by the Apache-2.0 or CC0-1.0 grants. They are preserved for review and
+remain all rights reserved unless an individual file says otherwise. See
+statements/README.md before relying on them.
+
+Licenses do not grant permission to use IPI names, logos, or other marks to
+imply endorsement, origin, or compatibility. See TRADEMARKS.md.
+
+Third-party components retain their own licenses, copyright notices, and
+attribution requirements.

README.md

@@ -23,6 +23,7 @@ Repository-specific instructions always take precedence.
 | [Maintainers](MAINTAINERS.md) | Access, review, and stewardship expectations |
 | [Roadmap](ROADMAP.md) | Milestones and public exit criteria |
 | [Licensing](LICENSING.md) | Licensing and upstream-attribution policy |
+| [Trademarks](TRADEMARKS.md) | Fair use, independent forks, and endorsement rules |
 | [IPI proposals](ipi/README.md) | Protocol and governance proposal process |
 
 ## Proposal naming
@@ -43,9 +44,18 @@ verification evidence.
 
 Files under [statements/](statements/) and [translations/](translations/) are
 preserved separately from the technical and community standards in this
-repository. Their presence does not make them a current protocol specification
-or a substitute for qualified legal review. Changes to those files require an
-explicit legal review process.
+repository. They are excluded from the Apache-2.0 and CC0-1.0 grants and remain
+all rights reserved unless a file says otherwise. Their presence does not make
+them a current protocol specification or a substitute for qualified legal
+review. See [the legal-document notice](statements/README.md) before relying on
+them.
+
+## License
+
+General repository content is Apache-2.0. IPI proposals under `ipi/` are
+CC0-1.0. Historical legal documents are excluded as described above. Names and
+marks are governed by [TRADEMARKS.md](TRADEMARKS.md). See [NOTICE](NOTICE) and
+[LICENSING.md](LICENSING.md) for the exact scope.
 
 ## Historical and incubating material
 

TRADEMARKS.md

@@ -0,0 +1,49 @@
+# IPI Trademark Policy
+
+Open-source licenses grant rights in code and documentation. They do not grant
+rights to use project names, logos, domains, or other marks in a way that
+suggests endorsement, certification, or official status.
+
+## Uses that do not require permission
+
+You may use the word **IPI** truthfully to:
+
+- state that software implements, integrates with, or is derived from IPI;
+- link to the IPI project or discuss it in news, research, reviews, and
+  community material; and
+- describe compatibility, provided the claim is accurate and does not imply
+  certification or endorsement.
+
+Examples include “built for IPI,” “compatible with IPI-####,” and “an
+independent implementation of an IPI specification.” Make independent status
+clear and do not copy the official visual identity so closely that users could
+confuse the source.
+
+## Uses that require written permission
+
+Permission is required to:
+
+- present a product, service, organization, event, network, or release as
+  official, endorsed, certified, or operated by IPI;
+- use an IPI mark as the primary name of an unrelated commercial offering;
+- register a confusingly similar domain, account, company name, or application
+  name; or
+- use the marks in a deceptive, defamatory, or unlawful way.
+
+## Forks and distributions
+
+Forks may accurately describe their origin, but must use a distinct name and
+visual identity unless permission is granted. Modified software must not be
+presented as an official IPI release. Compatibility claims should identify the
+relevant version, proposal, test, or other reproducible evidence.
+
+## No technical gatekeeping
+
+This policy is not a mechanism for restricting implementation of open IPI
+specifications. Anyone may implement, test, study, and distribute covered work
+under its applicable license. Trademark rules address source and endorsement,
+not technical permission.
+
+This is a bootstrap policy and may be refined through the public governance
+process. Raise non-sensitive questions in the organization Discussions. Report
+impersonation or security-sensitive misuse through [SECURITY.md](SECURITY.md).

ipi/IPI-0000.md

@@ -277,8 +277,13 @@ implementation.
 
 ## Copyright and licensing
 
-Proposal authors must have the right to submit their text and examples. The
-project-wide documentation license remains pending until the relevant rights
-holders record a decision under [LICENSING.md](../LICENSING.md). Until then,
-public access to a proposal must not be mistaken for permission to reuse it
-outside the rights provided by law.
+Proposal authors must have the right to submit their text and examples. IPI
+proposals, templates, and proposal metadata in this directory are dedicated to
+the public domain under [CC0 1.0 Universal](LICENSE). This permits independent
+implementations and standards bodies to reproduce, quote, translate, and
+implement the specification without seeking additional copyright permission.
+
+CC0 does not grant trademark rights, patent rights held by third parties, or
+permission to misrepresent conformance. Implementers remain responsible for
+the security, licensing, and accuracy of their implementations. See the
+project-wide [licensing policy](../LICENSING.md).