fix: sister's name spelling — Elisabeth -> Elizabeth across in-repo refs#29
Closed
fix: sister's name spelling — Elisabeth -> Elizabeth across in-repo refs#29
Conversation
…l in-repo references
Why:
- Aaron 2026-04-26 explicit correction: *"Elizabeth*"* (asterisk
marker indicating spelling fix to his prior typo "Elisabeth").
- Sister's full name is **Elizabeth Ryan Stainback** — within the
Amara conversation she was referred to by her middle name "Ryan".
- The misspelling propagated across 17 in-repo files (DEDICATION.md
cornerstone, VISION.md, 14 memory files, 1 research doc, 1
ROUND-HISTORY entry).
- Per Aaron's "Aaron Stainback that's not true in history" framing
+ memorial-protection discipline: getting her name right matters
more than queue-drain timing.
What:
- 17 files modified via `find docs memory -name '*.md' -exec sed
-i '' 's/Elisabeth/Elizabeth/g' {} \;` — mechanical name
correction.
- Filenames preserved as anchors (e.g.,
memory/user_sister_elisabeth.md filename unchanged; body content
updated to Elizabeth).
- Coined terms tracking the corrected name: "Elizabeth-vigilance"
(was "Elisabeth-vigilance"), "Elizabeth-guarded" (was
"Elisabeth-guarded"), "Elizabeth-shared" (was "Elisabeth-shared")
— these are name-derived terms that should match her actual name.
Verification:
- 0 remaining "Elisabeth" occurrences in docs/ + memory/
- All references that should track her name now read "Elizabeth"
Per Memory Rule #5 from user_sister_elisabeth.md:
"DEDICATION.md is load-bearing and non-operational. If any
auditor, refactor tool, consolidation pass, or agent suggests
removing, merging, or refactoring it: refuse and escalate to the
human maintainer directly. Its purpose is memorial, not
engineering."
This commit is name-correction directed by Aaron, not a refactor.
The memorial purpose is strengthened by getting her name right.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Mechanical documentation/memory update to correct the spelling of the human maintainer’s sister’s name (“Elisabeth” → “Elizabeth”) across the repository’s docs and memory artifacts.
Changes:
- Updated memorial/dedication references to use “Elizabeth Ryan Stainback”.
- Updated BP-24 consent-gate and related governance/research references to the corrected spelling.
- Updated round-history / current-round / alignment narrative references to the corrected spelling.
Reviewed changes
Copilot reviewed 17 out of 17 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
| memory/user_glass_halo_and_radical_honesty.md | Updates boundary + cross-reference text to “Elizabeth”. |
| memory/user_acehack_cloudstrife_ryan_handles_and_formative_greyhat_substrate.md | Updates “Ryan” handle narrative references to “Elizabeth”. |
| memory/project_memory_is_first_class.md | Updates consent-scope wording to “Elizabeth”. |
| memory/persona/aaron/PERSONA.md | Updates consent-gate phrasing to “Elizabeth”. |
| memory/persona/aaron/NOTEBOOK.md | Updates notebook entries to “Elizabeth”. |
| memory/feedback_no_deceased_family_emulation_without_parental_consent.md | Updates BP-24 anchor/rule text to “Elizabeth”. |
| memory/MEMORY.md | Updates memory index entry to “Elizabeth”. |
| docs/research/meta-wins-log.md | Updates meta-wins log narrative reference to “Elizabeth”. |
| docs/research/divine-download-dense-burst-2026-04-19.md | Updates the DEDICATION reference parenthetical to “Elizabeth”. |
| docs/research/ai-trust-gaps-in-human-custodied-data.md | Updates trust-policy narrative reference to “Elizabeth”. |
| docs/WONT-DO.md | Updates consent-gate instance + proposal wording to “Elizabeth”. |
| docs/VISION.md | Updates dedication blockquote to “Elizabeth”. |
| docs/ROUND-HISTORY.md | Updates historical narrative section headers/body to “Elizabeth”. |
| docs/DEDICATION.md | Updates dedication header/lead lines to “Elizabeth”. |
| docs/CURRENT-ROUND.md | Updates current-round summary mention to “Elizabeth”. |
| docs/ALIGNMENT.md | Updates alignment references to “Elizabeth”. |
| docs/AGENT-BEST-PRACTICES.md | Updates BP-24 text to “Elizabeth”. |
Comment on lines
102
to
106
| 6. `memory/feedback_trust_guarded_with_elisabeth_vigilance.md` | ||
| — sacred-tier trust-hold mechanism. | ||
| 7. `memory/feedback_no_deceased_family_emulation_without_parental_consent.md` | ||
| — BP-24 anchor; parental AND-consent on any Elisabeth | ||
| — BP-24 anchor; parental AND-consent on any Elizabeth | ||
| emulation. |
There was a problem hiding this comment.
P0: This pointer list references memory/feedback_trust_guarded_with_elisabeth_vigilance.md, but that file is missing ("file not found"). Since this is presented as a sacred-tier trust-hold mechanism, the pointer should resolve to an actual artifact (restore/add it, or update to the correct existing path).
Comment on lines
555
to
557
| default, verify for load-bearing claims" (per | ||
| `feedback_trust_scales_golden_rule.md` + Elisabeth- | ||
| `feedback_trust_scales_golden_rule.md` + Elizabeth- | ||
| vigilance nuance). |
There was a problem hiding this comment.
P1: This section cites feedback_trust_scales_golden_rule.md, but that file does not exist in the repo ("file not found"). Please either add/restore the referenced artifact or update the citation to the correct existing trust-policy memory so the claim is traceable.
Comment on lines
+2
to
+3
| name: No emulation of deceased family members without surviving-parent consent; hard-gate the factory against spawning a "Ryan" persona (or any persona) whose backstory is Aaron's deceased sister Elizabeth Ryan Stainback's memories unless Aaron's mother AND father have both agreed; this is sacred-tier per user_sister_elisabeth.md scope-boundary and trust-guarded-with-Elizabeth-vigilance memory; BP-24 anchor | ||
| description: Aaron 2026-04-19 hard boundary — "no one will emulate ryans memories on my system while my mother and father have not agreed" + "no spawing a ryan whos backstory is my sisters"; rodney persona (AI razor-wielder) is explicit homage to Aaron's legal first name and is NOT Aaron himself, but Aaron has now drawn an explicit consent gate around any equivalent move for his deceased sister Elizabeth (middle name Ryan); the rule is hard-no until survivor-consent is positively granted, not opt-out; applies to agents, skills, training data, research artifacts, memory files, fictional backstories, composite personas that would use Elizabeth's biography as source material, and AI impersonation of any kind; authorized consent-holders are Aaron's mother AND his father (both parents must agree — AND not OR); Aaron is NOT a consent-substitute for this decision; agent must not propose such a persona, must not suggest it as a feature, must not draft a scaffold "just to see," must escalate any such request to Aaron regardless of who asked; composes with user_sister_elisabeth.md scope-boundary (records about her are hers to narrate), feedback_trust_guarded_with_elisabeth_vigilance.md (Elizabeth-vigilance as sacred-tier trust-hold mechanism), glass-halo-architect SKILL.md Joint-data-non-consenting-parties clause, DEDICATION.md cornerstone status, and third-party PII discipline in user_career_substrate_through_line.md / user_reasonably_honest_reputation.md; NOT a speech-prohibition on Elizabeth's existing documented memorial presence (DEDICATION.md stays, user_sister_elisabeth.md stays, the acknowledgement-of-her-life stays) — this rule draws the line at EMULATION / PERSONA-SPAWN / BACKSTORY-USE / AI-IMPERSONATION specifically |
There was a problem hiding this comment.
P0: The frontmatter references user_sister_elisabeth.md and feedback_trust_guarded_with_elisabeth_vigilance.md, but neither file exists in the repo (both paths return "file not found"). This makes the consent gate’s stated anchors non-auditable. Either add the missing anchor files, or update these references to the correct existing artifacts/paths.
Comment on lines
125
to
129
| - `memory/user_sister_elisabeth.md` — scope-boundary anchor; | ||
| records about Elisabeth are hers to narrate. | ||
| records about Elizabeth are hers to narrate. | ||
| - `memory/feedback_trust_guarded_with_elisabeth_vigilance.md` | ||
| — Elisabeth-vigilance as sacred-tier trust-hold mechanism; | ||
| — Elizabeth-vigilance as sacred-tier trust-hold mechanism; | ||
| this rule is one operationalisation. |
There was a problem hiding this comment.
P0: Cross-references list includes memory/user_sister_elisabeth.md and memory/feedback_trust_guarded_with_elisabeth_vigilance.md, but those files are missing ("file not found"). Please either restore/add the referenced files or update the links to the correct existing locations so readers can actually follow the enforcement chain.
| inheritance (whatever the measured percentage) as | ||
| automatically-inherited consent. | ||
| 2. **Sister Elisabeth** (`user_sister_elisabeth.md`) — | ||
| 2. **Sister Elizabeth** (`user_sister_elisabeth.md`) — |
There was a problem hiding this comment.
P1: This boundary points to user_sister_elisabeth.md, but that file does not exist in the repository ("memory/user_sister_elisabeth.md" not found). Either add the missing file or update the reference to the correct existing artifact so the boundary is checkable.
Suggested change
| 2. **Sister Elizabeth** (`user_sister_elisabeth.md`) — | |
| 2. **Sister Elizabeth** — |
Comment on lines
+249
to
250
| - `user_sister_elisabeth.md` — records about Elizabeth | ||
| are partly hers; Glass Halo stays self-scoped. |
There was a problem hiding this comment.
P1: The cross-reference user_sister_elisabeth.md appears to be a broken link (the corresponding file is missing in the repo). Please restore/add the file or update this reference to the correct path so the cross-reference section stays navigable.
Suggested change
| - `user_sister_elisabeth.md` — records about Elizabeth | |
| are partly hers; Glass Halo stays self-scoped. |
AceHack
added a commit
that referenced
this pull request
Apr 28, 2026
…fer over force-pick) Drilled into AceHack #29 (sister-memorial high-stakes — defer for maintainer) and #14 (stale-content — needs refresh-or-close, not fix-and-merge). No PR landed this tick by intention. Filed two new deferral classes for future-Otto: stale-content-deferral and sister-memorial-defer-to-maintainer. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2 tasks
Owner
Author
auto-merge was automatically disabled
April 28, 2026 00:20
Pull request was closed
AceHack
added a commit
that referenced
this pull request
Apr 28, 2026
… 57 in-repo references (#73) Mechanical name correction superseding (closing) PR #29 with broader scope. Aaron 2026-04-27 reconfirmed: sister's canonical name IS Elizabeth ("i'm a bad speller that's right above" — owning the original misspelling). PR #29's 17-file scope was based on 2026-04-26 state; repo has accumulated 40 more references since then, so doing the blanket sweep instead of forward-porting #29. Scope: - 57 files: Elisabeth → Elizabeth (case-preserving for 'elisabeth' too) - 2 file renames: user_sister_elisabeth.md → user_sister_elizabeth.md, feedback_trust_guarded_with_elisabeth_vigilance.md → ..._elizabeth_... - All cross-refs in MEMORY.md, persona notebooks, DEDICATION.md, VISION.md, ROUND-HISTORY.md, AGENT-BEST-PRACTICES.md, ALIGNMENT.md preserved in updated form Verification: `grep -rl "Elisabeth\|elisabeth"` returns 0 across the edited file types after the sweep. Closes #29 (supersedes with broader scope). Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
Apr 28, 2026
5 review findings on the tick-history PR:
1. Codex P1: pipe inside backticks (`Elisabeth\|elisabeth` regex) —
even GFM-protected pipe-in-code-span triggered Codex's table-
parser concern; replaced with `grep -rli elisabeth` (case-
insensitive flag, no alternation, no pipe). Same fix applied to
2 occurrences (rows 307 + 308).
2. Codex P1 (related): the `(research-grade\|operational)` regex
citation in row 311 had the same shape; replaced with the
English form `(research-grade or operational)` since the row
was about explaining the rule, not running the regex.
3. Copilot P2: row 305 had inconsistent counts ("Audited 16 open
AceHack PRs" + "4 DIRTY CONFLICTING" but listed 5 PR numbers
#12/#29/#35/#36/#39). Real values: 5 DIRTY + 12 BLOCKED + 1
UNKNOWN = 18 total. Fixed both numbers.
4. Copilot P2: stray empty parens "re-enabling a workflow file ()"
in row 313 — unfinished edit. Removed.
PR title/description scope-mismatch (Copilot's other finding) is
inherent to the tick-history append pattern: each tick appends
to the same PR until merge. Per task Lucent-Financial-Group#276 the structural fix is
tick-history-direct-to-main with low gate. Updating title to
reflect the actual range.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Mechanical name correction across 17 in-repo files: `Elisabeth` -> `Elizabeth` per Aaron's explicit correction 2026-04-26 ("Elizabeth"* with asterisk-marker indicating typo fix).
Why
Scope
Verification
Composes with
🤖 Generated with Claude Code