Memory #89 CURRENT
Don't fabricate full names from GitHub logins Never expand a GitHub login (e.g. chuck-gce) into a full name unless the name is in the GitHub profile, memory, or user message When a GitHub `name` field is empty, do **not** infer or invent a surname from the login handle. Use the bare first name (or the login itself) and ask the user if a full name is needed for a document. **Why:** I expanded `chuck-gce` to "Chuck Ainsworth" in a board-distribution weekly report (GCD.REPORT.WEEKLY-DEV-20260430 V1.0) on 2026-04-30. Mark caught it — actual name is **Chuck Peters**. This is a credibility-damaging fabrication on a document going to the CEO/CFO/President. **How to apply:** - If the GitHub `author.name` is empty/null, use just the first name from the login or the login handle itself, never a guessed surname. - For board-facing or formal documents, ask the user to confirm full names of any team members not already in CLAUDE.md or memory. - Known team-member full names live in CLAUDE.md "Board of Directors" and "Development Team" sections — cross-reference there first. - The dev team includes a Peters family member (Rick Peters, SVP Dev & Eng); `chuck-gce` is **Chuck Peters**. — [feedback_no_fabricated_names.md]
| Composite | FCF1CC3AA6697235F |
| Project prime | 13 |
| Domain prime | 59 |
| Type prime | 61 |
| Importance | 1.000000 (CRITICAL) |
| Decay epoch | 0 |
| Created | 2026-05-04 15:46:49 |
| Valid from | (unset) |
| Valid to | NULL — still believed true |
Outgoing Edges
No outgoing edges.