Personas
A synthetic customer with a SOUL (who they are) and a growing memory of everything they've been through. Not a static profile — it remembers and evolves.
Why it matters: Answers come from lived experience and shift over time, instead of repeating the same line.
What it holds
- SOUL — the authoritative identity (role, company context, values, quirks)
- Goals, constraints and pain points
- Avatar path + provenance (what the persona was derived from)
- Memory lives in separate, time-indexed records (see below)
Data shape
A real, trimmed record (stored as JSON):
{
"id": "persona_7f3…", "slug": "lena-vogt",
"display_name": "Lena Vogt",
"role": { "title": "Head of Operations", "seniority": "lead" },
"company_context": { "industry": "logistics", "size": "120" },
"segment": { "name": "ops leaders at mid-size firms" },
"goals": ["ship the Q3 rollout"], "constraints": ["no new headcount"],
"pain_points": ["Monday triage eats the morning"],
"soul": { "rendered": "data/personas/lena-vogt/SOUL.md" },
"avatar": { "path": "data/personas/lena-vogt/avatar.png" },
"created_at": "2026-03-02T…", "updated_at": "2026-05-30T…"
}What it's made of
A persona is a graph Node. Its memory is separate records — ExperienceEvent, DailySummary, PainPointObservation — each keyed by persona_id and a timestamp, so recall and time-travel work.