# Community Use and Attribution License
## Version 1.0

This is a custom source-available software license. It is not the Mozilla Public License, a PolyForm license, or an OSI-approved open-source license. The version identifier is fixed; publication of another version does not change this one.

### 1. Definitions and scope

**Covered Software** means the software expressly released under this License, including copies, modifications, translations, and portions of that software. It includes a modified source file and a new source file containing protectable expression from Covered Software. A separate file containing no such expression is not covered merely because it communicates with or is distributed alongside Covered Software.

**Contributor** means a person or entity that owns or controls rights in material it makes available under this License. Each Contributor licenses only rights it has authority to license.

**You** means the person or entity exercising these permissions. Activities arranged through agents or entities You control are treated as Your activities when applying the commercialization restrictions.

**Attribution Record** means the project-identification and contributor-credit information supplied with Covered Software in an ATTRIBUTION file, a CONTRIBUTORS file, or an equivalent clearly identified record. Copyright and third-party license notices remain required independently of this record.

**Software Offering** means distributing or providing others access to Covered Software as an application, service, library, component, or other software product, including a modified, renamed, embedded, or remotely accessed version. This term excludes the activities expressly permitted by Section 3.

**Monetization** means receiving or soliciting money or other economic consideration attributable to a Software Offering, as specified in Section 4. It does not mean all income earned by a person or business that uses the software.

### 2. Grant and acceptance

Each Contributor grants You worldwide, nonexclusive, royalty-free permission, for the duration of its applicable rights, to run, reproduce, modify, translate, display, perform, distribute, and make Covered Software available over a network, subject to this License. Permitted commercial activities are described in Section 3.

These permissions are granted on the express conditions in Sections 3 through 7, not merely in exchange for promises independent of the grant. By exercising a permission for which You need this License, You accept those conditions. No acceptance is required for acts independently authorized by applicable law or another valid license.

Recipients obtain the applicable permissions directly from the Contributors. This License transfers no ownership and permits no Contributor to license another person's rights without authority.

### 3. Expressly permitted activities

Subject to the source and attribution conditions, the following activities are permitted even when undertaken for profit:

(a) Using Covered Software for Your own work or operations, including professional theatrical productions, engineering, education, manufacturing, and other commercial activities.

(b) Charging for performances, physical goods, professional work, or other outputs produced or assisted by Covered Software, where the customer is not principally purchasing the software or access to its functionality. An output is not Covered Software merely because the software produced it; embedded copies of covered code remain covered.

(c) Charging for genuine development, customization, installation, integration, maintenance, training, or support. Fees may include a profit. Any delivered Covered Software must be identified as licensed under this License without a separate software-license fee. The customer must receive the required source and must not need continuing payment to You for permission to run the delivered software or appoint another provider.

(d) Managing a customer-controlled deployment for that customer's own work. The customer must control authorized access, have control of or a practical right to transfer its deployment and data, and receive what it needs to appoint another provider. Selling general access to a public or multi-customer hosted application is not converted into this exception by calling the charge support, management, or hosting, or by creating a separate instance for each subscriber.

(e) Providing general-purpose infrastructure not offered specifically as access to Covered Software; and incorporating Covered Software incidentally into a larger system whose principal sold functionality is materially different from the covered application, rather than a substitute, rebranding, or repackaging of it.

(f) Publishing source forks, distributing copies without Monetization, and operating public or private instances without Monetization. A permitted fork may compete with, improve upon, or replace the original project. It need not obtain the original maintainer's approval.

Charging for an activity expressly allowed above does not by itself constitute prohibited Monetization. Renaming a prohibited charge or dividing it between related parties does not make it permitted.

### 4. Prohibited software commercialization; limited donations

**4.1** Without separate permission from the relevant rights holders, You must not exercise rights under this License to create, distribute, or operate a Monetized Software Offering.

**4.2** Prohibited Monetization includes:

(a) Sale, rental, subscription, access, download, usage, seat, API, or feature charges for the Software Offering, including mandatory memberships or purchases required to obtain its functionality.

(b) Advertising, paid promotional placements, affiliate commissions, or referral payments associated with pages, interfaces, or responses through which the Software Offering is provided.

(c) Selling or licensing user information or usage data collected through the Software Offering, or receiving consideration for supplying that information to another party. Necessary processing by a service provider on Your behalf, without such consideration, is not prohibited by this paragraph.

(d) Payments described as donations, sponsorships, support, or another category when they are actually a condition of software access, functionality, preferential service capacity, or another software benefit.

These restrictions apply whether or not revenues exceed costs and whether consideration is received in cash, cryptocurrency, goods, services, or another form. Neutral identification of the operator and a truthful description of separately available Section 3 services are not, without more, paid promotional placements.

**4.3** You may request and accept genuinely voluntary donations solely to reimburse reasonable, documented, direct third-party expenses of operating a freely accessible instance. Eligible expenses are hosting, bandwidth, storage, domain registration, transaction fees, and necessary third-party service charges. They exclude compensation for operator or developer time, unrelated overhead, profit distributions, and duplicate reimbursement.

No donation may be required for access or confer software features, access priority, advertising, or promotional placement. A neutral acknowledgement of a donor's name is permitted. Receipts may not exceed eligible expenses already incurred and a reserve equal to three months of reasonably budgeted eligible expenses. Unexpected excess must, within 90 days, be refunded or irrevocably donated to an independent charitable organization without benefit to You, and further solicitation must stop until within this limit. Keep records sufficient to demonstrate compliance; donor identities need not be publicly disclosed.

### 5. Source availability and downstream rights

When You distribute Covered Software, supply recipients with this License, the required attribution and notices, and the corresponding source for the covered version, including Your modifications. Source may accompany the distribution as a separate, clearly identified download without an additional fee.

When You provide members of the public access to Covered Software's functionality over a network, provide those users a reasonably prominent, no-charge means to obtain that source, License, and attribution for the deployed version. Keep that means available while the version is offered. Access conditions reasonably needed to secure the service may apply, but source access must not require an additional purchase or separate approval. Source need not be made available to people who are not entitled to use a restricted service.

Corresponding source means the preferred editable form of covered files, with the build instructions and project-specific scripts needed to reproduce the covered components. It does not require disclosure of credentials, personal information, customer data, general-purpose tools, or independent files excluded by Section 1. Provide nonsecret configuration examples where necessary.

Distribute Your covered modifications under this same License version. You may choose separate terms for independent components, but may not use those terms or technical restrictions to deny recipients the permissions granted for Covered Software. A service may have ordinary security and conduct rules; those rules must not purport to cancel recipients' separate rights in downloaded code.

Private use alone does not require publication of modifications. Delivery to a customer requires supplying that customer, not necessarily the general public, with the required materials.

### 6. Attribution, contributor recognition, and lineage

**6.1 Preserve received records.** Retain the substance of all copyright, license, warranty, and attribution notices received with Covered Software. Include the Attribution Record with each distribution and in the credits made available under Section 6.4.

**6.2 Carry credits forward.** For a fork of a project or application, preserve the inherited Attribution Record from the version You adopted. Whenever You incorporate another version, merge, rebase, cherry-pick, copy, or otherwise import covered contributions, carry forward the inherited records associated with that incorporation as well as credits already present in Your fork. Rewriting or removing version-control history does not remove this requirement. Record the upstream project and, when supplied or reasonably ascertainable, its source location and incorporated revision or release.

There is no obligation to monitor or credit future upstream work that You do not incorporate. Upstream revisions do not authorize deletion of existing credits, except for the corrections allowed below. For extraction of an expressly identified component rather than a project fork, preserve that component's applicable credits and upstream project identification; undifferentiated project-level credits remain applicable.

**6.3 Add accepted contributors.** Before distributing or publicly deploying a version, add each identified person or entity whose contribution You accepted and incorporated into that version, using the public credit identity supplied with the contribution. Include identified coauthors, not just the person who merged or committed the change. A contributor may choose a pseudonym. Purely automated accounts need not be listed as people, and contribution credit does not imply copyright ownership or maintenance responsibility.

You may deduplicate records, change their presentation, correct demonstrable factual errors, update broken project references, and honor a credited person's verified request for a different public identity or anonymized credit. Do not publish private contact information merely to comply with this License. Preserve copyright-ownership notices unless their alteration is authorized by the relevant holder or required by law.

For a continuing project fork, replacing, refactoring, or removing an earlier contribution does not by itself justify erasing its inherited project-history credit. Such a person may be identified as a historical contributor. This requirement does not attach to independently created software containing no Covered Software or other protected material derived from it.

**6.4 Make credits accessible.** For software with an interactive interface, provide a readily discoverable Credits, About, or equivalent entry in the ordinary interface. It must identify the original project, distinguish the current operator or fork from that project where applicable, and provide the full inherited and added contributor record, project references, license text, and required source-access information. A credits page or dialog is sufficient; individual names need not appear on every screen.

For software without a suitable interactive interface, provide equivalent information through ordinary documentation, a standard informational command, or an accessible service-information endpoint. Production audiences and recipients of outputs that are not Covered Software need not be shown credits merely because the software helped produce those outputs.

A locally supplied record is required; a link solely to a mutable external contributor page is insufficient. No tracking, remote verification, compulsory logo display, or advertising is required.

### 7. Truthful identity and trademarks

You may identify Your own changes and operate a differently named fork, but must not falsely claim authorship of others' contributions or imply that the original project or a Contributor endorses or operates Your version.

This License grants no trademark or logo rights except any limited permission necessary for truthful textual attribution. It does not limit rights to truthful reference that applicable law independently provides.

### 8. Contributions and additional permissions

A contribution is not a copyright assignment. A Contributor who intentionally submits material for inclusion under this License must have authority to provide the required rights and must identify any separately licensed material. Maintainers must obtain the relevant Contributor's agreement before treating a submission as licensed under these terms; merely discovering code in a pull request or repository does not establish authority.

Neither being credited nor maintaining the project authorizes anyone to grant exceptions for another Contributor's material. Commercial exceptions, alternative licensing, or special rights for an official deployment require permission covering the relevant rights. Nothing prevents a rights holder from separately licensing rights it actually controls.

### 9. Breach, correction, and downstream protection

Actions outside the grant are not authorized. If You violate a condition in Sections 3 through 7, Your permissions under this License terminate, subject to the following correction process.

For Your first violation, permissions are automatically reinstated when You fully correct it within 30 days after discovering it or receiving a written notice identifying it, whichever occurs first. Correction includes ending prohibited Monetization and taking reasonable steps to supply missing source or credit and correct affected releases. This is not permission to continue a violation for 30 days. Reinstatement does not waive an accrued claim unless the relevant rights holder agrees in writing.

For subsequent violations, reinstatement requires written permission from the rights holders whose permissions terminated. Termination of Your permissions does not terminate compliant recipients' direct permissions. Provisions concerning ownership, accrued claims, disclaimers, and construction survive termination.

### 10. Patents

Each Contributor also grants a royalty-free, nonexclusive patent license, subject to these same conditions, for claims it can license that would necessarily be infringed by its contribution alone or by that contribution in the version it supplied. The grant covers making, having made, using, offering for sale, selling, importing, and otherwise transferring those covered implementations for permitted purposes. It does not cover infringement caused solely by later modifications or combinations outside that version.

If You initiate litigation alleging that Covered Software infringes a patent, the patent permissions granted to You by Contributors under this section end. A defensive counterclaim responding to a patent action is excluded from this provision.

### 11. No warranty; liability limits

TO THE EXTENT APPLICABLE LAW PERMITS, COVERED SOFTWARE IS SUPPLIED WITHOUT WARRANTIES, WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING WARRANTIES ABOUT QUALITY, FITNESS FOR A PARTICULAR TASK, TITLE, OR NON-INFRINGEMENT. YOU ARE RESPONSIBLE FOR SELECTING, TESTING, AND OPERATING IT.

TO THAT SAME EXTENT, CONTRIBUTORS ARE NOT LIABLE FOR LOSS OR DAMAGE ARISING FROM THE SOFTWARE OR THIS LICENSE, INCLUDING LOST DATA, REVENUE, BUSINESS, OR OPPORTUNITY, UNDER CONTRACT, TORT, OR ANOTHER LEGAL THEORY. THESE TERMS DO NOT EXCLUDE LIABILITY THAT THE LAW DOES NOT ALLOW TO BE EXCLUDED.

Any paid service, warranty, or support commitment You make is Your responsibility, not another Contributor's.

### 12. Construction and existing rights

This License concerns only the rights and material it expressly covers. It does not restrict fair use, fair dealing, statutory exceptions, independent development, or valid permissions received under another license. Third-party materials retain their separate terms.

If a provision cannot lawfully be enforced, it shall be limited to the minimum extent necessary, with the remainder continuing to apply as far as lawful. No provision selects a mandatory forum or waives nonwaivable statutory rights.

This text controls over an informal summary. Attribution records identify provenance and credits; they cannot add new restrictions or enlarge anyone's rights. An exception must identify its scope and be granted by parties with the required authority. A later license version does not replace these terms for an existing copy without the necessary permissions.
