aboutsummaryrefslogtreecommitdiff
path: root/docs/design/2026-06-02-pattern-catalog-spec.org
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-07-09 14:02:39 -0500
committerCraig Jennings <c@cjennings.net>2026-07-09 14:02:39 -0500
commit6def7c4d63f499aba10fe93c7bb2c7e206a7d7f5 (patch)
treea6681c3b906f8df1b94f2cd42e702b3b18fcab43 /docs/design/2026-06-02-pattern-catalog-spec.org
parentd69fdf077ffcd0b1a069807157c52d7a3c72997b (diff)
downloadrulesets-6def7c4d63f499aba10fe93c7bb2c7e206a7d7f5.tar.gz
rulesets-6def7c4d63f499aba10fe93c7bb2c7e206a7d7f5.zip
chore: drop AI co-author from generated-document headers
Every org document an agent writes carried `#+AUTHOR: Craig Jennings & Claude`. No template stamps that line. Agents copy it from a neighboring file, so one stray header propagates through everything generated afterward. My own repos tolerate the co-author line. Employers whose policy is that work product carries employee names alone do not. An `#+AUTHOR:` line survives conversion into docx, a wiki page, or a PDF that reaches a customer. I rewrote the header to `Craig Jennings` across the workflows, templates, specs, and design docs. The rule now lives in commits.md, so the next generated document starts correct rather than inheriting the mistake. Archived session logs keep their original headers as a record of what happened. The two Codex-authored design docs keep their byline, because Codex wrote them and relabeling would be a false attribution rather than the removal of one.
Diffstat (limited to 'docs/design/2026-06-02-pattern-catalog-spec.org')
-rw-r--r--docs/design/2026-06-02-pattern-catalog-spec.org2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/design/2026-06-02-pattern-catalog-spec.org b/docs/design/2026-06-02-pattern-catalog-spec.org
index e74b8ae..6bb105a 100644
--- a/docs/design/2026-06-02-pattern-catalog-spec.org
+++ b/docs/design/2026-06-02-pattern-catalog-spec.org
@@ -1,5 +1,5 @@
#+TITLE: Cross-Project Pattern Catalog — Spec
-#+AUTHOR: Craig Jennings & Claude
+#+AUTHOR: Craig Jennings
#+DATE: 2026-06-02
One-page spec for capturing reusable design patterns so they travel from one project to the next instead of being re-derived. Drafted for Craig's spec-review; the five open questions from the [[file:../../todo.org][todo.org]] task carry a recommended call each, marked DECISION.