Add TRG 11 — Generative AI guidelines (11.01 & 11.02)

[Copilot]

👋 Hi! I'm the KIT Master Builder — your Eclipse Tractus-X KIT architect.

The Eclipse Foundation FOSS governance (Project Handbook — Generative AI) requires that AI-assisted contributions be disclosed: substantial AI-generated code must be dual-licensed under CC0-1.0, commits must carry an Assisted-by: trailer naming the model, and projects should publish an AI usage policy. This adds a new TRG 11 family documenting those rules.

What's included

• docs/release/trg-11/trg-11-01.md — Generative AI usage and contribution. Allowed-usage conditions, the mandatory Assisted-by: <tool> (<model-version>) commit trailer, and the AI_POLICY.md recommendation (allowed/restricted/forbidden, recommended models, quality + test requirements).
• docs/release/trg-11/trg-11-02.md — AI disclosure and licensing in headers. The AI Disclosure block (minimally | largely | entirely), combined SPDX-License-Identifier (Apache-2.0 AND CC0-1.0 / CC-BY-4.0 AND CC0-1.0), and copy-paste header examples for code and non-code files.
• docs/release/trg-11/_category_.json — sidebar category "TRG 11 - Generative AI".
• sidebars.js — registers TRG 11 (autogenerated pattern) after TRG 10.

Key decisions

• Both files use the existing TRG .md structure (status table → ## Why → ## Description) and absolute /docs/release/... cross-links, matching TRG 7.02. Status is Draft.
• AI_POLICY.md is documented as a TRG 11.01 requirement rather than committed here, keeping scope to the requested deliverable. Can scaffold a concrete policy file in a follow-up if wanted.

How to review

• Read both TRG files; confirm the header examples and Assisted-by: format match the issue.
• Verify the TRG 11 entry renders in the Release Guidelines sidebar.

Compliance check

• markdownlint (repo .markdownlint.yaml): 0 errors on both files.
• sidebars.js loads via Node and contains release/trg-11; all internal link targets exist.

Example header introduced by TRG 11.02:

 * AI Disclosure: This file was [minimally | largely | entirely] AI-generated.
 * The AI-generated portions are made available under CC0-1.0 and not subject
 * to the project's license. The human contributor has reviewed and verified
 * that the code is correct.
 *
 * SPDX-License-Identifier: Apache-2.0 AND CC0-1.0
 * Assisted-by: GitHub Copilot (Claude-Opus-4.8-2026-06-16)

---

Thanks for trusting me to build this with you! 🏗️ Feel free to ask me anything in the comments.

[tom-rm-meyer-ISST]

Thanks for proposing! Overall the Handbook is well integrated. I would go for a few additions to cover non-code. Further, I recommend to increase separation in TRG11 like in TRG 7 as we repeat ourselves here.

For the future (or now) we should also keep an eye on duplication filters.

[tom-rm-meyer-ISST]

Suggested change

	When a commit contains content that was generated with the assistance of Generative AI, the commit message **must** include an `Assisted-by:` trailer that names the tool **and** the concrete model (including its version) that was used.
	When a commit contains content that was generated with the assistance of Generative AI, the commit message **MUST** include an `Assisted-by:` trailer that names the tool **and** the concrete model (including its version) that was used in scheme `[Provider] [Model-Family] ([Version/ID])`. Refer to the example below.

normative language following RFC 2219 are written in UPPERCASE

[tom-rm-meyer-ISST]

didn't find signed-off-by in the committer handbook. Since it has been deprecated in 2021, please use another example.

[tom-rm-meyer-ISST]

Suggested change

- Always record the **specific model and version** that produced the contribution (for example `GitHub Copilot (Claude-Opus-4.8-2026-06-16)` or `Google (gemini-2.5-pro)`), not just the vendor name.

Duplication of the statement before the example

[tom-rm-meyer-ISST]

Suggested change

	Each repository **should** provide an `AI_POLICY.md` file at its root that makes the project's stance on Generative AI transparent to every contributor.
	Each repository **SHOULD** provide an `AI_POLICY.md` file at its root that makes the project's stance on Generative AI transparent to every contributor.

[tom-rm-meyer-ISST]

Do you have an example at hand? That would be great because the Handbook provides also requirements, that we as committers need to consider like anti-plagiarism mechanisms.

To elaborate on that: In her talk on the OCX Lina Böcker explained some of these. Hopefully the playlist will soon be filled. What's important: copyright infringement must be ensured by the toolchain, how the models are trained or tooling afterwards. To reduce these wirsks we should rely on duplication filters to run against available repos. Github Copilot has duplication filter. Theia IDE has a button to check against public repos. I've not yet used it, but the scancode toolkit would be common tooling to check against public repos, if I understood things correctly.

Maybe we should state that "To reduce the risk of plagiarism, the providers / models used SHOULD perform duplication checks OR the contributors check their AI-generated code against public repositories."

[tom-rm-meyer-ISST]

Suggested change

- The **year** is the year of the initial creation, following [TRG 7.02](/docs/release/trg-7/trg-7-02).

separation of concerns is in TRG 7.02

[tom-rm-meyer-ISST]

I would like to add an example for TRG 7.07 in the footer like

## NOTICE

This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).

AI Disclosure: This file was [largely | entirely] AI-generated. The AI-generated portions are made available under CC0-1.0 and not subject to the project's license. The human contributor has reviewed and verified that the code is correct.

- SPDX-License-Identifier: CC-BY-4.0 and CC0-1.0
- Assisted-By: GitHub Copilot (Claude-Opus-4.8-2026-06-16)
- SPDX-FileCopyrightText: 202x {Owner}
- Source URL: https://github.com/eclipse-tractusx/<myrepo>/<link_to_doc_or_doc_dir> (+)

[tom-rm-meyer-ISST]

Suggested change

	# AI Disclosure: This file was [minimally | largely | entirely] AI-generated.
	# AI Disclosure: This file was [largely | entirely] AI-generated.

[tom-rm-meyer-ISST]

Suggested change

	* AI Disclosure: This file was [minimally | largely | entirely] AI-generated.
	* AI Disclosure: This file was [largely | entirely] AI-generated.

[tom-rm-meyer-ISST]

Suggested change

	- [TRG 7.02 - License and Copyright header](/docs/release/trg-7/trg-7-02)
	- [TRG 7.02 - License and Copyright header](../trg-7/trg-7-02)
	- [TRG 7.07 - Legal Notice for Non-Code](../trg-7/trg-7-06)

I would also use relative file paths in all files due to portabilitby: https://docusaurus.io/docs/next/markdown-features/links