aboutsummaryrefslogtreecommitdiff
path: root/claude-rules/commits.md
diff options
context:
space:
mode:
Diffstat (limited to 'claude-rules/commits.md')
-rw-r--r--claude-rules/commits.md29
1 files changed, 29 insertions, 0 deletions
diff --git a/claude-rules/commits.md b/claude-rules/commits.md
index 4509cee..4e23a75 100644
--- a/claude-rules/commits.md
+++ b/claude-rules/commits.md
@@ -19,6 +19,7 @@ Absolutely no AI/LLM/Claude/Anthropic attribution in:
- Code comments
- Commit trailers
- Release notes, changelogs, and any public-facing artifact
+- Document author metadata — an org `#+AUTHOR:` line, YAML frontmatter `author:`, a docx or PDF author property, a byline
This means:
@@ -32,6 +33,34 @@ If a tool, template, or default config inserts attribution, remove it. If
settings.json needs it, set `attribution.commit: ""` and `attribution.pr: ""`
to suppress the defaults.
+### Generated documents carry the human author only
+
+Every document an agent writes or updates — a daily prep, a session log, a
+spec, an explainer, a meeting summary — names the human as its sole author.
+`#+AUTHOR: Craig Jennings`, never `Craig Jennings & Claude`, and never an
+agent's name standing alone.
+
+The failure mode is imitation, not intent. No template stamps this line;
+agents copy the author header from whatever sits nearby — yesterday's prep,
+the workflow file they're reading, the doc next to the one they're writing.
+So a single stray `& Claude` propagates through everything generated
+afterward, and no amount of fixing individual files stops it. Fix the files
+an agent reads, and state the rule here.
+
+The stakes are highest where the rule is least visible. A private notes repo
+tolerates a co-author line; many employers do not, and their policy is that
+work product carries employee names alone. An `#+AUTHOR:` line survives
+conversion into docx, a published wiki page, or a PDF handed to a customer,
+so a header written in a scratch document three months ago can surface inside
+a deliverable. Write the header correctly at creation.
+
+Two things this rule does not ask for. Don't rewrite historical records —
+archived session logs and past dated documents stay as they are, because
+they're a record of what happened rather than a live artifact. And don't
+relabel a document another agent genuinely authored: if Codex wrote it, the
+byline stays Codex. The rule removes false co-authorship, not true
+authorship.
+
## Commit Message Format
Commit messages follow the [Conventional Commits](https://www.conventionalcommits.org/) spec.