TASL v1.1 – The Patchwork Update

Release Notes: TASL v1.1 (The Patchwork Update)

This is the second official release of the Transparent & Attributed Source License (TASL). Version 1.1 focuses on closing compliance loopholes, formalizing contributor protections, and making the license legally bulletproof against jurisdiction-level workarounds.

Purpose

While v1.0 successfully identified modern threats like AI models and SaaS distributions, careful inspection in revealed areas where sophisticated actors could bypass attribution obligations or exploit corporate loopholes. This update patches those gaps, ensuring that the spirit of transparency remains unbroken across complex multi-tier network applications and unexpected judicial overrides.

Key Features in v1.1

• Airtight Severability ("Failure of Condition"): Fixes a critical missing element in v1.0. If a court or licensee uses local laws to declare your AI, SaaS, or Attribution requirements unenforceable, the entire grant of rights is revoked immediately and retroactively. Licensees cannot use courts to strip your conditions while keeping your code for free.

• Multi-Tier SaaS Protection: Clarifies how component swapping operates in a network environment (SaaS) and patches a major loophole where backend API providers could ignore user-facing GUI attribution requirements.

• Adaptive Attribution Rules: Replaces the subjective "reasonable number of interactions" from v1.0 with a strict 3-click maximum for GUIs, while providing clear, explicit compliance paths for headless environments (command-line flags, API reference logs, or documentation headers).

• Robust Patent Non-Assertion: Dramatically scales up the basic v1.0 patent clause into a comprehensive cross-licensing defense. It establishes lifelong protection for downstream contributors and ensures that anyone initiating patent litigation instantly drops all rights to the software.

• Active Notice Requirement: Upgrades the "Self-Healing" mechanic. The 30-day cure period now triggers explicitly upon receiving formal notice of a violation, preventing bad actors from claiming they simply "weren't aware" of their non-compliance to stall enforcement.

• Governance Formalization: Explicitly links license stewardship and official updates to the TASL Foundation repository and official channels to prevent malicious third-party compliance forks.

How to Use

1. Download v1.1.md.

2. Rename it to LICENSE.md and replace the older version or include it in your repository.

3. Optionally add a mention in your README.md

TASL v1.0 – Initial Release

Release Notes: TASL v1.0 (Initial Release)

This is the first official release of the Transparent & Attributed Source License (TASL).

Purpose

Traditional licenses like the GPL were written before the rise of Cloud Computing (SaaS) and Large Language Models (AI). TASL ensures that if your logic is "borrowed" by a machine or hidden inside a proprietary container, the original creator still receives the credit and transparency they deserve.

Key Features in v1.0

• AI Protection: Explicitly defines AI training as a usage that requires project attribution in model metadata.

• Structural Derivative Clause: Protects logic and architectural patterns even if the code is rewritten in a different programming language.

• Linking Pragmatism: Allows static linking in commercial/closed-source contexts if the build process is documented and the component is user-swappable.

• SaaS Clause: Closes the "Cloud Loophole" by requiring source disclosure for network-accessed modifications.

• Self-Healing: Includes a 30-day "Cure Period" to fix accidental license violations without immediate legal termination.

• Author’s Prerogative: Grants the original author the right to relicense the main project while keeping forks protected under the TASL ecosystem.

How to Use

1. Download v1.0.md.

2. Rename it to LICENSE.md and include it in your repository.

3. Optionally add a mention in your README.md