chore(license): align with AtelierOS — CLA §3 relicense + trademark n…

CLA.md

@@ -0,0 +1,160 @@
+# AWP — Contributor License Agreement (CLA)
+
+**Version 1.0 — 2026-05-15**
+
+Thank you for contributing to AWP (Agent Workflow Protocol). This
+document is the Contributor License Agreement ("Agreement") between
+you ("Contributor") and Silvio Jurk ("Maintainer",
+`silvio.jurk@gmail.com`).
+
+It is intentionally short. The two clauses that matter are §2 (Outbound
+License) and §3 (Relicense Right). Everything else mirrors industry-
+standard CLAs (Apache Software Foundation ICLA, Google CLA).
+
+By opening a pull request against this repository, by adding a
+`Signed-off-by:` trailer to your commits, or by otherwise intentionally
+submitting work for inclusion in the Project, you accept this Agreement.
+
+---
+
+## 1. Definitions
+
+**"Contribution"** — any original work of authorship intentionally
+submitted for inclusion in the Project, in any form (specification
+text, code, docs, configuration, tests, etc.).
+
+**"Project"** — the AWP source repository at
+`github.com/veegee82/agent-workflow-protocol` (and any future
+successor location) plus all software and specification documents it
+produces.
+
+---
+
+## 2. Outbound License (Apache-2.0)
+
+You license each Contribution to the Maintainer and to every recipient
+of the Project under the **Apache License, Version 2.0** (see the
+[`LICENSE`](LICENSE) file). The copyright and patent grants of Apache
+§§ 2 and 3 apply.
+
+This mirrors Apache § 5 ("inbound = outbound") and would apply even
+without this Agreement. It is restated here for clarity.
+
+---
+
+## 3. Relicense Right (the load-bearing clause)
+
+You additionally grant the Maintainer a **perpetual, worldwide,
+non-exclusive, royalty-free, irrevocable right** to relicense your
+Contribution, in whole or in part, under any of the following:
+
+(a) any license approved by the Open Source Initiative;
+
+(b) any source-available license (Business Source License, Functional
+    Source License, Fair Source License, Elastic License v2, or any
+    license of comparable structure);
+
+(c) a commercial license offered to third parties who cannot or do not
+    wish to comply with the open-source terms.
+
+This right exists so the Maintainer can adapt the Project's license
+to future market conditions (e.g. hyperscaler-clone defence,
+enterprise procurement requirements) without needing to coordinate
+with every past Contributor. **You retain the right to use your own
+Contribution under Apache-2.0 indefinitely.** The relicense right is
+non-exclusive — it grants additional licensing options to the
+Maintainer; it does not strip any rights from you.
+
+A relicense decision does not affect any version of the Project
+already published under Apache-2.0; those releases remain Apache-2.0
+forever. Only future releases would carry the new license, at the
+Maintainer's discretion.
+
+---
+
+## 4. Representations
+
+You represent that:
+
+1. **You are legally entitled to grant the above licenses.** If your
+   employer has rights to intellectual property that includes your
+   Contributions, you have received permission, your employer has
+   waived such rights, or your employer has executed a separate
+   Corporate CLA with the Maintainer.
+
+2. **Each Contribution is your original creation** (or, if not, you
+   submit it separately marked as third-party work with full source
+   and license details).
+
+3. **Your Contribution does not knowingly include patents, trademarks,
+   or other restrictions** that would prevent the licenses in §§ 2–3
+   from being effective.
+
+---
+
+## 5. No Warranty
+
+You provide Contributions on an "AS IS" basis, without warranties of
+any kind, express or implied. The Maintainer is under no obligation
+to integrate, distribute, or otherwise use any Contribution.
+
+---
+
+## 6. How to sign
+
+There is no CLA-bot ceremony. You sign by **any** of these:
+
+- **Opening a pull request** against this repository. Your PR body or
+  description is taken as acceptance.
+- **Adding `Signed-off-by: Your Name <email>` to your commits.** This
+  is the [Developer Certificate of Origin](https://developercertificate.org/)
+  trailer; for this Project it additionally constitutes acceptance of
+  this CLA. `git commit -s` adds it automatically.
+- **A one-line PR comment** of the form
+  `I have read CLA.md and accept its terms.`
+
+One acceptance per contributor is sufficient for all current and
+future Contributions to this Project.
+
+If you wish to revoke a previous acceptance, contact the Maintainer
+at `silvio.jurk@gmail.com`. Note that revocation does not retroact on
+Contributions already merged — the licenses granted on those
+Contributions are irrevocable as stated in §§ 2–3.
+
+---
+
+## 7. Governing law
+
+This Agreement is governed by the laws of the Federal Republic of
+Germany, without regard to its conflict-of-laws provisions. The
+exclusive place of jurisdiction for any disputes arising from or in
+connection with this Agreement is the seat of the Maintainer, to the
+extent legally permissible.
+
+---
+
+## Why this CLA exists (plain-language explanation)
+
+AWP is currently Apache-2.0 for maximal adoption. If in the future a
+major cloud provider clones the Project and offers it as a managed
+service in competition with the Maintainer's own hosted offering, or
+if enterprise procurement requirements call for a commercial-license
+seat, the Maintainer may switch the license of future releases to a
+source-available form (e.g. BSL with a 2-year Apache-2.0 change date —
+the same path Sentry, HashiCorp, and MariaDB MaxScale took).
+
+That move requires the relicense right granted in §3. Without it,
+each past Contributor would need to individually agree, which is
+not feasible at scale. The §3 grant is the optionality you give the
+Maintainer in exchange for the broader stewardship of the Project.
+
+Existing Apache-2.0 releases stay Apache-2.0 forever — your
+Contribution under Apache-2.0 cannot be retracted from versions
+already published. The relicense right only affects future versions.
+
+---
+
+## Historical versions
+
+- **v1.0 — 2026-05-15** (this file) — Apache-2.0 + relicense right.
+  Aligned with the AtelierOS CLA v3.0 model.

CONTRIBUTING.md

@@ -35,6 +35,43 @@ Once the issue has been discussed and the approach is agreed upon:
 4. Ensure all validation checks pass
 5. Submit a pull request referencing the issue
 
+## License and CLA
+
+AWP is licensed under the [Apache License, Version 2.0](LICENSE).
+
+[`CLA.md`](CLA.md) is a short Contributor License Agreement (one page,
+two load-bearing clauses) that mirrors the Apache Software Foundation
+ICLA. Two things to know:
+
+- **§2 (Outbound License):** your contribution is licensed under
+  Apache-2.0 — the same terms as the project itself. This is the same
+  outcome as Apache § 5 ("inbound = outbound").
+- **§3 (Relicense Right):** you additionally grant the Maintainer the
+  non-exclusive right to relicense your contribution under any future
+  OSI-approved or source-available license (e.g. BSL, FSL) for
+  *future* releases of the project. Apache-2.0 versions stay
+  Apache-2.0 forever; you can always use your own contribution under
+  Apache-2.0 indefinitely.
+
+§3 is the optionality clause that lets AWP adapt to future market
+conditions (hyperscaler-clone defence, enterprise procurement)
+without coordinating with every past contributor. The same path
+Sentry, HashiCorp, and MariaDB MaxScale took.
+
+**How to sign:** no bot, no signing ceremony. Opening a PR IS the
+acceptance. Adding `Signed-off-by:` (`git commit -s`) is the cleanest
+audit trail and is encouraged for security-sensitive changes. See
+[`CLA.md`](CLA.md) for the full text and the plain-language
+explanation at the end.
+
+## Trademark
+
+"AWP" and "Agent Workflow Protocol" remain identifiers of the project
+as published by the copyright holder. The Apache License explicitly
+does not grant trademark rights (§ 6). Forks under a different name
+are permitted and welcome; forks marketed under the "AWP" /
+"Agent Workflow Protocol" name are not.
+
 ## Code Style -- Reference Implementation
 
 The reference implementation is written in Python. Follow these conventions:

NOTICE

@@ -4,5 +4,31 @@ Copyright 2026 Silvio Jurk
 This product includes software developed by Silvio Jurk
 and the AWP contributors.
 
-Licensed under the Apache License, Version 2.0.
-See LICENSE for the full license text.
+Licensed under the Apache License, Version 2.0 (see LICENSE).
+
+────────────────────────────────────────────────────────────────────────
+
+Trademark notice
+────────────────
+
+"AWP" and "Agent Workflow Protocol" are the project names used by the
+copyright holder to identify this software. The Apache License does
+not grant permission to use the trade names, trademarks, service
+marks, or product names of the licensor, except as required for
+describing the origin of the Work and reproducing the content of this
+NOTICE file (see License § 6).
+
+Forks intended for redistribution under a different name remain
+permitted by the License; the trademark restriction only prevents
+unauthorized use of the "AWP" / "Agent Workflow Protocol" identifier
+to brand derivative or third-party products.
+
+────────────────────────────────────────────────────────────────────────
+
+Third-party components
+──────────────────────
+
+This software depends on third-party components distributed under
+their own licenses. Each package retains its upstream license; see
+the dependency manifests under reference/ (per language) for the
+canonical inventory.