From 6bd4b6831da29eb6c679635daf77806eaceff258 Mon Sep 17 00:00:00 2001 From: Alex Reznichenko Date: Sun, 22 Nov 2026 16:07:16 +0100 Subject: [PATCH 01/20] legal: contributor agreement v2.0 transition note This document outlines the transition from Contributor Agreement version 1.1 to version 2.0, detailing changes in ownership and licensing terms, as well as steps for activation and post-activation procedures. Signed-off-by: Alex Reznichenko --- CLA_TRANSITION_v2.0.md | 36 ++++++++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 CLA_TRANSITION_v2.0.md diff --git a/CLA_TRANSITION_v2.0.md b/CLA_TRANSITION_v2.0.md new file mode 100644 index 0000000..fba7fed --- /dev/null +++ b/CLA_TRANSITION_v2.0.md @@ -0,0 +1,36 @@ +# Contributor agreement transition to version 2.0 + +Status on 22 November 2026: version 2.0 texts approved in direction by the owner and prepared for review. **Not activated.** The live status is the table in [CLA.md](CLA.md). + +## What changes + +Version 1.1 assigns transferable economic rights in accepted contributions to Botshare LTD. Under version 2.0 the contributor keeps ownership and grants Botshare LTD a non-exclusive, worldwide, perpetual, irrevocable, royalty-free, transferable and sublicensable licence, with patent rights, for any purpose. The public project licences do not change. + +## What does not change + +- Contributions accepted under version 1.1 stay assigned. This transition reverses nothing. +- DCO sign-off on every commit. +- Outbound licences: MIT, CERN-OHL-P-2.0, CC BY 4.0. + +## Before activation + +1. Legal review by Cyprus-qualified intellectual property counsel of: enforceability and irrevocability of the licence, the patent licence and its termination clause, contributors under 18 and the guardian consent, and the effect on version 1.1 assignments (including whether click-through assignments were valid, and the fallback licence). +2. Written approval of the final texts by Botshare LTD's director. +3. The activation steps in [CLA.md](CLA.md), in order. No contributor is treated as covered by version 2.0 before a CLA Assistant record of that contributor's acceptance exists, dated on or after the activation date. + +## At activation + +1. Notify contributors: what changes, that earlier contributions stay under version 1.1, and that the next pull request asks for a new acceptance. +2. Send organizations with a signed version 1.1 corporate agreement the version 2.0 corporate agreement for signature. Each stays under version 1.1 until both parties have signed. +3. Obtain guardian consent for every contributor under 18 before merging further work from them, with the box for earlier contributions ticked where they have any. +4. Recheck every open external pull request. A pull request whose author has not accepted version 2.0 is not merged, unless Botshare LTD decides and records that it merges under version 1.1 with the author's agreement. +5. Update the contribution, licensing and notice files in the other OpenAMRobot repositories that still describe assignment only. + +## After activation + +- Do not switch CLA Assistant back to version 1.1. Correct a non-material error as 2.0.1; a material change is a new version that needs acceptance. +- One month later, reconcile the CLA Assistant export with merged pull requests and record any gap. + +## Separate from this agreement + +People who work for Botshare LTD for pay, as employees or contractors, are covered by their own written agreements with Botshare LTD, not by the contributor agreement. From 7617ecf2a1154697f1b0b5c67997189f1acc3730 Mon Sep 17 00:00:00 2001 From: Alex Reznichenko Date: Sun, 22 Nov 2026 16:08:00 +0100 Subject: [PATCH 02/20] legal: align DCO note with contributor agreement v2.0 Clarify the distinction between DCO and contributor agreement, and update copyright transfer language. Signed-off-by: Alex Reznichenko --- DCO.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/DCO.md b/DCO.md index c25a4e5..b4cd79c 100644 --- a/DCO.md +++ b/DCO.md @@ -27,8 +27,8 @@ Signed-off-by: Legal Name The name must identify the contributor and the email must be controlled by them. All commits in a pull request, including web edits and commits added after review, must pass the DCO check. -## DCO and assignment are separate +## DCO and the contributor agreement are separate -DCO confirms provenance and authority to contribute. It does **not** transfer copyright. Assignment of transferable economic rights in accepted contributions is governed by the applicable OpenAMRobot Contributor Agreement. +DCO confirms provenance and authority to contribute. It does **not** transfer or license copyright. Rights in accepted contributions are governed by the contributor agreement version the contributor accepted: a licence to Botshare LTD under version 2.0, an assignment under version 1.1. See [CLA.md](CLA.md). A pull request cannot be accepted while its DCO or Contributor Agreement requirement is unsatisfied. From 2d558acdc72ab86d37dc11b2873b144797a9a114 Mon Sep 17 00:00:00 2001 From: Alex Reznichenko Date: Sun, 22 Nov 2026 16:08:28 +0100 Subject: [PATCH 03/20] legal: align NOTICE with contributor agreement v2.0 Signed-off-by: Alex Reznichenko --- NOTICE.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/NOTICE.md b/NOTICE.md index a404e5a..7eb3998 100644 --- a/NOTICE.md +++ b/NOTICE.md @@ -5,13 +5,13 @@ OpenAMRobot is a project initiated, operated, and controlled by: **Botshare LTD** Company ID: HE479056 VAT: 60197356L -Chrysanthou Mylona 1, Panayides Building, Office 1 +Chrysanthou Mylona 1, Panayides Building, Floor 2, Office 1 3030 Limassol, Cyprus info@botshare.ai · https://botshare.ai -Copyright and transferable economic rights in original OpenAMRobot materials are owned by Botshare LTD or used by it under applicable agreements. +Original OpenAMRobot materials are owned by Botshare LTD, were assigned to it, or are licensed to it by their contributors under the OpenAMRobot contributor agreements with the right to sublicense. -Accepted external contributions are governed by the OpenAMRobot Contributor Agreement. Contributor attribution, legally non-waivable authorship or moral rights, and authentic third-party notices remain recognized. +Accepted external contributions are governed by the contributor agreement version their contributor accepted ([CLA.md](CLA.md)). Contributors who accepted version 2.0 keep ownership of their contributions. Contributor attribution, legally non-waivable authorship or moral rights, and authentic third-party notices remain recognized. Botshare LTD does not claim ownership of third-party materials. Each repository or file may contain additional licence and attribution notices that control that material. From 363fe26f004701e8b29e8978ac1097ee804ed5ad Mon Sep 17 00:00:00 2001 From: Alex Reznichenko Date: Sun, 22 Nov 2026 16:08:53 +0100 Subject: [PATCH 04/20] legal: align organization profile with contributor agreement v2.0 Signed-off-by: Alex Reznichenko --- profile/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/profile/README.md b/profile/README.md index e06cdea..b72dfa0 100644 --- a/profile/README.md +++ b/profile/README.md @@ -514,14 +514,14 @@ What 2.0 brings: ## Licensing, ownership, and contributions -OpenAMRobot is a project of **Botshare LTD**. Botshare LTD owns the transferable economic rights in original OpenAMRobot materials created by or validly assigned to it. Third-party materials remain subject to their respective owners, licences, and notices. +OpenAMRobot is a project of **Botshare LTD**. Botshare LTD owns the original OpenAMRobot materials it created or that were assigned to it, and holds a permanent, sublicensable licence to contributions whose authors keep ownership. Third-party materials remain subject to their respective owners, licences, and notices. Public availability under MIT or another applicable open-source or open-hardware licence grants the permissions stated in that licence; it does not transfer ownership of underlying copyright, trademarks, patents, or other intellectual property. Accepted external contributions require: 1. DCO sign-off for every commit; and -2. an accepted Individual or Corporate Contributor Agreement governing assignment of transferable economic rights to Botshare LTD. +2. a recorded Individual or Corporate contributor agreement. Under version 2.0 contributors keep ownership and license Botshare LTD; contributions accepted under version 1.1 were assigned. Contributor attribution and legally non-waivable authorship or moral rights remain recognized. From e638d92f3050492ab8b50781970bcc4a200ecc29 Mon Sep 17 00:00:00 2001 From: Alex Reznichenko Date: Sun, 22 Nov 2026 16:09:19 +0100 Subject: [PATCH 05/20] legal: align LICENSING with contributor agreement v2.0 Signed-off-by: Alex Reznichenko --- LICENSING.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/LICENSING.md b/LICENSING.md index e83a9a4..42deb68 100644 --- a/LICENSING.md +++ b/LICENSING.md @@ -1,14 +1,15 @@ # OpenAMRobot licensing standard -OpenAMRobot uses asset-appropriate permissive licences for original material owned by or validly assigned to **OpenAMRobot (Botshare LTD)**. +OpenAMRobot uses asset-appropriate permissive licences for original material that **Botshare LTD** owns, that was assigned to it, or that contributors license to it under the [contributor agreements](CLA.md) with the right to sublicense. | Material | Licence | |---|---| | Software, firmware, scripts, configuration, APIs, tests, and code examples | [MIT](https://spdx.org/licenses/MIT.html) | | Documentation, diagrams, tutorials, original images, and other authored content | [Creative Commons Attribution 4.0 International](https://spdx.org/licenses/CC-BY-4.0.html) | | CAD, PCB and schematic source, mechanical/electrical design files, manufacturing source, and CAD-derived robot geometry | [CERN Open Hardware Licence Version 2 — Permissive](https://spdx.org/licenses/CERN-OHL-P-2.0.html) | +| Datasets, recordings, simulation assets, AI models and weights | Stated per asset after individual review. Default: CC BY 4.0 for suitable datasets, MIT for models and weights. See the [Third-Party Material Policy](THIRD_PARTY_POLICY.md). | -Copyright (c) 2021–2026 OpenAMRobot (Botshare LTD). +Copyright (c) 2021–2026 OpenAMRobot (Botshare LTD) and OpenAMRobot contributors. The root `LICENSE` identifies the predominant licence for this repository. Where a repository contains several asset types, the table above and any more specific file, directory, SPDX, package, or notice declaration determine the applicable licence. @@ -18,7 +19,7 @@ No OpenAMRobot licence relicenses third-party material. Third-party material rem ## Ownership and branding -Public licensing grants the permissions in the applicable licence; it does not transfer ownership of the underlying intellectual property. OpenAMRobot, OpenAMR, associated logos, visual identity, and claims of official affiliation or certification are not licensed under MIT, CC BY 4.0, or CERN-OHL-P-2.0. See the organization [Trademark Policy](https://github.com/openAMRobot/.github/blob/main/TRADEMARK_POLICY.md). +Public licensing grants the permissions in the applicable licence; it does not transfer ownership of the underlying intellectual property. Botshare LTD may also offer the same material under other terms, including proprietary terms, as the contributor agreements allow. OpenAMRobot, OpenAMR, associated logos, visual identity, and claims of official affiliation or certification are not licensed under MIT, CC BY 4.0, or CERN-OHL-P-2.0. See the organization [Trademark Policy](https://github.com/openAMRobot/.github/blob/main/TRADEMARK_POLICY.md). ## Earlier distributions From 2a61c981ecef106785ec2556dde7d072c3f45e25 Mon Sep 17 00:00:00 2001 From: Alex Reznichenko Date: Sun, 22 Nov 2026 16:09:39 +0100 Subject: [PATCH 06/20] legal: align GOVERNANCE with contributor agreement v2.0 Signed-off-by: Alex Reznichenko --- GOVERNANCE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index e5d0c10..2beb39c 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -16,7 +16,7 @@ Maintainer status grants operational authority only. It does not transfer owners Contributors may propose changes through issues, discussions, and pull requests. Contributions must comply with [CONTRIBUTING.md](CONTRIBUTING.md), [DCO.md](DCO.md), [CLA.md](CLA.md), the applicable repository licence, and all third-party notices. -Transferable economic rights in accepted external contributions are governed by the applicable Contributor Agreement. Attribution and legally applicable authorship or moral rights remain recognized. +Rights in accepted external contributions are governed by the contributor agreement version the contributor accepted ([CLA.md](CLA.md)): contributors keep ownership and license Botshare LTD under version 2.0; version 1.1 assigned transferable economic rights. Attribution and legally applicable authorship or moral rights remain recognized. ## Decisions From d9bb38f5362691603b13426f66fa3435cbea11a7 Mon Sep 17 00:00:00 2001 From: Alex Reznichenko Date: Sun, 22 Nov 2026 16:09:52 +0100 Subject: [PATCH 07/20] legal: align README with contributor agreement v2.0 Signed-off-by: Alex Reznichenko --- README.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index ef7e296..fb569a9 100644 --- a/README.md +++ b/README.md @@ -57,8 +57,11 @@ The ecosystem encourages open-source collaboration, education, research, and ind - [IP Policy](IP_POLICY.md) - [Contributor Agreement Process](CLA.md) - [Contributor Agreement Recordkeeping](CLA_RECORDKEEPING.md) -- [Individual Contributor Agreement](INDIVIDUAL_CONTRIBUTOR_AGREEMENT.md) -- [Corporate Contributor Agreement](CORPORATE_CONTRIBUTOR_AGREEMENT.md) +- [Individual Contributor License Agreement 2.0](INDIVIDUAL_CONTRIBUTOR_LICENSE_AGREEMENT.md) +- [Corporate Contributor License Agreement 2.0](CORPORATE_CONTRIBUTOR_LICENSE_AGREEMENT.md) +- [Guardian Consent for contributors under 18](MINOR_CONTRIBUTOR_GUARDIAN_CONSENT.md) +- [Individual Contributor Agreement 1.1](INDIVIDUAL_CONTRIBUTOR_AGREEMENT.md) +- [Corporate Contributor Agreement 1.1](CORPORATE_CONTRIBUTOR_AGREEMENT.md) - [Trademark Policy](TRADEMARK_POLICY.md) ## Security & Support @@ -109,7 +112,7 @@ OpenAMRobot encourages contributions from: - educators, - industrial partners. -OpenAMRobot is operated by **Botshare LTD**. Accepted external contributions require DCO sign-off and an applicable Contributor Agreement assigning transferable economic rights to Botshare LTD. Accepted project material is distributed under the applicable repository or file licence. Authorship, attribution, non-waivable moral rights, and third-party rights remain recognized as required. +OpenAMRobot is operated by **Botshare LTD**. Accepted external contributions require DCO sign-off and a recorded contributor agreement ([CLA.md](CLA.md)). Under version 2.0 contributors keep ownership and grant Botshare LTD a permanent, royalty-free, sublicensable licence; contributions accepted under version 1.1 were assigned to Botshare LTD. Accepted project material is distributed under the applicable repository or file licence. Authorship, attribution, non-waivable moral rights, and third-party rights remain recognized as required. --- From 7de8564bd0a22ab4e41290285d3181d7a23e747f Mon Sep 17 00:00:00 2001 From: Alex Reznichenko Date: Sun, 22 Nov 2026 16:10:28 +0100 Subject: [PATCH 08/20] legal: define material AI assistance and its disclosure Signed-off-by: Alex Reznichenko --- AI_CONTRIBUTION_POLICY.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/AI_CONTRIBUTION_POLICY.md b/AI_CONTRIBUTION_POLICY.md index c3c8272..ae66e89 100644 --- a/AI_CONTRIBUTION_POLICY.md +++ b/AI_CONTRIBUTION_POLICY.md @@ -4,7 +4,8 @@ AI tools may assist OpenAMRobot work, but the human contributor remains responsi A contributor must: -- disclose material generative-AI assistance in the pull request; +- disclose material generative-AI assistance in the pull request description: which parts, which tool, and that the contributor reviewed and tested them. Assistance is material when a tool generated a substantial part of the code, text, design or data; autocomplete, spelling and formatting aids are not. Per-commit tool trailers are not required; +- confirm that the tool's terms allow the output to be submitted and licensed under the contributor agreement; - review output for correctness, safety, security, licence compatibility, provenance, and substantial similarity; - confirm authority to submit all prompts, inputs, references, and outputs; - avoid entering confidential information, personal data, credentials, client material, unpublished inventions, or restricted source into an AI service; From 4aa660e648ee89271113358c11310232c06f3967 Mon Sep 17 00:00:00 2001 From: Alex Reznichenko Date: Sun, 22 Nov 2026 16:10:40 +0100 Subject: [PATCH 09/20] legal: record agreement version, coverage start and guardian consent Signed-off-by: Alex Reznichenko --- CLA_RECORDKEEPING.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/CLA_RECORDKEEPING.md b/CLA_RECORDKEEPING.md index e4e4409..ce27be3 100644 --- a/CLA_RECORDKEEPING.md +++ b/CLA_RECORDKEEPING.md @@ -8,14 +8,17 @@ For each contributor, record privately: - legal name and verified contact email; - GitHub username and, where applicable, employer or represented entity; -- agreement type (ICLA or CCLA), exact version, acceptance method, and acceptance timestamp; +- agreement type (ICLA or CCLA), document identifier and exact version, acceptance method, and acceptance timestamp; +- for a contributor under 18, that guardian consent is on record and its date (the form itself and the date of birth stay in the private file only); - CCLA signatory authority and the covered contributor list; - repository, pull request number, and accepted commit hashes; - disclosed Background IP, third-party material, AI assistance, employer, university, client, sponsor, or co-author permissions; - accepting maintainer and merge timestamp; and - any exception, withdrawal, superseding agreement, or legal follow-up. -Export CLA Assistant acceptance records regularly and retain them with the immutable agreement version that the contributor accepted. Restrict access to authorized Botshare LTD personnel and apply the Contributor Privacy Notice and applicable retention requirements. +A contributor's coverage under a version starts at the recorded acceptance time of that version, never earlier. When a contributor moves from version 1.1 to version 2.0, keep both records: contributions accepted before the version 2.0 acceptance time stay under version 1.1. + +Export CLA Assistant acceptance records regularly, and always before the organization-wide agreement is switched to a new version, and retain them with the immutable agreement version that the contributor accepted. Restrict access to authorized Botshare LTD personnel and apply the Contributor Privacy Notice and applicable retention requirements. DCO status and Git history support provenance but do not replace the Contributor Agreement record. From 18680dcbb80d13768d2fde7430edcd4b95660d9c Mon Sep 17 00:00:00 2001 From: Alex Reznichenko Date: Sun, 22 Nov 2026 16:10:51 +0100 Subject: [PATCH 10/20] legal: add licence-compatibility and asset-card items to the PR template Signed-off-by: Alex Reznichenko --- .github/PULL_REQUEST_TEMPLATE.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index c26fda4..97b94b4 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -67,6 +67,7 @@ platform lead. Telemetry and fixtures are not safety evidence. --> - [ ] Every commit is signed off under the [DCO](https://github.com/openAMRobot/.github/blob/main/DCO.md). - [ ] I am covered by an accepted [Contributor Agreement](https://github.com/openAMRobot/.github/blob/main/CLA.md). -- [ ] Third-party material is identified with source and licence. +- [ ] Third-party and background material is identified with source and licence, and nothing included or required is under non-commercial, copyleft or other restricted terms ([policy](https://github.com/openAMRobot/.github/blob/main/THIRD_PARTY_POLICY.md)). +- [ ] Any dataset, simulation asset, model or weights comes with its provenance card. - [ ] No confidential, personal, credential or export-controlled information is included. - [ ] No partner, customer or private person is named; the application is Use_Case_1. From 679b53e4dc2cf038ba0c199413e00add053f3ddb Mon Sep 17 00:00:00 2001 From: Alex Reznichenko Date: Sun, 22 Nov 2026 16:11:58 +0100 Subject: [PATCH 11/20] legal: privacy notice 1.1 (CLA Assistant, acceptance fields, guardian consent) Signed-off-by: Alex Reznichenko --- CONTRIBUTOR_PRIVACY_NOTICE.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/CONTRIBUTOR_PRIVACY_NOTICE.md b/CONTRIBUTOR_PRIVACY_NOTICE.md index a247b84..e5e5708 100644 --- a/CONTRIBUTOR_PRIVACY_NOTICE.md +++ b/CONTRIBUTOR_PRIVACY_NOTICE.md @@ -1,8 +1,8 @@ # OpenAMRobot Contributor Privacy Notice -**Version:** 1.0 — 29 August 2026 +**Version:** 1.1 — 22 November 2026 -This notice explains how **Botshare LTD** (Company ID HE479056), Chrysanthou Mylona 1, Panayides Building, Office 1, 3030 Limassol, Cyprus (“Botshare”, “we”), processes personal data relating to OpenAMRobot contributors. +This notice explains how **Botshare LTD** (Company ID HE479056), Chrysanthou Mylona 1, Panayides Building, Floor 2, Office 1, 3030 Limassol, Cyprus (“Botshare”, “we”), processes personal data relating to OpenAMRobot contributors. Contact: info@botshare.ai. @@ -12,7 +12,8 @@ We may process: - legal name, signature, address, country, email, and professional affiliation; - GitHub usernames, commit identity, pull requests, reviews, and contribution history; -- agreement type, version, execution and acceptance dates; +- agreement type, version, execution and acceptance dates, and the fields entered at electronic acceptance; +- for a contributor under 18: the guardian's name, relationship and contact details, the contributor's date of birth, and the signed guardian consent; - employer or organizational authorization and Authorized Contributor status; - disclosed provenance, third-party rights, and contribution-related correspondence; and - records needed to establish, exercise, or defend legal claims. @@ -32,7 +33,7 @@ Providing data required to execute an agreement is contractual. Without it, Bots ## Sources and recipients -Data is obtained from the contributor, the contributor’s organization, public GitHub records, and contribution communications. It may be disclosed only as reasonably necessary to Botshare personnel and service providers, professional advisers, courts, regulators, counterparties in due diligence or a corporate transaction subject to appropriate safeguards, and the public where the contributor deliberately publishes data through GitHub. +Data is obtained from the contributor, the contributor’s organization, public GitHub records, and contribution communications. Electronic acceptance of the Individual agreement is collected through CLA Assistant (cla-assistant.io), which receives the GitHub identity, the accepted document and the acceptance time. Data may be disclosed only as reasonably necessary to Botshare personnel and service providers, professional advisers, courts, regulators, counterparties in due diligence or a corporate transaction subject to appropriate safeguards, and the public where the contributor deliberately publishes data through GitHub. ## International transfers @@ -42,7 +43,9 @@ GitHub and other service providers may process data outside the EEA. Botshare wi Public Git and contribution records may remain available indefinitely as part of the project’s technical and authorship history. -Executed agreements, authority records, and chain-of-title evidence are retained for the life of the relevant intellectual-property rights and thereafter for the period reasonably necessary to establish, exercise, or defend claims, subject to applicable limitation periods and legal obligations. Data not needed for these purposes will be deleted or anonymized. +Executed agreements, authority records, and chain-of-title evidence are retained for the life of the relevant intellectual-property rights and thereafter for the period reasonably necessary to establish, exercise, or defend claims, subject to applicable limitation periods and legal obligations. Data not needed for these purposes will be deleted or anonymized. A date of birth supplied on a guardian consent is deleted once the contributor has accepted the agreement personally as an adult. + +A residential address is not collected for electronic acceptance. ## Rights From 2eca89fa76e2159f4f9a05380d48b827595fc995 Mon Sep 17 00:00:00 2001 From: Alex Reznichenko Date: Sun, 22 Nov 2026 16:12:37 +0100 Subject: [PATCH 12/20] legal: align CONTRIBUTING with contributor agreement v2.0 Signed-off-by: Alex Reznichenko --- CONTRIBUTING.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index bb0cac5..a0d5041 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -34,7 +34,7 @@ are in [AGENTS.md](AGENTS.md). ## 2. Set up -1. Sign the contributor agreement once: see [CLA.md](CLA.md). +1. Accept the contributor agreement: see [CLA.md](CLA.md). Contributors under 18 need the guardian consent described there first. 2. Fork the repository and create **one branch per work package**. 3. Sign off every commit: `git commit -s`. The sign-off certifies the [DCO](DCO.md) with your own name and e-mail. @@ -108,8 +108,7 @@ A maintainer merges; approval or a green check alone does not accept a contribut ## Legal, conduct and contact Contributions are governed by the [IP Policy](IP_POLICY.md), the -[Individual](INDIVIDUAL_CONTRIBUTOR_AGREEMENT.md) or -[Corporate](CORPORATE_CONTRIBUTOR_AGREEMENT.md) Contributor Agreement, the +contributor agreement version you accepted ([CLA.md](CLA.md)), the [AI contribution policy](AI_CONTRIBUTION_POLICY.md) and the [third-party policy](THIRD_PARTY_POLICY.md). Identify any material you did not create yourself with its source and licence. Do not submit secrets, personal data or confidential From 63c6e258552d50a21fe471836bfe6eb7d463c0ba Mon Sep 17 00:00:00 2001 From: Alex Reznichenko Date: Sun, 22 Nov 2026 16:12:50 +0100 Subject: [PATCH 13/20] state: record contributor agreement 2.0 work Signed-off-by: Alex Reznichenko --- STATE.md | 1 + 1 file changed, 1 insertion(+) diff --git a/STATE.md b/STATE.md index ba5ebae..d1714a2 100644 --- a/STATE.md +++ b/STATE.md @@ -27,6 +27,7 @@ The PR evidence check fails when STATE.md exists and a PR neither updates it nor | Decisions of 3 Nov 2026 | #85 | merged as dafab0e (2026-11-04) | owner review: K1/K2 GX11CAC decided, rear power module, BMS side gap, FB-A/FB-B, receiver 15 mm gap, flag rod guide | | P-03 rev20.4 (decisions of 8 Nov 2026) | decisions/2026-11-08-owner-decisions | open for owner review (2026-11-08) | owner review: in_force P-03-rev20.4, ZX80 55 mm lower, head camera 60 mm, receiver frame (no metal within 20 mm of the sides, 15 mm above), DOLD CAD, arch backing plate, new WIRING-ROUTING (slot defined, two lift cable openings, scoped check after review), P-03 rev20.6 item 30: LIFT fixing through the foot tabs 260 x 30 mm (D-20) and backing plate (D-21), COMPUTE Orin NX 8 GB on the Robotics 104 (D-01); review of 9 Nov 2026 (2026-11-10): one P-03-rev20.6 source, duplicate YAML keys rejected by the loader, WIRING-ROUTING cover-slot matcher narrowed (unless read per sentence), slot geometry enforced by openamrobot-docs slot_rule.py, BOM 7.15 recorded as the roadmap extract source, ROADMAP.md compute | | #83 | #84 | merged as 5ed600e (2026-11-02) | none; the 2 Nov 2026 values are in force | +| Contributor agreement 2.0 | #93 (legal/contributor-retained-rights-v2-proposal) | texts and policy alignment prepared for review (2026-11-22); not activated, CLA Assistant still presents 1.1 | Cyprus IP counsel review, director approval, then the activation steps in CLA.md | | PLATFORM-PIN | #74 | pin 131e500fc4e5afc9f648cbd7dbf5b416280761fb (2.0 base, P-03 rev20.1 item 25 D7), validated by openamr-upperbody-sw #21; merged with this PR (2026-11-01) | none; touches decisions.yaml only | ## Decisions this repository implements From 75796c3e82450b19e7a7954e6ad3995abd5b3f98 Mon Sep 17 00:00:00 2001 From: Alex Reznichenko Date: Sun, 22 Nov 2026 16:13:16 +0100 Subject: [PATCH 14/20] legal: align IP policy with contributor agreement v2.0 Signed-off-by: Alex Reznichenko --- IP_POLICY.md | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-) diff --git a/IP_POLICY.md b/IP_POLICY.md index e09f120..45bddce 100644 --- a/IP_POLICY.md +++ b/IP_POLICY.md @@ -6,7 +6,7 @@ OpenAMRobot is initiated, operated, and controlled by **Botshare LTD**, a Cyprus - Company ID: HE479056 - VAT: 60197356L -- Address: Chrysanthou Mylona 1, Panayides Building, Office 1, 3030 Limassol, Cyprus +- Address: Chrysanthou Mylona 1, Panayides Building, Floor 2, Office 1, 3030 Limassol, Cyprus - Email: info@botshare.ai - Website: https://botshare.ai @@ -14,22 +14,25 @@ The `openAMRobot` GitHub organization is infrastructure operated by Botshare LTD ## 2. Ownership and licensing -Botshare LTD owns the rights in original OpenAMRobot material created by it and rights validly assigned to it. This includes, where applicable, transferable copyright and related economic rights, database and design rights, contribution-specific invention rights, project know-how, branding, and contractual rights. +Botshare LTD owns the rights in original OpenAMRobot material created by it, its employees and contractors, and rights validly assigned to it, including contributions accepted under contributor agreement version 1.1. It also owns its own modifications of contributed material, technology it develops independently, and the selection and arrangement of the project as a whole. This includes, where applicable, transferable copyright and related economic rights, database and design rights, contribution-specific invention rights, project know-how, branding, and contractual rights. This statement does not claim: - legally non-transferable authorship, inventorship, or moral rights; - third-party rights; +- ownership of contributions accepted under contributor agreement version 2.0, which stays with the contributor; - contributor rights not validly assigned under an executed agreement; or - rights that mandatory law reserves to employees, inventors, consumers, or other persons. +For contributions accepted under contributor agreement version 2.0, Botshare LTD holds a non-exclusive, worldwide, perpetual, irrevocable, royalty-free, transferable and sublicensable licence, including patent rights, for any purpose, including manufacturing and proprietary products. Botshare LTD, its manufacturers, distributors, customers, successors and acquirers need no further permission from a contributor and owe no royalty. + Public distribution under MIT or another applicable licence grants the permissions stated in that licence. It does not transfer ownership of underlying intellectual property. Existing open-source grants for copies already distributed remain governed by their applicable terms. ## 3. Company and contributor Background IP “Background IP” is material developed or acquired independently of a contribution and identified before acceptance. Botshare LTD retains all rights in its Background IP, including private designs, trade secrets, confidential information, proprietary tooling, commercial know-how, unreleased roadmaps, credentials, customer material, manufacturing data, and non-public datasets. -Contributors retain their properly disclosed Background IP, subject only to the licence expressly granted under the applicable Contributor Agreement where necessary to use an Accepted Contribution. +Contributors retain their properly disclosed Background IP. Background IP that is included in an Accepted Contribution is licensed to Botshare LTD in full under the applicable contributor agreement, with no added restriction; if those rights cannot be granted, the material is left out or covered by a separate written agreement signed by Botshare LTD before acceptance. No public repository may contain Company or third-party confidential information without documented authorization. @@ -46,12 +49,12 @@ No contributor may submit material they are not authorized to disclose or licens An external contribution may be accepted only when: 1. every commit satisfies the [Developer Certificate of Origin](DCO.md); -2. the contributor is covered by a recorded electronic acceptance of the [Individual](INDIVIDUAL_CONTRIBUTOR_AGREEMENT.md) or an executed [Corporate](CORPORATE_CONTRIBUTOR_AGREEMENT.md) Contributor Agreement; +2. the contributor is covered by a recorded electronic acceptance of the Individual agreement, or an executed Corporate agreement, in the version in force for that contributor under [CLA.md](CLA.md), and, for a contributor under 18, by a guardian consent on record; 3. required employer, university, client, sponsor, co-author, joint-inventor, or institutional permissions are documented; -4. third-party, Background, and materially AI-assisted material is disclosed; and +4. third-party, Background, and materially AI-assisted material is disclosed, and third-party material and dependencies meet the commercial compatibility rules of the [Third-Party Material Policy](THIRD_PARTY_POLICY.md); and 5. mandatory reviews and status checks pass. -The applicable recorded Contributor Agreement—not the DCO, repository location, or merge alone—governs assignment and licensing of contributor rights. +The applicable recorded Contributor Agreement—not the DCO, repository location, or merge alone—governs the licensing or assignment of contributor rights. A Contribution becomes an “Accepted Contribution” only when an authorized maintainer merges it into an official repository or Botshare LTD expressly confirms acceptance in writing. @@ -65,7 +68,7 @@ This policy is prospective and does not itself alter historical rights. Botshare - **Original documentation, diagrams, tutorials, images, and educational content:** CC BY 4.0. - **Original hardware source, CAD, PCB and schematic source, manufacturing source, and CAD-derived robot geometry:** CERN-OHL-P-2.0. - **Third-party or derivative material:** applicable upstream licence; no unauthorized relicensing. -- **Datasets and AI models:** no implied licence; each asset requires explicit terms and provenance. +- **Datasets, recordings, simulation assets, AI models and weights:** no implied licence; each asset is reviewed individually and requires explicit terms and provenance. Default public licences are CC BY 4.0 for suitable datasets and MIT for models and weights; no asset may carry non-commercial or other restricted terms from third-party training data, weights or assets. - **Logos, names, and brand assets:** excluded from software, content, and hardware licences unless expressly stated. - **Confidential or proprietary material:** not published in public repositories and not licensed by implication. @@ -95,7 +98,7 @@ Required contribution checks must not be bypassed except through a documented, t ## 10. Governing hierarchy -For a specific Contribution, the signed Contributor Agreement controls assignment and inbound licensing. The applicable repository or file licence controls outbound public permissions. A third-party licence controls the corresponding third-party material. This policy governs project administration and does not override mandatory law or an executed agreement. +For a specific Contribution, the contributor agreement version accepted by that contributor controls inbound rights (licence under version 2.0, assignment under version 1.1). The applicable repository or file licence controls outbound public permissions. A third-party licence controls the corresponding third-party material. This policy governs project administration and does not override mandatory law or an executed agreement. ## 11. Contact From 0f9f0cda8ebfbdd664292ac06341fcb3629bd906 Mon Sep 17 00:00:00 2001 From: Alex Reznichenko Date: Sun, 22 Nov 2026 16:13:42 +0100 Subject: [PATCH 15/20] legal: commercial compatibility classes, asset cards and background material rule Signed-off-by: Alex Reznichenko --- THIRD_PARTY_POLICY.md | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/THIRD_PARTY_POLICY.md b/THIRD_PARTY_POLICY.md index 43ea608..e7b9239 100644 --- a/THIRD_PARTY_POLICY.md +++ b/THIRD_PARTY_POLICY.md @@ -35,3 +35,32 @@ Links and factual component references are preferred when redistribution permiss ## Review Pull requests containing third-party material require explicit provenance review before acceptance. Unclear material must be removed or quarantined until rights are confirmed. + +## Commercial compatibility + +OpenAMRobot must stay free to build, manufacture, sell, modify, redistribute and use in proprietary products without royalties and without asking anyone for permission. Third-party material is therefore accepted by licence class. The class applies both to material copied into a repository and to anything the default robot needs in order to be built, manufactured, run or used (libraries, packages, firmware components, hardware designs, simulation assets, datasets, base models and weights). + +| Class | Examples | Rule | +|---|---|---| +| Allowed | MIT, BSD-2-Clause, BSD-3-Clause, Apache-2.0, ISC, Zlib, BSL-1.0, CC0-1.0, CC-BY-4.0, CDLA-Permissive-2.0, CERN-OHL-P-2.0 | May be used once the required record exists and notices are preserved. Apache-2.0 material keeps its licence, `NOTICE` content and change notices; it is not relabelled MIT. | +| Approval needed | LGPL, MPL-2.0, EPL-2.0, CERN-OHL-W-2.0, CC-BY-SA-4.0, any licence with a patent or field-of-use condition, any vendor or custom licence | Only with written approval of Botshare LTD before acceptance, as a separate and replaceable component that is never copied into or statically combined with OpenAMRobot sources. The approval and its conditions are recorded. | +| Not accepted | GPL, AGPL, SSPL, CERN-OHL-S-2.0, Business Source and other source-available licences, any non-commercial, no-derivatives, research-only or evaluation-only terms, behavioural-use licences for models, and material with no licence | Not copied into a repository and not made a requirement of the default robot. | + +A tool used only on a developer's machine or in CI, whose output is not a derivative of the tool, is not a dependency of the robot for this table. It is still recorded when it affects reproducibility. + +When no compatible option exists, the choice is to write an original replacement, to make the function optional, or to ask Botshare LTD for a separate arrangement with the rights holder. It is never to hide or relabel the material. + +## Datasets, simulation assets and AI models + +Each dataset, recording set, simulation asset, model and set of weights is reviewed individually before acceptance and again before public release. It needs a card stating: + +- how it was produced, with the source commit, simulator and tool versions; +- every source dataset, asset pack, base model and pre-trained weight used, with licence and source; +- whether it shows identifiable people, private places or other personal data; +- the proposed public licence. + +Default public licences are CC BY 4.0 for suitable datasets and MIT for models and weights. An asset derived from material under other terms carries those terms and is accepted only if they fall in the Allowed class or are approved as above. Data or weights under non-commercial, research-only or behavioural-use terms must not be used to produce an asset submitted to OpenAMRobot. + +## Contributor Background Material + +Material a contributor owns and includes in a contribution is licensed to Botshare LTD in full under the contributor agreement, with no added restriction. If the contributor cannot grant that, the material is left out or covered by a separate written agreement signed by Botshare LTD before acceptance. Material that is only referred to, and not included, is named in the pull request with its location and licence. From 7fb9fcc70ae52e60e77c01c918e34b51be6ea9be Mon Sep 17 00:00:00 2001 From: Alex Reznichenko Date: Sun, 22 Nov 2026 16:14:19 +0100 Subject: [PATCH 16/20] legal: version-aware contributor agreement process and v2.0 activation steps Signed-off-by: Alex Reznichenko --- CLA.md | 82 ++++++++++++++++++++++++++++++++++++++++++---------------- 1 file changed, 60 insertions(+), 22 deletions(-) diff --git a/CLA.md b/CLA.md index e162df2..1610f39 100644 --- a/CLA.md +++ b/CLA.md @@ -1,54 +1,92 @@ # OpenAMRobot Contributor Agreement Process -Botshare LTD requires an accepted contributor agreement before accepting an external contribution. +Botshare LTD requires a recorded contributor agreement before accepting an external contribution. -## Applicable agreement +## Agreement versions -- Use the [Individual Contributor Agreement](INDIVIDUAL_CONTRIBUTOR_AGREEMENT.md) when contributing in your own capacity. -- Use the [Corporate Contributor Agreement](CORPORATE_CONTRIBUTOR_AGREEMENT.md) when an employer or organization owns, controls, sponsors, or authorizes the work. +| Version | Model | Documents | Status | +|---|---|---|---| +| 2.0 | Contributor keeps ownership; Botshare LTD receives a permanent, irrevocable, worldwide, royalty-free, transferable and sublicensable licence | [Individual Contributor License Agreement](INDIVIDUAL_CONTRIBUTOR_LICENSE_AGREEMENT.md), [Corporate Contributor License Agreement](CORPORATE_CONTRIBUTOR_LICENSE_AGREEMENT.md), [Guardian Consent](MINOR_CONTRIBUTOR_GUARDIAN_CONSENT.md) | Approved text. **Not yet offered for acceptance.** | +| 1.1 | Assignment of transferable economic rights to Botshare LTD | [Individual Contributor Agreement](INDIVIDUAL_CONTRIBUTOR_AGREEMENT.md), [Corporate Contributor Agreement](CORPORATE_CONTRIBUTOR_AGREEMENT.md) | Currently offered through CLA Assistant. Closed to new acceptances from the activation date of version 2.0. | + +**Activation date of version 2.0:** not set. Botshare LTD records the date here, in the same change that records the activation evidence below. Until then, CLA Assistant presents version 1.1, and nobody is covered by version 2.0. + +The version whose acceptance is recorded for a contributor governs that contributor's contributions: + +- Contributions accepted under version 1.1 stay under version 1.1. Assignments already made remain in effect. +- From the recorded time a contributor accepts version 2.0, version 2.0 governs every contribution of that contributor accepted afterwards, and no assignment under version 1.1 takes place for them. +- Publishing or changing a file in this repository does not change the agreement any contributor has accepted. + +## Which agreement applies + +- Use the Individual agreement when contributing in your own capacity. +- Use the Corporate agreement when an employer or organization owns, controls, sponsors, or authorizes the work. - If an employer, university, client, sponsor, co-author, joint inventor, or other party may have rights, obtain written authorization before submission. -- A contributor must not self-select the Individual Agreement merely to avoid a rights holder’s authorization. +- A contributor must not choose the Individual agreement to avoid a rights holder's authorization. +- A contributor under 18 needs the Guardian Consent on record before any contribution is merged. ## Individual contributor workflow -OpenAMRobot uses CLA Assistant with the organization-wide, shared **OpenAMRobot ICLA v1.1**. +OpenAMRobot uses CLA Assistant with one organization-wide agreement. 1. Open a pull request. 2. Follow the CLA Assistant link shown on the pull request. -3. Authenticate with the GitHub account used for the contribution. -4. Review and affirmatively accept the complete ICLA v1.1. -5. Wait for the CLA Assistant status check to pass. +3. Sign in with the GitHub account used for the contribution. +4. Read the complete agreement shown, check its document identifier and version, and accept it. +5. Wait for the `license/cla` status check to pass. 6. Ensure every commit also passes DCO. -An individual normally signs the shared agreement once. Later pull requests from the same verified GitHub account are recognized automatically while that agreement version remains applicable. +A contributor normally accepts once per version. When a new version is activated, CLA Assistant asks for a new acceptance on the next pull request. + +## Contributors under 18 + +1. A parent or legal guardian completes the [Guardian Consent](MINOR_CONTRIBUTOR_GUARDIAN_CONSENT.md) and sends it privately to **info@botshare.ai**. +2. Botshare LTD confirms in writing that it is on record. +3. Only then may a maintainer merge the contributor's pull requests. A CLA Assistant acceptance given by the minor alone is not sufficient. +4. On reaching 18, the contributor accepts the Individual agreement personally. ## Corporate, employer, and institutional workflow CLA Assistant acceptance is for contributors acting in their individual capacity. Where an employer, company, university, sponsor, client, or institution owns or controls the work: -1. complete the [Corporate Contributor Agreement](CORPORATE_CONTRIBUTOR_AGREEMENT.md); +1. complete the Corporate agreement in force; 2. have an authorized representative sign it; -3. identify the Authorized Contributors and GitHub usernames; -4. send the agreement privately to **info@botshare.ai** with subject: `OpenAMRobot Corporate Contributor Agreement — [legal entity]`; and -5. wait for Botshare LTD to confirm coverage before submitting or merging Contributions. +3. list the Authorized Contributors and their GitHub usernames; +4. send it privately to **info@botshare.ai** with subject `OpenAMRobot Corporate Contributor Agreement, [legal entity]`; and +5. wait for Botshare LTD to confirm coverage in writing before submitting or merging contributions. + +An organization that signed version 1.1 stays under version 1.1 until both parties have signed version 2.0. Signed agreements, identity documents, and private authorization records must never be committed to a public repository. ## Acceptance controls -DCO and the Contributor Agreement are cumulative: +DCO and the contributor agreement are cumulative: + +- DCO records provenance and the committer's certification. +- The accepted agreement governs inbound rights: assignment under version 1.1, licence under version 2.0. +- Passing an automated check does not cure invalid acceptance, missing authority, missing guardian consent, impersonation, or undisclosed third-party rights. +- A pull request must not merge until both DCO and the applicable agreement requirement are satisfied. +- A green `license/cla` check shows that the contributor accepted the agreement CLA Assistant presented at that time. Before the activation date that is version 1.1. A maintainer must not treat any contributor as covered by version 2.0 before the activation date, or without a CLA Assistant record of that contributor dated on or after it. + +## Activating version 2.0 + +Version 2.0 is activated only when all of the following are done and recorded: -- DCO records provenance and the committer’s certification. -- The accepted Agreement governs assignment and inbound rights. -- Passing an automated check does not cure invalid acceptance, missing authority, impersonation, or undisclosed third-party rights. -- A pull request must not merge until both DCO and the applicable CLA requirement are satisfied. +1. Botshare LTD's director approves the final texts in writing, after legal review. +2. The exact approved Individual text is published in a new, separately versioned CLA Assistant document. The version 1.1 document is never edited. +3. The published text is compared with the file in this repository and the SHA-256 of the file is recorded below. +4. A test pull request confirms that CLA Assistant shows version 2.0, asks a version 1.1 signer for a new acceptance, and records the acceptance with the document identifier. +5. The version 1.1 signature list is exported and stored privately with the version 1.1 text. +6. The organization-wide CLA Assistant link is switched to the version 2.0 document, and the activation date is entered above. +7. Every open external pull request is rechecked so that it asks for version 2.0. -Botshare LTD maintains records linking the agreement or electronic acceptance to the contributor, agreement version, GitHub identity, corporate authorization where relevant, pull requests, commit hashes, timestamps, and acceptance decision. +Activation evidence (filled in at activation): CLA Assistant document URL and revision: not set. SHA-256 of the Individual text: not set. Test pull request: not set. ## Version changes -The agreement version accepted by the contributor governs Contributions covered by it. A material amendment requires new acceptance. Updating a public Markdown file or Gist does not silently amend an accepted agreement. A material new version must use a separately versioned agreement record. +A material amendment requires new acceptance. Updating a public Markdown file or CLA Assistant document does not amend an accepted agreement. A material new version uses a separately versioned agreement record. ## Data protection -Contributor records are handled under the [Contributor Privacy Notice](CONTRIBUTOR_PRIVACY_NOTICE.md). Public repositories must contain no signed agreements, residential addresses, identification documents, or private contact details. +Contributor records are handled under the [Contributor Privacy Notice](CONTRIBUTOR_PRIVACY_NOTICE.md). Public repositories must contain no signed agreements, residential addresses, dates of birth, identification documents, or private contact details. From f4ad6b0ae9d9dfe9b5cea23cb3f97e5bac54217d Mon Sep 17 00:00:00 2001 From: Alex Reznichenko Date: Sun, 22 Nov 2026 16:15:01 +0100 Subject: [PATCH 17/20] legal: guardian consent form for contributors under 18 Signed-off-by: Alex Reznichenko --- MINOR_CONTRIBUTOR_GUARDIAN_CONSENT.md | 66 +++++++++++++++++++++++++++ 1 file changed, 66 insertions(+) create mode 100644 MINOR_CONTRIBUTOR_GUARDIAN_CONSENT.md diff --git a/MINOR_CONTRIBUTOR_GUARDIAN_CONSENT.md b/MINOR_CONTRIBUTOR_GUARDIAN_CONSENT.md new file mode 100644 index 0000000..3c2694c --- /dev/null +++ b/MINOR_CONTRIBUTOR_GUARDIAN_CONSENT.md @@ -0,0 +1,66 @@ +# OpenAMRobot Guardian Consent for Contributors under 18 + +**Document identifier:** OpenAMRobot-GC-1.0 +**Version:** 1.0, 22 November 2026 +**Used with:** [Individual Contributor License Agreement version 2.0](INDIVIDUAL_CONTRIBUTOR_LICENSE_AGREEMENT.md) ("Agreement") + +A person under 18 may contribute to OpenAMRobot when a parent or legal guardian completes this form. Send the signed form privately to **info@botshare.ai**. Do not post it, or any personal details from it, in a pull request, issue or repository. Contributions are merged only after Botshare LTD has confirmed in writing that the form is on record. + +## 1. Who signs + +- "Minor": the contributor, who is under 18. +- "Guardian": a parent or other person with legal authority to act for the Minor. + +## 2. What the Guardian agrees + +2.1 The Guardian has read the Agreement and has explained it to the Minor. + +2.2 The Guardian confirms having legal authority to act for the Minor in this matter under the law of the country where the Minor lives. Where that law requires the consent of both parents or of another person or authority, the Guardian confirms that this consent has been obtained. + +2.3 The Guardian enters the Agreement on the Minor's behalf and in the Guardian's own name, and grants Botshare LTD the licences in the Agreement for the Minor's Accepted Contributions. + +2.4 This consent covers Contributions of the Minor accepted from the date below. Where the box in section 5 is ticked, it also covers Contributions of the Minor that were accepted before that date, which are licensed on the terms of the Agreement from the date each was accepted. + +2.5 The Minor keeps ownership of the Minor's Contributions, as the Agreement provides. No payment is owed by either side. + +2.6 The Guardian consents to Botshare LTD processing the personal data on this form, and the Minor's public GitHub contribution record, as described in the [Contributor Privacy Notice](CONTRIBUTOR_PRIVACY_NOTICE.md). + +2.7 The Guardian may withdraw this consent for future Contributions by writing to info@botshare.ai. Licences for Contributions accepted before the withdrawal continue, as the Agreement provides. + +## 3. What the Minor confirms + +The Minor has read the Agreement, understands that accepted work is licensed to Botshare LTD permanently and may be used commercially, and wishes to contribute on those terms. On reaching 18, the Minor will accept the Agreement personally at the next contribution. + +## 4. What Botshare LTD does + +Botshare LTD keeps this form privately, records only "guardian consent on record" with the GitHub username and the date in its contributor record, and deletes the Minor's date of birth once the Minor has accepted the Agreement personally as an adult. + +## 5. Details and signatures + +Minor's full name: _________________________________________ + +Minor's GitHub username: ___________________________________ + +Minor's date of birth: ______________________________________ + +Country of residence: ______________________________________ + +[ ] This consent also covers the Minor's Contributions accepted before the date below. + +Guardian's full name: ______________________________________ + +Relationship to the Minor: __________________________________ + +Guardian's email and phone: ________________________________ + +Guardian's signature: ______________________________________ + +Minor's signature: _________________________________________ + +Date: _____________________________________________________ + +### Botshare LTD + +Confirmed on record by (name, title): ________________________ + +Date: _____________________________________________________ From a4521266809cf66f1f7c6285a9963e9d8ad04e40 Mon Sep 17 00:00:00 2001 From: Alex Reznichenko Date: Sun, 22 Nov 2026 16:15:14 +0100 Subject: [PATCH 18/20] legal: corporate contributor license agreement v2.0 Signed-off-by: Alex Reznichenko --- CORPORATE_CONTRIBUTOR_LICENSE_AGREEMENT.md | 102 +++++++++++++++++++++ 1 file changed, 102 insertions(+) create mode 100644 CORPORATE_CONTRIBUTOR_LICENSE_AGREEMENT.md diff --git a/CORPORATE_CONTRIBUTOR_LICENSE_AGREEMENT.md b/CORPORATE_CONTRIBUTOR_LICENSE_AGREEMENT.md new file mode 100644 index 0000000..9656554 --- /dev/null +++ b/CORPORATE_CONTRIBUTOR_LICENSE_AGREEMENT.md @@ -0,0 +1,102 @@ +# OpenAMRobot Corporate Contributor License Agreement + +**Document identifier:** OpenAMRobot-CCLA-2.0 +**Agreement version:** 2.0, 22 November 2026 +**Status:** approved text. It applies to an organization only from the date both parties have signed it. Until then, a Corporate Contributor Agreement version 1.1 signed by that organization continues to apply to it. + +This Corporate Contributor License Agreement ("Agreement") is between **Botshare LTD**, Company ID HE479056, VAT 60197356L, of Chrysanthou Mylona 1, Panayides Building, Floor 2, Office 1, 3030 Limassol, Cyprus ("Company"), and the legal entity identified in the signature section ("Contributor Organization"). + +In consideration of the parties' mutual promises, and of Company's evaluation, possible acceptance, maintenance, publication and distribution of Contributions, the parties agree as follows. + +## 1. Incorporated terms + +1.1 The [Individual Contributor License Agreement version 2.0](INDIVIDUAL_CONTRIBUTOR_LICENSE_AGREEMENT.md), document identifier OpenAMRobot-ICLA-2.0 ("Individual Terms"), sections 1 to 9, 12, 14 and 15, form part of this Agreement, read with "Contributor Organization" in place of "Contributor" and with the changes below. Where this Agreement and the Individual Terms differ, this Agreement prevails. + +1.2 "Contribution" means material Submitted by an Authorized Contributor within the authority given by Contributor Organization. + +1.3 "Authorized Contributor" means an employee, officer, contractor or other representative of Contributor Organization listed in Schedule A, as changed under section 3. + +## 2. Ownership and licence + +2.1 Contributor Organization keeps ownership of the intellectual property rights it holds in its Contributions and remains free to use, license and commercialize them anywhere. No ownership is assigned to Company. Section 2 of the Individual Terms applies to Company's own work. + +2.2 Contributor Organization grants Company, Company Group and Downstream Parties the licences in sections 3, 4, 6 and 7 of the Individual Terms for every Accepted Contribution, covering all rights that Contributor Organization owns or can license, including rights it obtained from its employees and contractors. + +2.3 The patent licence covers patent claims owned or licensable by Contributor Organization and by the entities it controls. + +## 3. Authorized Contributors + +3.1 Contributor Organization keeps Schedule A accurate. An addition takes effect when Company acknowledges it in writing. A removal takes effect for future Contributions when Company receives the notice. + +3.2 Removal of a person, a change of that person's employment, or the end of this Agreement does not affect the licences for Contributions accepted before it. + +3.3 Each Authorized Contributor uses an attributable GitHub account, signs every commit under the DCO and follows the project policies. Authorized Contributors do not need to accept the Individual Terms for work covered by this Agreement. + +3.4 A person who also contributes in a personal capacity, outside the authority of Contributor Organization, needs a recorded acceptance of the Individual Contributor License Agreement for that work. + +3.5 Contributor Organization names a point of contact in Schedule B for notices under this Agreement. + +## 4. Statements of Contributor Organization + +Contributor Organization confirms, at each submission and acceptance, that: + +(a) the person signing has authority to bind it; + +(b) it owns or controls the rights licensed, and has obtained from its employees, contractors, co-authors and inventors all assignments, permissions and consents needed, including the consents in section 8 of the Individual Terms; + +(c) the statements in sections 5, 6, 9 and 10(b), (d), (e) and (f) of the Individual Terms are true for each Contribution; + +(d) it remains responsible for any employee-inventor compensation or similar payment owed under its own relationships. None is owed by Company Group or Downstream Parties. + +## 5. Relation to version 1.1 + +5.1 If Contributor Organization signed Corporate Contributor Agreement version 1.1, this Agreement replaces it for every Contribution that becomes an Accepted Contribution after the date both parties have signed this Agreement. Company agrees that no assignment under version 1.1 takes place for those Contributions. + +5.2 Contributions accepted under version 1.1 before that date remain governed by version 1.1. Assignments already made under it remain in effect and are not reversed by this Agreement. + +5.3 If an assignment under version 1.1 is found not to have been effective for a Contribution, the licences in this Agreement apply to that Contribution from the date it was accepted. + +## 6. Signature and records + +6.1 This Agreement is signed by an authorized representative of each party, by handwritten signature on a scanned copy or by an advanced or qualified electronic signature, and sent privately to info@botshare.ai. It is not accepted through CLA Assistant. + +6.2 Contributions of an organization are treated as covered by this version only after Company has confirmed in writing that the signed Agreement and Schedule A are on record. + +6.3 Signed agreements and schedules are not published in any repository. + +## Contributor Organization signature + +Legal name: _______________________________________________ + +Registration number: ______________________________________ + +Registered address: _______________________________________ + +Country of incorporation: __________________________________ + +Authorized signatory name and title: ________________________ + +Email: ____________________________________________________ + +Signature: ________________________________________________ + +Date: _____________________________________________________ + +## Botshare LTD signature + +Name and title: ____________________________________________ + +Signature: ________________________________________________ + +Date: _____________________________________________________ + +## Schedule A: Authorized Contributors + +| Full legal name | GitHub username | Relationship (employee, contractor, other) | +|---|---|---| +| | | | +| | | | + +## Schedule B: Point of contact + +Name: _____________________ Email: _____________________ From 0097fca03b9ad65a680b31092b44a3aea4a072a7 Mon Sep 17 00:00:00 2001 From: Alex Reznichenko Date: Sun, 22 Nov 2026 16:16:14 +0100 Subject: [PATCH 19/20] legal: individual contributor license agreement v2.0 Signed-off-by: Alex Reznichenko --- INDIVIDUAL_CONTRIBUTOR_LICENSE_AGREEMENT.md | 198 ++++++++++++++++++++ 1 file changed, 198 insertions(+) create mode 100644 INDIVIDUAL_CONTRIBUTOR_LICENSE_AGREEMENT.md diff --git a/INDIVIDUAL_CONTRIBUTOR_LICENSE_AGREEMENT.md b/INDIVIDUAL_CONTRIBUTOR_LICENSE_AGREEMENT.md new file mode 100644 index 0000000..1367270 --- /dev/null +++ b/INDIVIDUAL_CONTRIBUTOR_LICENSE_AGREEMENT.md @@ -0,0 +1,198 @@ +# OpenAMRobot Individual Contributor License Agreement + +**Document identifier:** OpenAMRobot-ICLA-2.0 +**Agreement version:** 2.0, 22 November 2026 +**Status:** approved text. It applies to a contributor only from the moment that contributor's acceptance of this exact version is recorded (section 16). The date from which Botshare LTD offers this version for acceptance is recorded in [CLA.md](CLA.md). + +This Contributor License Agreement ("Agreement") is between **Botshare LTD**, Company ID HE479056, VAT 60197356L, of Chrysanthou Mylona 1, Panayides Building, Floor 2, Office 1, 3030 Limassol, Cyprus ("Company"), and the individual who accepts it ("Contributor"). + +In consideration of the parties' mutual promises, and of Company's evaluation, possible acceptance, maintenance, publication and distribution of Contributions, the parties agree as follows. + +## 1. Definitions + +1.1 "Contribution" means any material that Contributor Submits, in any form: software in source and object form, firmware, configuration, tests, electronics, PCB designs, schematics, CAD, mechanical and hardware designs, manufacturing files, documentation, simulation assets, schemas, databases, datasets, recordings, AI models and weights, media, and other protectable material, together with the technical information disclosed in it. + +1.2 "Submit" means intentionally providing material to an official OpenAMRobot repository, pull request, issue, review, or another contribution channel designated by Company, for possible inclusion in OpenAMRobot. + +1.3 "Accepted Contribution" means a Contribution, or any part of one, that an authorized maintainer merges into an official OpenAMRobot repository by any method (merge, squash, rebase, cherry-pick or manual copy), or that Company expressly accepts in writing. + +1.4 "Background Material" means material that Contributor owns, created or acquired independently of the Contribution, and identified in the pull request before acceptance. + +1.5 "Third-Party Material" means material in which a person other than Contributor or Company holds rights. + +1.6 "Company Group" means Company and its affiliates, successors and assigns. + +1.7 "Downstream Parties" means the contractors, manufacturers, distributors, resellers, integrators, customers, licensees and users of Company Group, in each case for products, services and material that come from Company Group. + +## 2. Ownership + +2.1 Contributor keeps ownership of all intellectual property rights in Contributor's own Contributions. This Agreement does not assign or transfer ownership of them to Company. + +2.2 Contributor remains free to use, modify, publish, license and commercialize Contributor's own Contributions anywhere, including in other projects and products, alone or with others. Company has no claim on the proceeds. + +2.3 Company owns, and nothing in this Agreement gives Contributor any right in: + +(a) material created by Company, its employees and contractors, or assigned to Company under another agreement; + +(b) the modifications, improvements, adaptations and derivative works that Company or its personnel make to Accepted Contributions, as far as Company's own additions are concerned. The underlying Contribution stays owned by Contributor; + +(c) technology that Company develops independently, including technology that performs the same function as a Contribution; + +(d) the selection, arrangement and integration of the OpenAMRobot project as a whole, and Company's products built on it; + +(e) the OpenAMRobot and Botshare names, logos and brand assets, and Company's confidential information. + +2.4 Company has no duty to disclose, publish or contribute back its own work. Nothing in this Agreement restricts Company from developing, acquiring or using material that is similar to or competes with a Contribution. + +2.5 Contributor acquires no rights in material of other contributors by contributing, other than the rights given by the public licences under which that material is published. + +## 3. Licence to Company + +3.1 For each Accepted Contribution, Contributor grants Company a non-exclusive, worldwide, perpetual, irrevocable, fully paid, royalty-free, transferable and sublicensable (through multiple tiers) licence under all copyright and related rights, database rights, registered and unregistered design rights, semiconductor topography rights, rights in technical information and analogous rights that Contributor can license, to use, reproduce, modify, adapt, translate, combine, distribute, publish, communicate, display, perform, make derivative works of, manufacture and have manufactured, sell, offer for sale, lease, import, export, maintain, operate, commercialize and otherwise exploit the Accepted Contribution for any purpose, in open-source, proprietary, hardware and service offerings, with or without modification. + +3.2 The licence includes the right to use Accepted Contributions, including datasets and recordings, to train, fine-tune, evaluate and operate machine-learning models. As between the parties, Company owns the models, weights and outputs that Company produces in this way. + +3.3 Company may license and relicense Accepted Contributions, alone or combined with other material, to anyone on any terms, including proprietary and dual licences, without further consent, notice or payment. + +3.4 Company may transfer this licence, in whole or in part, to an affiliate, or to a successor or acquirer of the OpenAMRobot project or of the relevant business or assets, without Contributor's consent. The licence benefits Company Group and continues after any change of control. + +3.5 No royalty, fee or other payment is due, now or later, from Company Group or Downstream Parties for any use of an Accepted Contribution. Contributor will not make a claim against Company Group or Downstream Parties that is inconsistent with the licences in this Agreement. + +3.6 The licence cannot be revoked or terminated for any reason. It survives Contributor leaving the project, account deletion, any dispute between the parties and termination of this Agreement. Contributor's only remedy for a breach of this Agreement by Company is a claim for damages. + +3.7 The licence binds Contributor's heirs, successors and assigns. Contributor will transfer or exclusively license rights in an Accepted Contribution only subject to this Agreement. + +3.8 While a Contribution is under review and not yet accepted, Contributor permits Company and its maintainers to copy, build, run, test and discuss it for evaluation. + +## 4. Public licence + +4.1 Company publishes Accepted Contributions as part of OpenAMRobot under the project licence for the asset type: + +- software, firmware, scripts, configuration and tests: MIT; +- hardware sources, electronics, PCB, schematics, CAD, mechanical designs, manufacturing sources and CAD-derived robot geometry: CERN-OHL-P-2.0; +- documentation, diagrams, tutorials, images and educational content: CC BY 4.0; +- datasets, recordings, simulation assets, AI models and weights: the licence Company approves for that asset under section 6, by default CC BY 4.0 for suitable datasets and MIT for models and weights. + +4.2 Company decides whether, when and where an Accepted Contribution is published. Copies already distributed under a project licence stay under that licence. + +4.3 Contributor will not attach additional restrictions, copyleft terms, conflicting notices or approval requirements to a Contribution. + +## 5. Background Material and Third-Party Material + +5.1 Contributor keeps ownership of Background Material. + +5.2 Background Material that is included in an Accepted Contribution is licensed to Company on the terms of sections 3, 4 and 7, with no additional restriction. If Contributor cannot grant those rights in full, Contributor must leave the material out of the Contribution. It may be included only under a separate written agreement that Company signs before acceptance. + +5.3 Background Material that a Contribution refers to or can optionally be used with, and that is not included in the pull request, is not licensed by this Agreement. Naming it in the pull request, with its location and licence, is sufficient. A Contribution must not need such material to be built, manufactured, run or used unless the material is publicly available under a licence that the Third-Party Material Policy allows, or Company approves it in writing before acceptance. + +5.4 Third-Party Material may be included in, or required by, a Contribution only if: (a) its source, rights holder, exact version, licence and required notices are stated in the pull request; and (b) its licence allows commercial use, modification, manufacturing, redistribution and use in proprietary products without royalty and without requiring Company to publish its own material, as set out in the [Third-Party Material Policy](THIRD_PARTY_POLICY.md); or (c) Company approves it in writing before acceptance. + +5.5 This Agreement does not relicense Third-Party Material. Upstream licences, notices and attribution are preserved. Contributor will not present third-party, employer-owned, university-owned, confidential or unlicensed material as Contributor's own original work. + +5.6 Company may reject or remove any material whose rights do not meet this section. + +## 6. Datasets, recordings, simulation assets and AI models + +6.1 Each dataset, recording set, simulation asset, AI model or set of weights is reviewed individually. Contributor states in the pull request, or in a card supplied with the asset, how it was produced: the source data, the simulator and assets used, any base model or pre-trained weights with their licences, the tools used, and whether it shows identifiable people or private places. + +6.2 Contributor confirms that the asset was not produced from, and does not contain, training data, weights, simulation assets or other material whose terms prohibit or restrict commercial use, modification, redistribution or use in proprietary products, unless Company approved it in writing before acceptance. + +6.3 Contributor confirms that the asset contains no personal data, unless it is disclosed and has a lawful basis that also covers Company's use. + +6.4 The licence in section 3 applies in full to the asset from acceptance. Public release, and the public licence, follow Company's approval for that asset. Where upstream terms require a particular licence for an asset that Company approved, those terms apply to that asset and are recorded with it. + +## 7. Patents + +7.1 Contributor keeps ownership of Contributor's patents and inventions. + +7.2 Contributor grants Company Group a non-exclusive, worldwide, perpetual, irrevocable, royalty-free, transferable and sublicensable patent licence to make, have made, use, sell, offer for sale, lease, import, export and otherwise dispose of the Accepted Contribution and products and services that contain or use it. The licence extends to Downstream Parties. + +7.3 Contributor grants every other recipient of an Accepted Contribution under a project licence a non-exclusive, worldwide, perpetual, royalty-free patent licence to make, have made, use, sell, offer for sale, import and otherwise transfer the Accepted Contribution. + +7.4 The licences in 7.2 and 7.3 cover the patent claims that Contributor owns or can license, now or later, that are necessarily infringed by the Accepted Contribution alone or by its combination with OpenAMRobot as it existed when the Contribution was accepted. + +7.5 Contributor will not assert against Company Group or Downstream Parties any patent claim covered by 7.4. + +7.6 The licence in 7.3 ends for a recipient on the date that recipient files a patent claim against Contributor or Company alleging that the Accepted Contribution, or OpenAMRobot as published by Company, infringes a patent. Defensive counterclaims are excepted. It ends only for that recipient. A claim filed by anyone else does not affect the licences of Company Group or of Downstream Parties. + +7.7 The licences in this section bind any later owner or exclusive licensee of the patents. Contributor will transfer or exclusively license them only subject to this Agreement. + +## 8. Authorship and moral rights + +8.1 Contributor remains the author. Company keeps accurate attribution in the Git history or equivalent project records and will not present another person as the author. Attribution in every product, interface or copy is not promised unless law or a licence requires it. + +8.2 To the extent the law allows, Contributor consents to Company Group and Downstream Parties modifying, combining, translating, publishing, not publishing and removing Accepted Contributions, and agrees not to assert moral rights to prevent uses licensed by this Agreement. Contributor keeps the right to be identified as author and to object to treatment that damages Contributor's honour or reputation. + +## 9. AI-assisted material + +9.1 Contributor discloses materially AI-assisted content in the pull request description: which parts were AI-assisted, the tool used, and confirmation that Contributor reviewed and tested them. Per-commit tool trailers are not required. + +9.2 Content is "materially AI-assisted" when a tool generated a substantial part of the code, text, design or data. Autocomplete, spelling, formatting and comparable editing aids are not material. + +9.3 Contributor confirms that the terms of the tool allow the content to be Submitted and licensed under this Agreement, and that Contributor checked the output for Third-Party Material. Where the law gives no protection to AI output, the licence covers whatever rights exist. + +## 10. Contributor statements + +Contributor confirms, at submission and again at acceptance, that: + +(a) Contributor is at least 18 years old and has legal capacity to enter this Agreement, or section 11 has been completed; + +(b) the Contribution is Contributor's original work, except for Background Material and Third-Party Material disclosed under section 5; + +(c) Contributor has the right to grant these licences, and either no employer, university, client, sponsor, co-author or funding body has rights in the Contribution, or that party has given written permission. Where an organization owns or controls the work, the [Corporate Contributor License Agreement](CORPORATE_CONTRIBUTOR_LICENSE_AGREEMENT.md) applies instead; + +(d) Contributor has not granted, and will not grant, rights that conflict with this Agreement; + +(e) the Contribution contains no unauthorized confidential information, trade secrets, personal data or credentials, and Contributor does not know of any infringement of third-party rights; + +(f) Contributor follows the DCO and the project's contribution, provenance, security and AI policies, and will tell Company promptly at info@botshare.ai if any statement above stops being true. + +## 11. Contributors under 18 + +11.1 A person under 18 may contribute only after a parent or legal guardian has signed the [Guardian Consent](MINOR_CONTRIBUTOR_GUARDIAN_CONSENT.md) and Company has confirmed in writing that it is on record. An electronic acceptance given by the minor alone does not cover the minor's Contributions. + +11.2 The guardian enters this Agreement on the minor's behalf and in the guardian's own name, and grants the licences in this Agreement for the minor's Accepted Contributions. + +11.3 On reaching 18, the contributor accepts this Agreement personally, and by doing so confirms the licences for all earlier Accepted Contributions. + +## 12. DCO, records and confirmations + +12.1 Every commit needs a valid DCO sign-off. The DCO certifies origin and authority. It does not license or assign rights and does not replace this Agreement. + +12.2 Company may keep records of the agreement version, the electronic acceptance, the GitHub identity, pull requests, commit hashes and acceptance decisions, as described in the [Contributor Privacy Notice](CONTRIBUTOR_PRIVACY_NOTICE.md). + +12.3 At Company's request and reasonable expense, Contributor will confirm the licences in this Agreement in writing, for example to a customer, investor, acquirer or registry. Company's rights do not depend on that confirmation. + +## 13. Which contributions this version covers; relation to version 1.1 + +13.1 This version covers every Contribution that becomes an Accepted Contribution after Contributor's acceptance of it is recorded, including Contributions Submitted in pull requests opened before that moment. + +13.2 If Contributor accepted Individual Contributor Agreement version 1.1, this Agreement replaces version 1.1 for every Contribution that becomes an Accepted Contribution after Contributor's acceptance of this Agreement is recorded. Company agrees that no assignment under version 1.1 takes place for those Contributions. + +13.3 Contributions accepted under version 1.1 before that moment remain governed by version 1.1. Assignments already made under it remain in effect and are not reversed by this Agreement. + +13.4 If an assignment under version 1.1 is found not to have been effective for a Contribution, the licences in this Agreement apply to that Contribution from the date it was accepted. + +13.5 A later version applies to Contributor only after Contributor accepts it. Publishing a changed file or changing a link does not amend this Agreement. + +## 14. No obligation, no relationship, no warranty + +Company is not obliged to accept, use, publish or maintain any Contribution or to pay for it. This Agreement creates no employment, partnership, agency or joint venture and no governance right. Contributions are provided "as is", without warranty other than the statements in sections 5, 6, 9 and 10, and without any duty to provide support. Subject to mandatory law, neither party is liable to the other under this Agreement for indirect or consequential loss. Nothing limits liability that the law does not allow to be limited. + +## 15. Term, law and courts + +15.1 Either party may end this Agreement for future Contributions by written notice. The licences for Contributions accepted before the notice continue and stay irrevocable. + +15.2 This Agreement is governed by the laws of the Republic of Cyprus. The courts of the Republic of Cyprus have jurisdiction, subject to mandatory rules that give Contributor the right to use other courts. Either party may seek urgent interim relief in any competent court. + +15.3 If a provision is invalid or unenforceable, it is applied to the fullest extent the law permits, and the rest of this Agreement stays in force. If a licence cannot be irrevocable or perpetual under the applicable law, it lasts for the longest period and on the firmest terms that law permits. + +15.4 Company may assign this Agreement together with the OpenAMRobot project or the relevant business or assets. Contributor may not assign it. + +## 16. Acceptance + +16.1 Contributor accepts this specific version 2.0 through the CLA Assistant record linked to Contributor's GitHub account, where the record shows this document identifier, or by a signed copy sent to info@botshare.ai. + +16.2 Contributor is covered by this version only from the recorded acceptance time. An acceptance of version 1.1, or a passing automated check that does not record acceptance of this version, is not acceptance of this Agreement. + +16.3 Company accepts by offering this version for acceptance and recording Contributor's acceptance. From 9010d867dcb2a9eb911cac4fc4f0068d1a8dfd39 Mon Sep 17 00:00:00 2001 From: Alex Reznichenko Date: Sun, 22 Nov 2026 16:17:48 +0100 Subject: [PATCH 20/20] state: point the contributor agreement row at PR 95 Signed-off-by: Alex Reznichenko --- STATE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/STATE.md b/STATE.md index d1714a2..2645b6e 100644 --- a/STATE.md +++ b/STATE.md @@ -27,7 +27,7 @@ The PR evidence check fails when STATE.md exists and a PR neither updates it nor | Decisions of 3 Nov 2026 | #85 | merged as dafab0e (2026-11-04) | owner review: K1/K2 GX11CAC decided, rear power module, BMS side gap, FB-A/FB-B, receiver 15 mm gap, flag rod guide | | P-03 rev20.4 (decisions of 8 Nov 2026) | decisions/2026-11-08-owner-decisions | open for owner review (2026-11-08) | owner review: in_force P-03-rev20.4, ZX80 55 mm lower, head camera 60 mm, receiver frame (no metal within 20 mm of the sides, 15 mm above), DOLD CAD, arch backing plate, new WIRING-ROUTING (slot defined, two lift cable openings, scoped check after review), P-03 rev20.6 item 30: LIFT fixing through the foot tabs 260 x 30 mm (D-20) and backing plate (D-21), COMPUTE Orin NX 8 GB on the Robotics 104 (D-01); review of 9 Nov 2026 (2026-11-10): one P-03-rev20.6 source, duplicate YAML keys rejected by the loader, WIRING-ROUTING cover-slot matcher narrowed (unless read per sentence), slot geometry enforced by openamrobot-docs slot_rule.py, BOM 7.15 recorded as the roadmap extract source, ROADMAP.md compute | | #83 | #84 | merged as 5ed600e (2026-11-02) | none; the 2 Nov 2026 values are in force | -| Contributor agreement 2.0 | #93 (legal/contributor-retained-rights-v2-proposal) | texts and policy alignment prepared for review (2026-11-22); not activated, CLA Assistant still presents 1.1 | Cyprus IP counsel review, director approval, then the activation steps in CLA.md | +| Contributor agreement 2.0 | #95 (legal/cla-v2; supersedes #93) | texts and policy alignment prepared for review (2026-11-22); not activated, CLA Assistant still presents 1.1 | Cyprus IP counsel review, director approval, then the activation steps in CLA.md | | PLATFORM-PIN | #74 | pin 131e500fc4e5afc9f648cbd7dbf5b416280761fb (2.0 base, P-03 rev20.1 item 25 D7), validated by openamr-upperbody-sw #21; merged with this PR (2026-11-01) | none; touches decisions.yaml only | ## Decisions this repository implements