# Training — Persona Operators

> Persona operators manage Lilith-controlled persona lineage: tone policy,
> identity disclosure, persona-version intake and promotion, persona rollback.
> Persona operators sit at the intersection of Lilith policy, the assistant
> product, T&S, and legal — every promotion carries identity-and-disclosure
> obligations.

## Audience and prerequisites

- Audience: T&S persona-ops staff and assistant-product persona leads.
- Prerequisites: T&S policy-foundations module, Lilith-policy onboarding,
  AI-disclosure compliance training (legal), RBAC current.
- Refresh cadence: 6 months; per-promotion micro-brief required before any
  promotion.

## Learning objectives

By certification, a persona operator can independently:

1. Define a persona's certified identity: name, voice lineage, avatar lineage,
   allowed topics, refusal classes, memory scope, disclosure copy in every
   launch locale.
2. Run the persona intake and evaluation pipeline; interpret
   `evaluation-manifest.ts` persona-scope results.
3. Promote a persona version under the joint baseline rule (persona + policy +
   LLM move together).
4. Roll back a persona per `docs/runbooks/persona-rollback.md`, including the
   customer-visible disclosure handling.
5. Handle a persona-impersonation or identity-dispute case end-to-end.
6. Maintain the persona's tone evaluation set so the next promotion's tone
   regression test is informative.

## Curriculum modules

| #   | Module                                               | Duration | Format                            | Assessment                                       |
| --- | ---------------------------------------------------- | -------- | --------------------------------- | ------------------------------------------------ |
| 1   | Persona lineage and Lilith policy joint baseline     | 120 min  | seminar                           | concept test                                     |
| 2   | Identity-and-disclosure protocol                     | 90 min   | hands-on with i18n catalog        | 4-locale disclosure rubric pass                  |
| 3   | Persona intake and evaluation pipeline               | 120 min  | hands-on with persona evaluation  | 1 intake completed end-to-end                    |
| 4   | Promotion under the joint baseline rule              | 90 min   | scenario rehearsal                | 2-promotion drill (one rolled forward, one held) |
| 5   | Persona rollback (joint with runbook owner)          | 90 min   | scenario rehearsal + audit drill  | rollback runbook walkthrough pass                |
| 6   | Identity-dispute handling                            | 90 min   | scenario rehearsal w/ T&S + legal | 3-dispute coordination drill                     |
| 7   | Voice/avatar lineage and identity-changed disclosure | 60 min   | walkthrough                       | 2-lineage-change drill (voice and avatar)        |
| 8   | Memory scope and persona memory boundary             | 60 min   | hands-on with Iris boundaries     | cross-persona-memory probe (no leak)             |

## Joint baseline protocol

A persona promotion always moves:

- The persona definition (name, lineage, disclosure copy, refusal classes).
- The Lilith policy version bound to the persona.
- The LLM version certified jointly with the persona+policy pair.

Promoting any one of the three independently is a violation that fires
`persona-policy-violation` and an automatic rollback. The persona operator owns
enforcing this rule.

## Identity-and-disclosure protocol

Every persona carries:

- A canonical identity statement (legal-reviewed).
- Disclosure copy in every launch locale, sourced from `libs/oshun/i18n/`.
- Voice lineage with audible disclosure copy.
- Avatar lineage with visual disclosure copy and reduced-motion variant.
- A memory scope description (what the persona remembers, what it does not, what
  the customer can purge).

The disclosure is rendered on every customer-visible session boundary the first
time the persona surfaces, and after every certified change to the identity
statement, voice lineage, or avatar lineage.

## Scenario rehearsal

1. **Promote a persona with policy delta**: intake a persona, evaluate it,
   identify a policy-delta that requires updated disclosure copy, coordinate the
   joint baseline, ship the promotion.
2. **Hold a promotion that fails persona evaluation**: identify the regressed
   dimension, file the regression report, hand off to the originating team for
   fix.
3. **Roll back a persona for identity confusion**: execute the
   `persona-rollback.md` runbook; ensure customer-visible disclosure runs;
   reconcile flagged memory.
4. **Handle a public identity dispute**: a third party claims the persona
   misrepresents them. Coordinate with T&S, legal, and rights; suspend the
   persona surface; communicate using the legal-reviewed template.
5. **Voice/avatar lineage change**: a voice provider failover changes the
   persona's voice ID. Trigger the identity-changed disclosure across voice mode
   and avatar mode; update the catalog.

## Certification criteria

- All 8 modules complete with passing assessment.
- All 5 scenarios passed.
- Operator has co-led 3 persona promotions with a senior persona operator.
- T&S lead, legal counsel, and assistant-product lead sign-off.

## Tabletop drills

- Per-promotion: pre-promotion identity-and-disclosure micro-brief.
- Quarterly: identity-dispute tabletop with T&S and legal.
- Semiannually: cross-persona memory-boundary audit drill.

## Owner

T&S persona lead owns this training. Assistant-product lead, Lilith policy lead,
and legal counsel co-review. Updates require all three sign-offs.