chore(license): remove deprecated commercial license documents
- Deleted the outdated COMMERCIAL_LICENSE.md and COMMERCIAL_LICENSE.zh-CN.md files, as they are no longer in effect. - Removed the COMMERCIAL.md and COMMERCIAL.zh-CN.md files related to Yao OpenAPI commercial usage, streamlining licensing documentation. - Updated LICENSE file to reflect changes in commercial usage terms and organization.
This commit is contained in:
Max
parent
2993b0b946
commit
cf0ebd5601
6 changed files with 42 additions and 342 deletions
|
|
@ -1,61 +0,0 @@
|
||||||
> **DEPRECATED**: This license is no longer in effect. Please refer to the [LICENSE](LICENSE) file for current licensing terms.
|
|
||||||
|
|
||||||
# Commercial License for Yao
|
|
||||||
|
|
||||||
This document outlines the terms for the commercial license of the **Yao** project. While the Yao project is primarily licensed under the **Apache License, Version 2.0**, certain commercial use cases require a separate commercial license.
|
|
||||||
|
|
||||||
## 1. Commercial License Requirements
|
|
||||||
|
|
||||||
The following use cases require a commercial license:
|
|
||||||
|
|
||||||
1. **Application Hosting Services**
|
|
||||||
If you use Yao, or any derivative product (such as a forked or modified version of Yao), to provide Yao-based application hosting services (e.g., Software-as-a-Service (SaaS) or Platform-as-a-Service (PaaS)) to users, you must obtain a commercial license. This restriction applies regardless of whether the original Yao code or a modified version is used to host and manage applications on behalf of third-party users for commercial purposes.
|
|
||||||
**In addition**, if you provide hosting services for applications that are built using Yao (even if they are customized or modified versions of Yao), a commercial license is required.
|
|
||||||
|
|
||||||
### Definition: Application Hosting Services
|
|
||||||
|
|
||||||
"Application Hosting Services" refers to any service that involves hosting Yao-based applications or web applications created with Yao (including modified versions of Yao) for third-party users. This includes, but is not limited to:
|
|
||||||
|
|
||||||
- **Hosting platforms** providing software or services built on top of Yao for third-party users.
|
|
||||||
- **SaaS or PaaS offerings** where you manage and host applications that are based on or utilize Yao, either in their original or modified form.
|
|
||||||
- **Managed hosting services** where Yao is used as the underlying technology for applications deployed for external clients.
|
|
||||||
|
|
||||||
In these cases, a commercial license is required, whether you are using the original Yao code or a fork/modified version.
|
|
||||||
|
|
||||||
2. **AI Web Application Generation Services**
|
|
||||||
If you provide services that generate AI-driven web applications using Yao, or any derivative product (such as a fork or modified version of Yao), to third-party users, you are required to purchase a commercial license.
|
|
||||||
|
|
||||||
### Definition: AI Web Application Generation Services
|
|
||||||
|
|
||||||
"AI Web Application Generation Services" refers to any service or functionality that utilizes Yao (or any forked or modified version of Yao) to automate the creation of web applications with AI capabilities. This includes, but is not limited to, providing third-party users with:
|
|
||||||
|
|
||||||
- **Automated web application development** driven by AI, where the service generates complete or partial web applications.
|
|
||||||
- **Customizable web solutions** that are powered by AI and built using Yao as the core technology.
|
|
||||||
- **On-demand application generation** for specific client needs, using Yao to dynamically build, configure, or deploy applications for users.
|
|
||||||
|
|
||||||
In these cases, whether Yao is directly used, forked, or modified, a commercial license is required to operate legally.
|
|
||||||
|
|
||||||
## 2. Use Under Apache License 2.0
|
|
||||||
|
|
||||||
For all other uses, the **Apache License, Version 2.0** applies. You are free to use, modify, and distribute the Yao project under the terms of Apache 2.0 as long as your usage does not fall within the restricted scenarios outlined above.
|
|
||||||
|
|
||||||
## 3. Obtaining a Commercial License
|
|
||||||
|
|
||||||
To inquire about or obtain a commercial license, please contact us at:
|
|
||||||
|
|
||||||
- **Email**: [friends@iqka.com]
|
|
||||||
- **Website**: [https://moapi.ai/contact]
|
|
||||||
|
|
||||||
Pricing and terms for commercial licenses vary based on usage scenarios, user scale, and other factors.
|
|
||||||
|
|
||||||
## 4. Compliance and Auditing
|
|
||||||
|
|
||||||
If you have any questions about whether your use case requires a commercial license, please contact us for clarification. We reserve the right to audit usage for compliance and enforce commercial licensing terms where necessary.
|
|
||||||
|
|
||||||
## 5. Disclaimer
|
|
||||||
|
|
||||||
Failure to comply with these licensing terms may result in a violation of the Yao licensing agreement and could lead to legal action.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
**Note:** This commercial license is supplementary to the Apache 2.0 license and only applies in specific commercial scenarios outlined above.
|
|
||||||
|
|
@ -1,61 +0,0 @@
|
||||||
> **已废弃**: 本许可证已不再生效。请参考 [LICENSE](LICENSE) 文件获取当前的许可条款。
|
|
||||||
|
|
||||||
# Yao 商业许可证
|
|
||||||
|
|
||||||
本文件概述了 **Yao** 项目的商业许可证条款。虽然 Yao 项目主要使用 **Apache 许可证 2.0 版** 授权，但某些商业使用场景需要单独的商业许可证。
|
|
||||||
|
|
||||||
## 1. 商业许可证要求
|
|
||||||
|
|
||||||
以下使用场景需要商业许可证：
|
|
||||||
|
|
||||||
1. **应用托管服务**
|
|
||||||
如果您使用 Yao 或其衍生产品（如 Yao 的分支版本或修改版本）为用户提供基于 Yao 的应用托管服务（例如，软件即服务（SaaS）或平台即服务（PaaS）），您必须获得商业许可证。此限制适用于无论是否使用原始 Yao 代码或修改版 Yao 代码，托管和管理应用程序的行为只要是为第三方用户提供的商业目的。
|
|
||||||
**此外**，如果您提供的托管服务是为使用 Yao 构建的应用程序提供托管服务（即使它们是定制或修改版的 Yao），也需要获得商业许可证。
|
|
||||||
|
|
||||||
### 定义：应用托管服务
|
|
||||||
|
|
||||||
"应用托管服务"指任何涉及托管基于 Yao 的应用程序或使用 Yao 创建的 WEB 应用程序（包括 Yao 的修改版本）的服务，服务对象为第三方用户。包括但不限于：
|
|
||||||
|
|
||||||
- **托管平台** 提供基于 Yao 的软件或服务给第三方用户。
|
|
||||||
- **SaaS 或 PaaS 服务**，在这些服务中，您管理并托管基于或利用 Yao 的应用程序，可能是原版或修改版。
|
|
||||||
- **托管服务**，其中 Yao 被用作为客户外部部署应用程序的基础技术。
|
|
||||||
|
|
||||||
在这些情况下，无论是使用原始 Yao 代码还是修改版 Yao，都需要获得商业许可证。
|
|
||||||
|
|
||||||
2. **AI WEB 应用生成服务**
|
|
||||||
如果您提供利用 Yao 或其衍生产品（如 Yao 的分支版本或修改版本）为第三方用户生成 AI 驱动的 WEB 应用程序的服务，您需要购买商业许可证。
|
|
||||||
|
|
||||||
### 定义：AI WEB 应用生成服务
|
|
||||||
|
|
||||||
"AI WEB 应用生成服务"指任何利用 Yao（或任何分支版本或修改版本的 Yao）自动化创建具有 AI 功能的 WEB 应用程序的服务或功能。包括但不限于，为第三方用户提供以下服务：
|
|
||||||
|
|
||||||
- **AI 驱动的自动化 WEB 应用开发**，该服务生成完整或部分 WEB 应用程序。
|
|
||||||
- **可定制的 WEB 解决方案**，这些解决方案由 AI 提供支持，并以 Yao 作为核心技术构建。
|
|
||||||
- **按需应用生成**，根据特定客户需求，使用 Yao 动态构建、配置或部署应用程序。
|
|
||||||
|
|
||||||
在这些情况下，无论是直接使用 Yao，还是使用其分支或修改版，均需要获得商业许可证。
|
|
||||||
|
|
||||||
## 2. 使用 Apache 许可证 2.0
|
|
||||||
|
|
||||||
对于所有其他用途，**Apache 许可证 2.0 版** 适用。只要您的使用不属于上述限制的商业场景，您可以自由地根据 Apache 2.0 许可证使用、修改和分发 Yao 项目。
|
|
||||||
|
|
||||||
## 3. 获取商业许可证
|
|
||||||
|
|
||||||
如需咨询或获取商业许可证，请通过以下方式联系我们：
|
|
||||||
|
|
||||||
- **电子邮件**：[friends@iqka.com]
|
|
||||||
- **网站**：[https://moapi.ai/contact](https://moapi.ai/contact)
|
|
||||||
|
|
||||||
商业许可证的定价和条款会根据使用场景、用户规模及其他因素有所不同。
|
|
||||||
|
|
||||||
## 4. 合规与审计
|
|
||||||
|
|
||||||
如果您对您的使用场景是否需要商业许可证有任何疑问，请联系我们以获取澄清。我们保留审核使用情况以确保合规，并在必要时执行商业许可条款的权利。
|
|
||||||
|
|
||||||
## 5. 免责声明
|
|
||||||
|
|
||||||
未遵守这些许可条款可能会导致违反 Yao 许可证协议，并可能导致法律诉讼。
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
**注意：** 此商业许可证是 Apache 2.0 许可证的补充，仅适用于上述特定的商业场景。
|
|
||||||
18
LICENSE
18
LICENSE
|
|
@ -1,13 +1,13 @@
|
||||||
# Open Source License
|
# Open Source License
|
||||||
|
|
||||||
Yao App Engine is licensed under a modified version of the Apache License 2.0, with the following additional conditions:
|
Yao Engine is licensed under a modified version of the Apache License 2.0, with the following additional conditions:
|
||||||
|
|
||||||
1. Commercial Usage Terms:
|
1. Commercial Usage Terms:
|
||||||
Yao App Engine may be utilized commercially, A commercial license from the producer is required if:
|
Yao Engine may be utilized commercially, A commercial license from the producer is required if:
|
||||||
|
|
||||||
a. Trademark and Branding Requirements
|
a. Trademark and Branding Requirements
|
||||||
|
|
||||||
- The Yao App Engine console/application logo and copyright information must not be removed or modified
|
- The Yao Engine / Yao Agents / Tai / Tai Link console/application logo and copyright information must not be removed or modified
|
||||||
- Logo and copyright information can only be changed with an authorization certificate issued through Yao Developer Certificate
|
- Logo and copyright information can only be changed with an authorization certificate issued through Yao Developer Certificate
|
||||||
|
|
||||||
b. Authorization Verification Requirements
|
b. Authorization Verification Requirements
|
||||||
|
|
@ -15,10 +15,16 @@ Yao App Engine is licensed under a modified version of the Apache License 2.0, w
|
||||||
- The Yao certificate verification logic, processes, and related pages (marked in code comments) must be preserved
|
- The Yao certificate verification logic, processes, and related pages (marked in code comments) must be preserved
|
||||||
- The complete Yao certificate verification system must be maintained regardless of usage purpose
|
- The complete Yao certificate verification system must be maintained regardless of usage purpose
|
||||||
|
|
||||||
|
c. Enterprise Scale Requirements
|
||||||
|
|
||||||
|
- Organizations with 50 or more employees, or with annual revenue exceeding USD 1,000,000, must obtain a commercial license from Infinite Wisdom Software.
|
||||||
|
- To obtain a commercial license, please contact us at https://yaoagents.com/enterprise
|
||||||
|
|
||||||
2. Contributor Agreement:
|
2. Contributor Agreement:
|
||||||
- The producer reserves the right to modify the open-source agreement terms
|
As a contributor, you should agree that:
|
||||||
- Contributed code may be used for commercial purposes, including cloud business operations
|
a. Infinite Wisdom Software can adjust the open-source agreement to be more strict or relaxed as deemed necessary.
|
||||||
|
b. Your contributed code may be used for commercial purposes, including but not limited to its cloud business operations.
|
||||||
|
|
||||||
All other rights and restrictions follow the Apache License 2.0 (http://www.apache.org/licenses/LICENSE-2.0).
|
All other rights and restrictions follow the Apache License 2.0 (http://www.apache.org/licenses/LICENSE-2.0).
|
||||||
|
|
||||||
© 2025 Infinite Wisdom Software.
|
© 2026 Infinite Wisdom Software.
|
||||||
|
|
|
||||||
30
LICENSE.zh-CN
Normal file
30
LICENSE.zh-CN
Normal file
|
|
@ -0,0 +1,30 @@
|
||||||
|
# 开源许可证
|
||||||
|
|
||||||
|
Yao Engine 基于修改版 Apache License 2.0 授权，并附加以下额外条款：
|
||||||
|
|
||||||
|
1. 商业使用条款：
|
||||||
|
Yao Engine 可用于商业用途，但在以下情况下须向 Infinite Wisdom Software 获取商业授权许可：
|
||||||
|
|
||||||
|
a. 商标与品牌要求
|
||||||
|
|
||||||
|
- 不得删除或修改 Yao Engine / Yao Agents / Tai / Tai Link 控制台/应用程序的徽标及版权信息
|
||||||
|
- 徽标和版权信息仅可在持有通过 Yao 开发者证书颁发的授权证书时方可更改
|
||||||
|
|
||||||
|
b. 授权验证要求
|
||||||
|
|
||||||
|
- 必须保留 Yao 证书验证逻辑、流程及相关页面（已在代码注释中标注）
|
||||||
|
- 无论使用目的如何，必须维持完整的 Yao 证书验证系统
|
||||||
|
|
||||||
|
c. 企业规模要求
|
||||||
|
|
||||||
|
- 员工人数达到 50 人及以上，或年收入超过 100 万美元的企业，须向 Infinite Wisdom Software 购买商业授权许可。
|
||||||
|
- 如需获取商业授权，请访问 https://yaoagents.com/enterprise 联系我们。
|
||||||
|
|
||||||
|
2. 贡献者协议：
|
||||||
|
作为贡献者，您需同意以下条款：
|
||||||
|
a. Infinite Wisdom Software 可视需要对本开源协议进行更严格或更宽松的调整。
|
||||||
|
b. 您贡献的代码可被用于商业用途，包括但不限于云服务业务运营。
|
||||||
|
|
||||||
|
其他所有权利与限制遵循 Apache License 2.0（http://www.apache.org/licenses/LICENSE-2.0）。
|
||||||
|
|
||||||
|
© 2026 Infinite Wisdom Software.
|
||||||
|
|
@ -1,107 +0,0 @@
|
||||||
# Commercial Usage Declaration - Yao OpenAPI
|
|
||||||
|
|
||||||
This document outlines the commercial usage terms for the Yao OpenAPI components contained within this directory.
|
|
||||||
|
|
||||||
## Commercial License Requirements
|
|
||||||
|
|
||||||
The Yao OpenAPI module is available for commercial use under the following **mandatory conditions**:
|
|
||||||
|
|
||||||
### 1. Developer Certificate Requirement
|
|
||||||
|
|
||||||
**Commercial usage requires obtaining a Yao Developer Certificate.**
|
|
||||||
|
|
||||||
- All commercial deployments of Yao OpenAPI must possess a valid Yao Developer Certificate
|
|
||||||
- The certificate must be obtained through official Yao certification channels
|
|
||||||
- Usage without proper certification constitutes license violation
|
|
||||||
|
|
||||||
### 2. Trademark and Branding Restrictions
|
|
||||||
|
|
||||||
**Yao branding elements are protected and must remain intact:**
|
|
||||||
|
|
||||||
- Yao App Engine logos and copyright information **MUST NOT** be removed or modified
|
|
||||||
- All Yao trademark elements must remain visible and unaltered in production deployments
|
|
||||||
- Logo and copyright modifications are **ONLY** permitted with explicit authorization through Yao Developer Certificate
|
|
||||||
|
|
||||||
### 3. Certificate Verification System Integrity
|
|
||||||
|
|
||||||
**The Yao certificate verification system must be maintained in its entirety:**
|
|
||||||
|
|
||||||
- **PROHIBITED**: Removal, modification, or circumvention of Yao certificate verification logic
|
|
||||||
- **PROHIBITED**: Alteration of certificate validation processes and related code components
|
|
||||||
- **PROHIBITED**: Modification of certificate verification pages (marked in code comments)
|
|
||||||
- **REQUIRED**: Complete preservation of the Yao certificate verification system regardless of usage purpose
|
|
||||||
|
|
||||||
### 4. Code Integrity Requirements
|
|
||||||
|
|
||||||
For commercial deployments, the following **core verification mechanisms** must remain unmodified:
|
|
||||||
|
|
||||||
- Certificate validation endpoints and middleware
|
|
||||||
- Authentication verification logic and OAuth implementation
|
|
||||||
- License verification routines and related authentication flows
|
|
||||||
- Commercial license checking and enforcement code
|
|
||||||
- Yao branding and copyright verification systems
|
|
||||||
|
|
||||||
_Note: General business logic and API customizations are permitted, but the core licensing and certificate verification infrastructure must remain intact._
|
|
||||||
|
|
||||||
## Compliance Obligations
|
|
||||||
|
|
||||||
### For Commercial Users:
|
|
||||||
|
|
||||||
1. **Obtain Valid Certification**: Acquire and maintain a current Yao Developer Certificate
|
|
||||||
2. **Preserve Verification Logic**: Maintain all certificate verification code intact
|
|
||||||
3. **Respect Trademark Rights**: Keep all Yao branding elements unmodified
|
|
||||||
4. **Regular Compliance Review**: Ensure ongoing adherence to certification requirements
|
|
||||||
|
|
||||||
### For Developers and Integrators:
|
|
||||||
|
|
||||||
1. **Code Review Responsibility**: Verify that certificate verification logic remains intact
|
|
||||||
2. **Documentation Compliance**: Maintain all certificate-related documentation and comments
|
|
||||||
3. **Deployment Verification**: Ensure production deployments include proper certificate validation
|
|
||||||
4. **Update Compliance**: When updating Yao components, preserve all certificate verification systems
|
|
||||||
|
|
||||||
## Prohibited Activities
|
|
||||||
|
|
||||||
The following activities are **strictly prohibited** without explicit written authorization:
|
|
||||||
|
|
||||||
- Removing or disabling certificate verification mechanisms
|
|
||||||
- Modifying Yao branding, logos, or copyright notices
|
|
||||||
- Circumventing license validation processes
|
|
||||||
- Redistributing modified versions that bypass certificate requirements
|
|
||||||
- Creating derivative works that remove authentication restrictions
|
|
||||||
|
|
||||||
## Legal Compliance
|
|
||||||
|
|
||||||
This commercial usage declaration is governed by:
|
|
||||||
|
|
||||||
- **Base License**: Modified Apache License 2.0
|
|
||||||
- **Additional Terms**: As specified in the root LICENSE file
|
|
||||||
- **Commercial Requirements**: As outlined in this document
|
|
||||||
- **Jurisdiction**: Subject to applicable intellectual property and software licensing laws
|
|
||||||
|
|
||||||
## Violation Consequences
|
|
||||||
|
|
||||||
Failure to comply with these commercial usage terms may result in:
|
|
||||||
|
|
||||||
- Immediate license termination
|
|
||||||
- Legal action for intellectual property infringement
|
|
||||||
- Liability for damages and legal costs
|
|
||||||
- Permanent prohibition from commercial Yao ecosystem usage
|
|
||||||
|
|
||||||
## Contact and Authorization
|
|
||||||
|
|
||||||
For commercial licensing inquiries, certificate applications, or clarification of usage terms:
|
|
||||||
|
|
||||||
- **Official Website**: [Yao Developer Certification Portal]
|
|
||||||
- **License Inquiries**: Contact authorized Yao licensing representatives
|
|
||||||
- **Technical Support**: Available exclusively to certified commercial users
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
**Important Notice**: This commercial declaration supplements and does not replace the terms specified in the root LICENSE file. In case of conflicts, the most restrictive terms apply.
|
|
||||||
|
|
||||||
**© 2025 Infinite Wisdom Software. All rights reserved.**
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
_Last Updated: 2025-07-22_
|
|
||||||
_Document Version: 1.0_
|
|
||||||
|
|
@ -1,107 +0,0 @@
|
||||||
# 商业使用声明 - Yao OpenAPI
|
|
||||||
|
|
||||||
本文档阐述了本目录下 Yao OpenAPI 组件的商业使用条款。
|
|
||||||
|
|
||||||
## 商业许可证要求
|
|
||||||
|
|
||||||
Yao OpenAPI 模块可用于商业用途，但须遵循以下**强制性条件**：
|
|
||||||
|
|
||||||
### 1. 开发者证书要求
|
|
||||||
|
|
||||||
**商业使用需要获得 Yao 开发者证书。**
|
|
||||||
|
|
||||||
- 所有 Yao OpenAPI 的商业部署都必须拥有有效的 Yao 开发者证书
|
|
||||||
- 证书必须通过官方 Yao 认证渠道获得
|
|
||||||
- 未经适当认证的使用构成许可证违规
|
|
||||||
|
|
||||||
### 2. 商标和品牌限制
|
|
||||||
|
|
||||||
**Yao 品牌元素受保护，必须保持完整：**
|
|
||||||
|
|
||||||
- Yao App Engine 标志和版权信息**不得**被移除或修改
|
|
||||||
- 所有 Yao 商标元素必须在生产部署中保持可见且未改动
|
|
||||||
- 标志和版权修改**仅**在通过 Yao 开发者证书获得明确授权后允许
|
|
||||||
|
|
||||||
### 3. 证书验证系统完整性
|
|
||||||
|
|
||||||
**Yao 证书验证系统必须完整保持：**
|
|
||||||
|
|
||||||
- **禁止**：移除、修改或绕过 Yao 证书验证逻辑
|
|
||||||
- **禁止**：更改证书验证流程和相关代码组件
|
|
||||||
- **禁止**：修改证书验证页面（在代码注释中标记）
|
|
||||||
- **要求**：无论使用目的如何，必须完整保持 Yao 证书验证系统
|
|
||||||
|
|
||||||
### 4. 代码完整性要求
|
|
||||||
|
|
||||||
对于商业部署，以下**核心验证机制**必须保持未修改状态：
|
|
||||||
|
|
||||||
- 证书验证端点和中间件
|
|
||||||
- 认证验证逻辑和 OAuth 实现
|
|
||||||
- 许可证验证例程和相关认证流程
|
|
||||||
- 商业许可证检查和执行代码
|
|
||||||
- Yao 品牌和版权验证系统
|
|
||||||
|
|
||||||
_注意：一般业务逻辑和 API 定制是允许的，但核心许可证和证书验证基础设施必须保持完整。_
|
|
||||||
|
|
||||||
## 合规义务
|
|
||||||
|
|
||||||
### 商业用户：
|
|
||||||
|
|
||||||
1. **获得有效认证**：获得并维护当前有效的 Yao 开发者证书
|
|
||||||
2. **保持验证逻辑**：保持所有证书验证代码完整
|
|
||||||
3. **尊重商标权**：保持所有 Yao 品牌元素未修改
|
|
||||||
4. **定期合规审查**：确保持续遵守认证要求
|
|
||||||
|
|
||||||
### 开发者和集成商：
|
|
||||||
|
|
||||||
1. **代码审查责任**：验证证书验证逻辑保持完整
|
|
||||||
2. **文档合规**：维护所有与证书相关的文档和注释
|
|
||||||
3. **部署验证**：确保生产部署包含适当的证书验证
|
|
||||||
4. **更新合规**：更新 Yao 组件时，保持所有证书验证系统
|
|
||||||
|
|
||||||
## 禁止活动
|
|
||||||
|
|
||||||
以下活动在没有明确书面授权的情况下**严格禁止**：
|
|
||||||
|
|
||||||
- 移除或禁用证书验证机制
|
|
||||||
- 修改 Yao 品牌、标志或版权声明
|
|
||||||
- 绕过许可证验证流程
|
|
||||||
- 重新分发绕过证书要求的修改版本
|
|
||||||
- 创建移除认证限制的衍生作品
|
|
||||||
|
|
||||||
## 法律合规
|
|
||||||
|
|
||||||
本商业使用声明受以下条款管辖：
|
|
||||||
|
|
||||||
- **基础许可证**：修改版 Apache License 2.0
|
|
||||||
- **附加条款**：如根目录 LICENSE 文件中指定
|
|
||||||
- **商业要求**：如本文档中概述
|
|
||||||
- **管辖权**：受适用的知识产权和软件许可法律约束
|
|
||||||
|
|
||||||
## 违规后果
|
|
||||||
|
|
||||||
未能遵守这些商业使用条款可能导致：
|
|
||||||
|
|
||||||
- 立即终止许可证
|
|
||||||
- 因知识产权侵权而提起法律诉讼
|
|
||||||
- 损害赔偿和法律费用责任
|
|
||||||
- 永久禁止商业 Yao 生态系统使用
|
|
||||||
|
|
||||||
## 联系和授权
|
|
||||||
|
|
||||||
如需商业许可咨询、证书申请或使用条款澄清：
|
|
||||||
|
|
||||||
- **官方网站**：[Yao 开发者认证门户]
|
|
||||||
- **许可证咨询**：联系授权的 Yao 许可代表
|
|
||||||
- **技术支持**：仅向经认证的商业用户提供
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
**重要声明**：本商业声明是对根目录 LICENSE 文件中指定条款的补充，不能替代这些条款。如有冲突，以最严格的条款为准。
|
|
||||||
|
|
||||||
**© 2025 Infinite Wisdom Software. 保留所有权利。**
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
_最后更新：2025-07-22_
|
|
||||||
_文档版本：1.0_
|
|
||||||
Loading…
Add table
Reference in a new issue