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: `--persona` → `$CHARTER_PERSONA` (pinned at launch) → local selection (`charter persona use`) → the committed default (`personas/.default`) → none. ## 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 its vault, never from anywhere else, and never print them (see the `secrets` skill). 3. Stay in role until asked to switch. **Do not switch the active persona unless asked.** Switching changes the session's identity for everyone downstream; routing a task does not. ## Route work instead of switching Every persona declares a `delegate-when:`, surfaced in its sub-agent description. - **Clear match → delegate** to that persona's sub-agent rather than doing it yourself. Delegation isolates context: only the result comes back, and the persona runs with *its*