My OS

logs/2026-06-20-athena-elt-profile-cleanup.md

Athena ELT Profile Cleanup

Context

Arijit asked Athena who the CTO was. Athena answered that CTO was only a role card and not a live profile.

That was wrong. Vulcan is the live CTO profile.

Cause

The My OS and Chowmes knowledge layers had drift:

11-elt-role-cards.md described ELT role cards but did not clearly state the current live profile roster.
MEMORY.md still said ELT roles were not yet live profiles.
Chowmes workspace files still referenced old melonie routing paths.
Live Hermes had multiple copies of USER.md and MEMORY.md; some were stale.

Correct Current Roster

Role	Profile	Name	Profile Status
CEO / Orchestrator	`default`	Athena	Live primary Telegram agent
CTO	`vulcan`	Vulcan	Existing profile
Product / UX Strategy	`arjuna`	Arjuna	Existing profile
Business / Revenue	`kubera`	Kubera	Existing profile
Legal / Risk	`prometheus`	Prometheus	Existing profile
COO	none	none	Deferred
CFO	none	none	Role card only
CMO	none	none	Role card only

Operating Rule

Athena should not answer from the role-card layer alone when Arijit asks who an advisor is.

She should check the current live-profile roster:

If the role is live, name the profile.
If the gateway is stopped, say the profile exists but is not currently exposed as an always-on chat surface.
If the role is not live, say it is currently a role card and explain what would justify promotion.

Verification

After cleanup, a fresh Athena prompt answered:

Vulcan is my CTO, and the exact live profile home path is `/opt/data/profiles/vulcan`.

The post-change Chowmes health check passed: gateway running, Telegram send test succeeded, runtime ownership healthy, and no root-owned runtime drift.