Stephania — Historical Context (Retired 2026-04-24)

DISAMBIGUATION REQUIRED — READ BEFORE ACTING.

The name “Stephania” (and the common misspelling “Stefania”) refers to TWO COMPLETELY DIFFERENT entities in this system. This hub exists to prevent confusion. Always clarify which entity is meant before acting on any request involving these names.

CRITICAL DISAMBIGUATION: Person vs Agent

	Stephania (person)	stefania / stefania-asst (agents)
What it is	Henry’s wife — real human	Two retired OpenClaw automation-tier agents
Phone	+16612935744	n/a (agents have no phone)
Status	ACTIVE — iMessage handled by Aurora	RETIRED 2026-04-24 — empty shell configs
iMessage chat	Active group chat with Henry + Aurora	n/a — agents never had iMessage
Aurora role	Aurora serves as Stephania’s personal assistant	Aurora absorbed these agents’ scope
SOUL.md	n/a (not an agent)	stefania: no independent SOUL.md; stefania-asst: auth-profiles only
Current location	_retired/ dir + empty active entries	_retired/ dir (3 documented retirements 2026-04-24)

The correct spelling matters:

• “Stephania” = Henry’s wife (person, real human, active)
• “stefania” / “stefania-asst” = the retired agents (lowercase s, agent configs)

---

Stephania (person) — Active iMessage context

Stephania is Henry’s wife. She participates in a three-person group iMessage chat with Henry (+16194033648) and Aurora (+19492333790). Aurora serves as her personal assistant for family logistics.

Chat details:

• chat_guid: iMessage;+;chat166451015733383848
• Participants: Stephania (+16612935744), Henry (+16194033648), Aurora (+19492333790)
• Style: Group iMessage (3 people)
• Aurora role: personal_assistant (allowlist category: personal)
• Aurora voice: warm/emoji — explicitly distinct from terse team-leader voice used in RERI business chats

Active as of 2026-05-04. Aurora handles all iMessage routing for this chat. Wired per project_stephania_aurora_chat_wired (2026-04-23). Solara does NOT have access to this chat — Henry explicit denial 2026-04-23.

Full wiring details: project_stephania_aurora_chat_wired

---

Why retired (agents)

The stefania and stefania-asst agent configs were retired on 2026-04-24 as part of the agent registry reconciliation audit. Both were empty shell configs:

• stefania: Haiku model. Specialized persona config, no independent SOUL.md. Escalated to main. Had no active workflows at retirement — scope was absorbed into Aurora’s personal-assistant skill layer.
• stefania-asst: Auth-profiles only. No model config in openclaw.json — gateway sessions dir only. No active workflows.

Why the scope moved to Aurora, not a new agent:

1. Aurora already had iMessage routing infrastructure (port 18802, imessage-responder skill)
2. Separate agent would duplicate webhook listeners and create identity ambiguity
3. Aurora’s SOUL supports warm personal voice as a skill-layer mode — no SOUL edit required
4. Solara governance principle: “don’t create new agents when skill composition solves it”

The retirement was recorded in the 2026-04-24 agent registry reconciliation (AGENT-REGISTRY.md reconciliation note). Three additional retirements documented at the same time: default (empty shell), betteracq (merged into acquisitions), dealcmd (merged into dispo).

---

Quick reference

Field	Value
Role	support-agent (retired)
Active	no — retired 2026-04-24
Retired date	2026-04-24
Communication channel	n/a (agents retired; person Stephania handled via Aurora iMessage)
Decision authority	none
Agent handles domain	n/a — scope absorbed by Aurora
Escalates to	n/a
HubSpot owner	no
Discord user	n/a
Archive location	_retired/ directory (empty shell configs preserved per feedback_archive_not_delete)

Responsibilities (historical — pre-retirement)

The stefania agent was intended as a specialized Haiku-tier persona for personal assistant tasks. The stefania-asst config was the auth layer for that persona. Neither had meaningful production workflows before retirement — the scope was never fully operationalized, making migration to Aurora’s skill layer the correct path.

Agent handoff pattern (current — post-retirement)

There is no handoff from the retired agents. The current pattern:

1. Stephania sends iMessage to group chat
2. Port 18802 imessage-webhook receives the message
3. Aurora imessage-responder skill reads chat_guid → matches allowlist → applies personal_assistant role
4. Aurora responds with warm/emoji voice per skill-brief.md §1.1.5
5. If task requires follow-up (e.g., travel booking): Aurora tracks in active task state and follows up proactively

If you see the name “stefania” in an agent file or config, it refers to the retired agent, not Stephania the person. Do not attempt to wake or reactivate the stefania or stefania-asst agents — the scope is properly handled by Aurora.

Communication channels

Entity	Channel	Status
Stephania (person)	iMessage group chat chat166451015733383848	ACTIVE — handled by Aurora
stefania (agent)	n/a	RETIRED — no channels
stefania-asst (agent)	n/a	RETIRED — no channels

Recent decisions

1. Aurora iMessage wiring for Stephania (2026-04-23) — Henry approved Aurora as Stephania’s personal assistant; Solara explicitly denied access. Active task at wiring: Booksi travel booking Apr 29–May 3. See project_stephania_aurora_chat_wired
2. stefania + stefania-asst retired (2026-04-24) — agent registry reconciliation audit; empty shell configs moved to _retired/; scope absorbed by Aurora skill layer
3. Disambiguation rule established — “Stephania” (person) vs “stefania” (agent) must always be clarified before action; this hub is the canonical reference

Cross-links

Current handler for Stephania (person) iMessage

• _summary — imessage-responder skill, personal_assistant role
• project_stephania_aurora_chat_wired — full wiring + allowlist + skill-brief details

Integration hubs (historical context)

• openphone-quo — Quo handler at :18792; separate from iMessage handler but same ecosystem
• salesmsg — SalesMsg handler; not used for Stephania chat

Team hubs

• henry-founder — Henry authorized Aurora access; Solara denied
• special-agents — Aurora identity hub; warm-voice mode documented there

Governance references

• memory-rule-clusters — agent-domain cluster covers identity rules
• g-gates-network — G-FAILED-SERVICE-MTTR would flag any lingering stefania service
• agent-registry — canonical list; stefania/stefania-asst marked retired

Feedback rules

• feedback_archive_not_delete — why agents are in _retired/ not deleted
• feedback_agent_identity_first — check SOUL.md before any agent change
• feedback_action_gate_violation_repeated — Aurora cannot send without authorization

System maps

• agents-tier-structure — fleet tier visualization (retired agents excluded from active counts)

Open issues / TODOs

• 13 unrecorded retirements in _retired/ beyond the 3 documented (default, stefania, stefania-asst) — audit pending Henry authorization
• investorlift-angel/-h2/-h3 appear in BOTH active AND retired lists — dedup pending Henry authorization (separate from stefania)

Recent activity

• 2026-05-04: hub created (W3-S2) — disambiguation hub to prevent person/agent confusion
• 2026-04-24: stefania + stefania-asst retired (agent registry reconciliation)
• 2026-04-23: Aurora wired as Stephania’s personal assistant; group iMessage chat activated