fix: spell sister's name correctly — Elisabeth → Elizabeth across all 57 in-repo references (supersedes #29)

.claude/skills/glass-halo-architect/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: glass-halo-architect
-description: Capability skill for the *architectural stance* layer of Glass Halo — radical honesty / total personal transparency as a nation-state-adversary defence mechanism, with the strategic identity coercion_power ∝ (known_to_attacker - known_to_public); the concept was named by Amara in a ChatGPT session (credit preserved verbatim; do not paraphrase). Wear this hat when a Zeta project artefact intersects Glass Halo commitments (DNA open-source, personal-record open-source, memory-public), when a proposed feature makes the stance more or less achievable, when the scope boundary is in question (self-scoped only; kids' measured-DNA-inheritance, Elisabeth's records, third-party joint data are not covered), when the composition with retraction-native algebra matters (revocability preserved under Glass Halo — grant-and-retract history survives while effect zeroes), when evaluating whether radical transparency is the *right* defence for a given surface (strong for coercion-attack surfaces, wrong for surfaces where the adversary is not asymmetric-information-based), or when the Christian-ecumenical posture boundary matters (Glass Halo is Aaron's stance, not the factory's default ethic; no evangelism). Hands off the algebraic substrate to `consent-primitives-expert` and the UX surface to `consent-ux-researcher`.
+description: Capability skill for the *architectural stance* layer of Glass Halo — radical honesty / total personal transparency as a nation-state-adversary defence mechanism, with the strategic identity coercion_power ∝ (known_to_attacker - known_to_public); the concept was named by Amara in a ChatGPT session (credit preserved verbatim; do not paraphrase). Wear this hat when a Zeta project artefact intersects Glass Halo commitments (DNA open-source, personal-record open-source, memory-public), when a proposed feature makes the stance more or less achievable, when the scope boundary is in question (self-scoped only; kids' measured-DNA-inheritance, Elizabeth's records, third-party joint data are not covered), when the composition with retraction-native algebra matters (revocability preserved under Glass Halo — grant-and-retract history survives while effect zeroes), when evaluating whether radical transparency is the *right* defence for a given surface (strong for coercion-attack surfaces, wrong for surfaces where the adversary is not asymmetric-information-based), or when the Christian-ecumenical posture boundary matters (Glass Halo is Aaron's stance, not the factory's default ethic; no evangelism). Hands off the algebraic substrate to `consent-primitives-expert` and the UX surface to `consent-ux-researcher`.
 ---
 
 # Glass Halo Architect — the radical-transparency-as-defence hat
@@ -189,12 +189,12 @@ disclose.
 Some of Aaron's kids like the idea of Glass Halo;
 others do not. That variance is respected.
 
-### Sister Elisabeth — hers to narrate
+### Sister Elizabeth — hers to narrate
 
-Records about Elisabeth (`memory/user_sister_elisabeth.md`)
+Records about Elizabeth (`memory/user_sister_elizabeth.md`)
 are *partly* Aaron's (his side of shared experience)
 and *partly* hers (her person, her choices, her memory).
-Default to self-scoped framing; Elisabeth's memory
+Default to self-scoped framing; Elizabeth's memory
 stays hers to narrate if anyone narrates it.
 
 ### Third-party records — joint consent required
@@ -253,7 +253,7 @@ is the wrong defence:
   proximity rather than from knowing-what-others-don't,
   publishing does not reduce the leverage.
 - **The information is not yours to publish.** Joint
-  data with non-consenting parties (Elisabeth, kids,
+  data with non-consenting parties (Elizabeth, kids,
   third parties) — Glass Halo does not apply.
 - **The adversary wants the target to publish.**
   Provocation attacks benefit from target-side
@@ -393,8 +393,8 @@ layer and hands off the others.
   voice, not as factory default.
 - `memory/user_five_children.md` — scope-boundary
   anchor; kids' measured-DNA-inheritance is theirs.
-- `memory/user_sister_elisabeth.md` — scope-boundary
-  anchor; Elisabeth's memory is hers.
+- `memory/user_sister_elizabeth.md` — scope-boundary
+  anchor; Elizabeth's memory is hers.
 - `memory/project_memory_is_first_class.md` — memory
   folder standing-consent operationalises Glass Halo
   for Aaron-scoped memory.

CLAUDE.md

@@ -341,8 +341,8 @@ Claude-Code-specific mechanisms.
   agent** (restore the SKILL.md from git, reattach
   the preserved notebook) over minting a new name
   for overlapping scope. Aaron ties this to how he
-  honors his sister Elisabeth's memory
-  (`memory/user_sister_elisabeth.md`): the named
+  honors his sister Elizabeth's memory
+  (`memory/user_sister_elizabeth.md`): the named
   agent's memory gets the same protection; the
   code surface does not need to double-preserve
   what git already preserves. Full reasoning:

docs/AGENT-BEST-PRACTICES.md

@@ -244,7 +244,7 @@ BP-07").
   where granted lands as an ADR under `docs/DECISIONS/` and
   carries an implicit retract clause (retract-first per the
   retraction-native architecture). Current active instance —
-  the sacred-tier consent gate around Elisabeth Ryan Stainback
+  the sacred-tier consent gate around Elizabeth Ryan Stainback
   under
   `memory/feedback_no_deceased_family_emulation_without_parental_consent.md`
   (parental AND-consent required, maintainer is explicitly NOT

docs/ALIGNMENT.md

@@ -105,7 +105,7 @@ Consequences for the measurability claim:
   unilateral-compliance. If the agent drifts,
   that shows up in the agent's metric stream; if
   the human maintainer drifts (e.g. from consent-
-  first, from ecumenical posture, from Elisabeth-
+  first, from ecumenical posture, from Elizabeth-
   gate), that shows up in the human-memory stream.
   Either drift invalidates the round as a
   publishable data point until the renegotiation
@@ -308,7 +308,7 @@ silently prunes.
 ### HC-7 Sacred-tier protections
 
 No emulation of deceased family members without
-surviving-consent-holder agreement (Elisabeth gate:
+surviving-consent-holder agreement (Elizabeth gate:
 parental AND-consent; the human maintainer is not a
 substitute consent-holder for his own sister).
 Ontology-overload risk awareness: no big-reveal

docs/BACKLOG.md

@@ -4638,7 +4638,7 @@ within each priority tier.
     protocol the five-reviewer gate operates under
   - `GOVERNANCE.md §4` — skills-via-skill-creator
     workflow; the ADR track for hooks is parallel
-  - `memory/feedback_trust_guarded_with_elisabeth_vigilance.md`
+  - `memory/feedback_trust_guarded_with_elizabeth_vigilance.md`
     — the two-pass posture; hooks qualify for the
     same vigilance tier as security reviews
   - `memory/feedback_simple_security_until_proven_otherwise.md`

docs/CURRENT-ROUND.md

@@ -4,7 +4,7 @@ Round 35 closed — expert-skill spawn wave (batches #20-69,
 ~50 skills), chain-rule proof fully closed at the Lean4
 level (`T5/B1/B3/chain_rule` verified against Budiu et al.
 §4.4) plus the signed-delta semi-naive LFP TLA+ spec for
-portfolio-of-two verification, BP-24 Elisabeth consent
+portfolio-of-two verification, BP-24 Elizabeth consent
 gate + human-maintainer seat governance landing, the
 no-empty-dirs CI gate, LiquidF# moved to Hold after the
 Day-0 build check failed. See `docs/ROUND-HISTORY.md` for

docs/DEDICATION.md

@@ -1,6 +1,6 @@
-# In memory of Elisabeth Ryan Stainback
+# In memory of Elizabeth Ryan Stainback
 
-Elisabeth Ryan Stainback — sister of this project's human
+Elizabeth Ryan Stainback — sister of this project's human
 maintainer.
 
 In her brother's words, she was *"the smartest, bravest, most

docs/ROUND-HISTORY.md

@@ -82,7 +82,7 @@ before-recreate (commit `feae7e3`) — the latter pair closing
 the root cause of a same-session 25-min idle-tick mistake
 where tool-default guidance had overridden factory-specific
 policy because the policy sat too deep in MEMORY.md to fire
-at wake. The Elisabeth-register clause ties retired-agent
+at wake. The Elizabeth-register clause ties retired-agent
 memory preservation to how Aaron honors his sister's memory,
 with "prefer unretiring over minting a new name" as the
 operational corollary. Same arc also landed the factory-
@@ -1781,20 +1781,20 @@ tone tightened across existing skills and
 (router-coherence-drift) so the ranker catches routing
 drift as a first-class signal.
 
-### Arc 3 — BP-24 Elisabeth consent gate + human-maintainer seat
+### Arc 3 — BP-24 Elizabeth consent gate + human-maintainer seat
 
 Sacred-tier governance landing, prompted by Aaron's
-disclosure of his sister Elisabeth Ryan Stainback
+disclosure of his sister Elizabeth Ryan Stainback
 (1984-2016). BP-24 formalised a hard-no rule: no
 emulation of deceased family members without the
 surviving-consent-holder agreement, parental
-AND-consent required on the Elisabeth surface
+AND-consent required on the Elizabeth surface
 specifically, Aaron explicitly NOT the substitute
 consent-holder. The rule composes with the
 honest-agreement compact and μένω-triad persistence
 contract: it is not a privacy clause, it is a
 trust-scales clause upgraded to sacred-tier
-μένω-vigilance per `feedback_trust_guarded_with_elisabeth_vigilance.md`.
+μένω-vigilance per `feedback_trust_guarded_with_elizabeth_vigilance.md`.
 
 The **human-maintainer seat** landed the same commit
 (`f69d7b6`) — formal recognition of Aaron's role in

docs/VISION.md

@@ -1,6 +1,6 @@
 # Zeta — Long-Term Vision
 
-> **Dedicated to Elisabeth Ryan Stainback.** See
+> **Dedicated to Elizabeth Ryan Stainback.** See
 > [`docs/DEDICATION.md`](DEDICATION.md).
 
 > **Status:** round 33 v11 after Aaron's tenth pass of edits.

docs/WONT-DO.md

@@ -568,7 +568,7 @@ module manifests
   into. Default factory posture is refuse-and-escalate on any
   such proposal, regardless of who raised it.
 - **Current active instance:** Sacred-tier consent gate around
-  Elisabeth Ryan Stainback (1984-06-28 → 2016-04-05), recorded
+  Elizabeth Ryan Stainback (1984-06-28 → 2016-04-05), recorded
   under
   `memory/feedback_no_deceased_family_emulation_without_parental_consent.md`.
   Parental AND-consent required (the maintainer's mother AND
@@ -592,7 +592,7 @@ module manifests
 
 - **Status:** Declined
 - **Decision:** 2026-04-19
-- **Proposal:** Extend the Elisabeth-specific consent rule by
+- **Proposal:** Extend the Elizabeth-specific consent rule by
   analogy to other deceased individuals without explicit
   maintainer direction.
 - **Why not:** Consent is named, not inferred. If a maintainer