Lightweight, permissive, clarity‑focused software license.
Authoritative terms are only in the
LICENSEfile. This README is explanatory and non‑binding.
- What is the ICL?
- Quick Start (Copy & Fill In)
- Adoption Steps (Detailed)
- Recommended Notices
- Human Summary of Core Conditions
- Disclaimer & Liability
- Infinite Clause (Longevity)
- Versioning & Future Changes
- FAQ
- Repository Policy (Private)
The Infinite Clause License (ICL) v1.0 (2025) is a permissive license granting broad rights to use, copy, modify, publish, distribute, sublicense, and sell the Software—subject to concise attribution, transparency of modifications, and non‑misrepresentation requirements. It aims to sit in the family of permissive licenses (like MIT / BSD) while explicitly codifying permanence of granted rights (the “Infinite Clause”).
Copy LICENSE into your project root, then replace placeholders:
Infinite Clause License (ICL)
Version 1.0 – 2025
Copyright (c) 2025 YOUR NAME / ORGANIZATION
Optional: Add project URL or contact line beneath the copyright.
Add (optional) source file header:
// Licensed under the Infinite Clause License (ICL) v1.0 (2025). See LICENSE.
- Copy the
LICENSEfile into your repository root. - Replace
[YEAR]with the current year or a range (e.g.2023-2025). - Replace
[AUTHOR/ORGANIZATION]with the legal name you want credited. - (Optional) Add supplemental notices (homepage, email, etc.).
Example README line:
Licensed under the Infinite Clause License (ICL) v1.0 – see LICENSE for details.
Example extended header (for multi‑author projects):
// ProjectX — core engine
// (c) 2024-2025 Alice Example & Contributors
// License: Infinite Clause License (ICL) v1.0 (2025). See LICENSE.
Non‑binding summary (see license text for exact language):
- Attribution: Keep copyright + license text with substantial portions.
- Modification Transparency: If you distribute a modified version, clearly document what changed (separate section or file, e.g.
CHANGES-ICL.md). - Source Clarity: Mark modified code sections or provide clear documentation of divergences.
- No False Endorsement: Don’t imply author or contributor endorsement without prior permission.
- Provided “AS IS” without warranty (express or implied).
- Authors / copyright holders are not liable for any damages or claims.
The granted rights are perpetual and irrevocable; downstream users cannot add extra restrictions. Only original authors may publish new license versions; existing grants under v1.0 remain effective.
- Current: v1.0 (2025).
- If future versions appear, you may (a) stay on v1.0 or (b) explicitly upgrade (your choice unless your own project policy states otherwise).
- To lock a project to this version, state: “This project is licensed solely under the Infinite Clause License (ICL) v1.0 (2025).”
Q: Is this OSI approved?
Not yet (new license). Treat it like any custom permissive license until recognized.
Q: Is it GPL‑compatible?
Practically yes from a copyright perspective (it’s permissive and imposes no copyleft), but always consult legal counsel for dual‑licensing or aggregation scenarios.
Q: Do I need to open source my modifications?
No. Transparency is required only when you distribute modified versions (state what changed), not that you must publish source.
Q: Can I relicense my fork?
You can distribute under additional terms only if they don’t impose new restrictions on the original code; you must retain the original ICL text for the covered portions.
Q: Why a “Source Clarity” clause?
It ensures recipients can distinguish original from altered logic, aiding auditing and trust.
Q: Is the SPDX identifier official?
Not yet; ICL-1.0 is a suggested provisional string.
This private repository auto‑closes issues and pull requests from non‑collaborators. Request collaborator (write) access before opening issues or PRs.
Use the ICL freely, responsibly, and transparently.