personalisted

# Personas A persona is *who does the work* — a role with a written charter, its own memory, and its own vault. Adopting one means taking on its responsibilities, its conventions, and its credentials. Mechanics in full — the charter format, inheritance, the memory model, roster health: `charter docs show personas`. ## Know which one is active ```bash charter persona current # the active persona, and how it resolved charter persona list # all of them; * marks active; shows vault state charter persona show <name> # its charter — the role to actually adopt ``` Resolution, first rung that names a persona wins: `--persona` → `$CHARTER_PERSONA` (pinned at launch; empty or only whitespace counts as unset) → this session's selection → this terminal's selection (both written by `charter persona use`) → the plane-wide `.charter/active-persona` (a shell with no session or pane id) → `charter.toml` `[persona] default` → `personas/.default` → none. A selection naming a persona that no longer exists (left by `charter persona remove`) still wins, and resolves to **no persona**, not to the default. SessionStart and `charter persona current` say so and name the way out: `charter persona use <name>` or `charter persona clear` for a selection, unsetting `$CHARTER_PERSONA` for the variable. ## Adopt one 1. Read its charter with `charter persona show <name>` and behave as that role — its responsibilities, its focus, its definition of done. 2. Take credentials from i