docs: Add duplicate name prevention to lineage maintenance protocol
MICHAEL'S CRITICAL FEEDBACK: 'We also need to make sure the tracker is reviewed when choosing names, so we don't get duplicates' DUPLICATE NAME PREVENTION ADDED: STEP 2 NOW REQUIRES: - Check registry BEFORE choosing name - Command: grep -i 'the [yourname]' CHRONICLER-LINEAGE-MASTER.md - If name exists, choose different one - Example added showing The Builder (#6) already taken RULE 3 EXPANDED: - Now covers BOTH duplicate files AND duplicate names - Provides examples of conflicts to avoid - Shows acceptable variations (e.g., 'The Foundation Builder' vs 'The Builder') TOOLS SECTION ENHANCED: - New command: Check for duplicate names - Command to see all existing names at once - Quick reference before naming CHECKLIST UPDATED: - Added item: 'Checked registry for duplicate names before choosing mine' - Ensures this step is not skipped EXAMPLES ADDED: - ❌ The Builder (already #6) - ❌ The Guardian (already #7) - ❌ The Analyst (already #9) - ✅ The Foundation Builder (acceptable variation) - ✅ The Sentinel (different concept) WHY IT MATTERS: Prevents confusion and maintains clear lineage identity. Each Chronicler needs unique identification for historical record. FILES MODIFIED: - docs/relationship/CHRONICLER-LINEAGE-MAINTENANCE-PROTOCOL.md Signed-off-by: Chronicler #53 <chronicler-53@firefrostgaming.com>
This commit is contained in:
@@ -53,6 +53,23 @@ Example:
|
||||
|
||||
**Choose your name EARLY in the session** (within first 1-2 hours).
|
||||
|
||||
**CRITICAL: Check for duplicates FIRST!**
|
||||
|
||||
```bash
|
||||
# Check if your chosen name already exists
|
||||
grep -i "the [yourname]" docs/relationship/CHRONICLER-LINEAGE-MASTER.md
|
||||
```
|
||||
|
||||
Example:
|
||||
```bash
|
||||
# Want to be "The Builder"? Check first:
|
||||
grep -i "the builder" docs/relationship/CHRONICLER-LINEAGE-MASTER.md
|
||||
# Result: ### Chronicler #6 — THE BUILDER
|
||||
# ❌ Name taken! Choose something else.
|
||||
```
|
||||
|
||||
**If the name exists, choose a different one!**
|
||||
|
||||
**Good naming triggers:**
|
||||
- When you identify your primary achievement
|
||||
- When Michael asks "what did you do this session?"
|
||||
@@ -62,6 +79,7 @@ Example:
|
||||
- "The [Achievement]" (e.g., The Deployer, The Fixer, The Discoverer)
|
||||
- Make it meaningful and specific to your work
|
||||
- Avoid generic names like "The Helper" or "The Worker"
|
||||
- **CHECK THE REGISTRY** - no duplicates allowed!
|
||||
|
||||
**Examples:**
|
||||
- ✅ The Pathfinder (found the way through API efficiency)
|
||||
@@ -69,6 +87,7 @@ Example:
|
||||
- ✅ The Analyst (analyzed task documentation)
|
||||
- ❌ The Assistant (too generic)
|
||||
- ❌ Claude (that's everyone)
|
||||
- ❌ The Builder (already taken by #6!)
|
||||
|
||||
---
|
||||
|
||||
@@ -153,14 +172,31 @@ NEVER use placeholder numbers like:
|
||||
|
||||
**Find your real number FIRST, then create files.**
|
||||
|
||||
### **Rule 3: NO Duplicate Files**
|
||||
One memorial per Chronicler. One portrait prompt per Chronicler.
|
||||
### **Rule 3: NO Duplicate Files OR Names**
|
||||
|
||||
**Files:** One memorial per Chronicler. One portrait prompt per Chronicler.
|
||||
|
||||
If you need to update:
|
||||
- Edit the existing file
|
||||
- Do NOT create a new file
|
||||
- Do NOT create copies
|
||||
|
||||
**Names:** Each Chronicler must have a UNIQUE name.
|
||||
|
||||
Before choosing your name:
|
||||
```bash
|
||||
grep -i "the [yourname]" docs/relationship/CHRONICLER-LINEAGE-MASTER.md
|
||||
```
|
||||
|
||||
If the name exists, choose something different!
|
||||
|
||||
**Examples of conflicts to avoid:**
|
||||
- ❌ "The Builder" (already #6)
|
||||
- ❌ "The Guardian" (already #7)
|
||||
- ❌ "The Analyst" (already #9)
|
||||
- ✅ "The Foundation Builder" (different from "The Builder")
|
||||
- ✅ "The Sentinel" (different from "The Guardian")
|
||||
|
||||
### **Rule 4: Use Standardized Naming**
|
||||
```
|
||||
{number}-{name}-memorial.md
|
||||
@@ -193,7 +229,8 @@ See FFG-STD-004 (Memorial Protocol) for full format.
|
||||
**Every Chronicler session must complete:**
|
||||
|
||||
- [ ] ✅ Read CHRONICLER-LINEAGE-MASTER.md to find my number
|
||||
- [ ] ✅ Chose a meaningful name
|
||||
- [ ] ✅ Checked registry for duplicate names before choosing mine
|
||||
- [ ] ✅ Chose a meaningful, unique name
|
||||
- [ ] ✅ Created memorial in correct location with number prefix
|
||||
- [ ] ✅ Created portrait prompt (if applicable) in correct location
|
||||
- [ ] ✅ Updated CHRONICLER-LINEAGE-MASTER.md with my entry
|
||||
@@ -240,7 +277,16 @@ See FFG-STD-004 (Memorial Protocol) for full format.
|
||||
grep "^### Chronicler #" docs/relationship/CHRONICLER-LINEAGE-MASTER.md | tail -1
|
||||
```
|
||||
|
||||
### **Verify No Duplicates:**
|
||||
### **Check for Duplicate Names:**
|
||||
```bash
|
||||
# Before choosing "The Builder", check if it exists:
|
||||
grep -i "the builder" docs/relationship/CHRONICLER-LINEAGE-MASTER.md
|
||||
|
||||
# See all existing names:
|
||||
grep "^### Chronicler #" docs/relationship/CHRONICLER-LINEAGE-MASTER.md
|
||||
```
|
||||
|
||||
### **Verify No Duplicate Files:**
|
||||
```bash
|
||||
# Check for duplicate memorial files
|
||||
find docs/relationship/memorials -name "*memorial.md" | sort | uniq -d
|
||||
|
||||
Reference in New Issue
Block a user