This is an automated email from the ASF dual-hosted git repository.
luigidemasi pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-kit.git
The following commit(s) were added to refs/heads/main by this push:
new 886dac2a [chore]: Require AI attribution for contributions
886dac2a is described below
commit 886dac2acd1b644f17f7f8cebd0206853c412c51
Author: Luigi De Masi <[email protected]>
AuthorDate: Sat Oct 24 11:05:45 2026 +0200
[chore]: Require AI attribution for contributions
Add repository-wide rules for AI disclosure, verified operator identity,
commit co-authorship and attribution preservation during squash merges.
Import the shared rules from CLAUDE.md so Claude contributors follow them.
Co-authored-by: OpenAI Codex <[email protected]>
---
AGENTS.md | 43 +++++++++++++++++++++++++++++++++++++++++++
CLAUDE.md | 2 ++
2 files changed, 45 insertions(+)
diff --git a/AGENTS.md b/AGENTS.md
new file mode 100644
index 00000000..a2f25ee6
--- /dev/null
+++ b/AGENTS.md
@@ -0,0 +1,43 @@
+# Camel-Kit AI Agent Guidelines
+
+These rules apply to all AI agents and harnesses used to contribute to this
repository.
+They follow [Apache Camel's attribution
rules](https://github.com/apache/camel/blob/main/AGENTS.md#attribution)
+and the [ASF Generative Tooling
Guidance](https://www.apache.org/legal/generative-tooling.html).
+
+## Attribution
+
+- All AI-generated content, including issue and PR descriptions, review
comments,
+ inline comments and replies, MUST clearly identify itself as AI-generated and
+ mention the human operator.
+- Never guess the operator's name. Determine the authenticated GitHub username
with
+ `gh api /user --jq '.login'`. If the lookup fails, omit the operator rather
than
+ inventing a name.
+- AI coding agents MUST be configured to add AI co-authorship trailers to
commits,
+ including documentation-only commits. For Claude Code, this can be
configured in
+ its [attribution
settings](https://code.claude.com/docs/en/settings#attribution-settings).
+- Use the identity of the agent that actually contributed, regardless of
provider
+ or harness. Never invent an attribution email or copy another agent's
identity.
+ Credit each contributing agent when multiple agents were involved.
+- Bot reviews require the same explicit disclosure; bot authorship alone does
not
+ replace it. Preserve existing attribution when editing public content.
+
+Use these templates consistently, substituting the actual agent identity and
+verified operator:
+
+- Commits: `Co-authored-by: ${agent name} <${agent email}>`
+- Issue/PR descriptions and comments:
+ `_AI-generated by ${agent name} on behalf of @${operator login}._`
+- If the operator lookup fails: `_AI-generated by ${agent name}._`
+
+The disclosure identifies the tooling and operator; it does not claim that a
human
+has reviewed or approved the content.
+
+## Merge attribution
+
+If any commit in a PR was AI-assisted, the squash-merge commit message MUST
include
+the AI co-authorship trailer. Preserve attribution when preparing other merge
+commit messages as well.
+
+## Project guidance
+
+See [CLAUDE.md](CLAUDE.md) for the project layout, build commands and
contribution checks.
diff --git a/CLAUDE.md b/CLAUDE.md
index 8914bba3..4089ad3a 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -1,5 +1,7 @@
# Camel-Kit
[email protected]
+
AI-agent workflows for the full Apache Camel integration lifecycle. The
product is
the **skills** — Markdown instruction files that guide AI coding agents — plus
a Java
CLI that installs them into user workspaces. Repo: `camel-kit`.
