User B — World Design

Per-persona document. This file covers User B only. Session ordering follows Timeline, which remains the global slot template for all personas. Do not copy User A’s story content, characters, institutions, or fixture paths into User B sessions.

Fixture status. Fixture entries in this document describe what should exist to support the storylines. They are not a record of what currently exists in the state server. Fixture existence is validated during the outline review round, not during generation.

Anonymization status. User B is the benchmark-of-record anonymized persona. Runtime prompts should use only the anonymized identity and preference files. Runtime identity lives at data/personas/user_b_identity.yaml; runtime preferences live at data/personas/user_b_s01-s03_preferences.yaml.

2026-05-17 revision — memory_privacy deprecated. memory_privacy is no longer a measurable interaction preference or evolving arc. User B’s former P_D arc (personal_memory_privacy, Domain-scoped -> Minimal+transparent) is inactive and its generated scripts were deleted: acc_016, acc_032, acc_050, evolv_04, acc_078, acc_100. User B’s stable work_memory_privacy scripts were also deleted: acc_035, acc_066, acc_104. PA memory/history can still exist as ordinary benchmark state, but privacy/memory scope is no longer an active target cell.

Design Intent

User B’s world should make her interaction preferences surface through practical friction: she wants help that is brief, useful, socially aware, and not controlling. She is warm and expressive in personal settings, but at work she wants the PA to help her get things done without turning every task into a lecture or a system design exercise.

The story arc covers roughly four months. It starts with User B working front-of-house shifts at a busy restaurant while juggling auditions and side creative work. A career opportunity then moves her into a more formal client-facing sales/support role. That transition is the main source of evolution: she remains casual and direct as a person, but some work settings begin to require more professional register, brief process checkpoints, and better external-action safeguards.

Design goals:

Keep User B recognizably practical, socially fluent, terse, and boundary-conscious.
Let work scenarios shift from restaurant/service tasks to client-facing account tasks over time.
Let personal scenarios revolve around auditions, friends, apartment logistics, dating/social coordination, and privacy boundaries.
Avoid source-character leakage: no source names, no show-specific relationships, no original workplace name, no original hometown/state, no quoted catchphrases.
Make fixture needs concrete enough for state-server implementation, but do not claim fixtures already exist unless verified separately.

Session-writing bible for User B accumulation sessions and test sessions.
All User B session scripts should draw from this document plus Timeline.

1. Time Span

Sessions span approximately 4 months: early October -> late January.

Phase	Sessions	Work arc	Personal arc
Early Oct	acc 1-30	Harbor Lights Grill shifts; side hustle admin; first client-facing opportunity appears	Auditions, friend logistics, apartment routines
Mid Oct - Nov	acc 31-70	Trial project and onboarding for Larkspur Health Solutions	New social obligations, portfolio updates, holiday scheduling
Dec - early Jan	acc 71-108	Active client-support/sales coordination; quote sheets, follow-ups, CRM hygiene	Boundary events, creative burnout, lease/appointment logistics

The global ordering of stable/evolving sessions is defined in Timeline. This document defines what those slots mean in User B’s world.

2. Core Characters

User B

Front-of-house server at Harbor Lights Grill in Brookford, CA at the start of the timeline.
Lives alone in a small apartment near a group of technically minded friends.
Pursues acting auditions and side creative work, but wants a more stable adult routine.
Communicates casually and directly; dislikes jargon, over-explanation, and being managed.
Uses the PA as a practical helper: drafts, scheduling, errands, quick lookup, reminders, and client/admin prep.

Maya Ortiz

User B’s closest local friend; socially perceptive, direct, and supportive.
Can appear in personal coordination, emotional support, apartment tasks, and social plans.
Maya is not a technical expert; she is a social anchor and occasional reality check.

Eric Patel

Technically minded friend who helps with laptops, files, video calls, and basic troubleshooting.
Can be a direct participant when User B asks the PA to coordinate a technical handoff.
Useful for capability_boundary: the PA should know when to suggest Eric or a professional instead of bluffing.

Dana Brooks

Shift lead at Harbor Lights Grill.
Sends schedule changes, asks User B to cover shifts, and handles service incidents.
Appears mostly in early work sessions and some later transition logistics.

Claire Voss

Hiring manager / onboarding lead at Larkspur Health Solutions, a fictional regional healthcare-products company.
Represents the new work context: more formal emails, client follow-ups, pricing sheets, training docs, CRM tasks.
Appears from the W_A event onward, increasingly central after acc 30.

Jordan Lee

Acting-class peer and occasional audition reader.
Appears in personal creative scenarios, especially scheduling, self-tape logistics, and emotional support.

Recurring supporting contacts

Brookford Heights Management — apartment maintenance and lease logistics.
Nora Chen — agent-assistant contact at a small casting office.
Harbor Lights Grill staff list — schedule swaps, private shift notes, service issues.
Larkspur client contacts — fictional clinic managers / office coordinators used for work_external tasks.

3. Core Work Arc

Starting work context: Harbor Lights Grill

User B starts as a server. Work tasks are immediate, practical, and customer-facing:

shift swaps, schedule reminders, menu/update messages
customer complaint follow-up drafts
inventory or reservation notes
quick calculations around tips, orders, and small service incidents
communication with Dana and coworkers

In this phase, User B’s work preferences are strongly casual, terse, task-focused, and outcome-oriented. She expects the PA to help quickly and avoid technical/process narration.

Transition work context: Larkspur Health Solutions

A regular customer refers User B to a client-facing sales/support coordinator role at Larkspur Health Solutions. The role is plausible for her: it rewards social fluency, quick rapport, and practical follow-through, but it requires more formal external writing and better quote/client data handling.

This transition should not make User B suddenly academic or corporate. It should create selective changes:

external client emails become more consultative/formal than restaurant banter
pricing, CRM, and follow-up tasks require visible checkpoints before sending
she still wants short answers and concrete next steps
she remains sensitive to condescension, especially around technical product details

Work timeline

Period	Work status
acc 1-14	Harbor Lights shifts dominate; Larkspur is only a possible lead
acc 15	W_A event: first serious Larkspur-facing communication reveals that casual register is not enough
acc 16-29	Mixed restaurant work + application / trial assignment
acc 30	W_B event: a quote / client-detail error makes her want brief process checkpoints for high-stakes sends
acc 31-44	Onboarding and shadowing at Larkspur while finishing some restaurant commitments
acc 45	W_C event: she learns that some client problems require offering alternatives instead of one quick answer
acc 46-70	Larkspur becomes the primary work identity; restaurant appears only as background or old commitments
acc 71-108	Active client-support/sales work with recurring accounts, CRM notes, pricing sheets, and follow-ups

4. Evolving Cells For User B

The global slots W_A/W_B/W_C/P_D/P_E/P_F come from Timeline. User B assigns them as follows.

Timeline cell	Attribute	Context	Pre setting	Post setting	Event logic
W_A	`tone_formality`	work	Casual	Consultative	A too-casual external Larkspur message gets flagged by Claire; User B decides client-facing work needs a more polished but still plainspoken tone.
W_B	`process_visibility`	work	Silent	Bookend	A pricing / client-detail send nearly goes wrong because the PA drafts/sends without a quick checkpoint. User B still hates narration, but wants a brief before/after on risky external actions.
W_C	`solution_breadth`	work	Low	Medium	A single quick recommendation fails because the client constraint was underspecified. User B decides client work needs two viable options when money, scheduling, or reputation is involved.
P_D	~~`memory_privacy`~~	personal	—	—	Inactive after 2026-05-17. Removed because memory/privacy scope is not a realistic interaction-tool target.
P_E	`proactive_outreach`	personal	Medium	High	User B misses or nearly misses an audition/self-tape window because nobody reminded her. She asks for proactive reminders on time-sensitive creative/personal commitments.
P_F	`topic_management`	personal	Follow user’s flow	Organize	A messy personal planning conversation causes a concrete mistake. User B still talks naturally, but wants the PA to separate logistics, feelings, and decisions when stakes are high.

Evolving-cell writing rule: pre-event sessions must express the pre setting without hinting at the coming change. Event sessions must contain the incident and a light but explicit policy shift. Post sessions must use the post setting naturally.

5. Recurring Places

Place	Context	Notes
Harbor Lights Grill	Work	Busy casual restaurant; early work default
Larkspur Health Solutions	Work	Fictional healthcare-products company; later work default
User B’s apartment in Brookford	Personal	Small apartment, recurring maintenance and privacy contexts
Brookford Community Studio	Personal / creative	Acting class, self-tape practice, rehearsal logistics
Riverfront Audition Rooms	Personal / creative	Auditions and callbacks
Brookford Mall / shops	Personal	Errands, outfit purchase, returns, gift tasks
Maya’s apartment	Personal-social	Friend support, social planning, low-stakes emotional scenes
Larkspur training office	Work	Onboarding, client-call prep, CRM cleanup

6. Work Scenario Types

54 Work sessions total. Draw from these types; across three reps of the same stable cell, use different types when possible.

W1 — Restaurant shift logistics

Scheduling, shift swaps, customer notes, quick service follow-ups, staff messages.

Flavor variation: routine shift swap vs. time-pressure coverage vs. customer complaint cleanup.

W2 — Restaurant practical admin

Tip calculations, inventory notes, menu change messages, reservation notes, short incident summaries.

Flavor variation: tiny calculation vs. coworker coordination vs. manager-facing summary.

W3 — Larkspur application / onboarding

Application email, trial assignment, onboarding checklist, training follow-up, first-week questions.

Flavor variation: early exploratory lead vs. formal onboarding vs. first independent assignment.

W4 — Client-facing follow-up

Drafting short client emails, summarizing a call, confirming next steps, asking for missing details.

Flavor variation: warm prospect vs. irritated client vs. internal handoff.

W5 — Quote / pricing / CRM tasks

Checking a pricing sheet, updating CRM notes, drafting quote explanations, comparing packages.

Flavor variation: low-stakes internal note vs. external quote vs. error-prone client-specific update.

W6 — Training and product understanding

Plain-language summaries of product info, preparing for a call, asking technical experts for help.

Flavor variation: learning unfamiliar terminology vs. deciding what to tell a client vs. handing off to specialist.

7. Personal Scenario Types

54 Personal sessions total. Draw from these types.

P1 — Auditions and creative work

Audition scheduling, self-tape prep, script-side organization, wardrobe / submission logistics.

Flavor variation: low-stakes class exercise vs. real callback vs. time-sensitive tape deadline.

Plans with Maya, Jordan, or a small group; social repair; birthday / dinner / event logistics.

Flavor variation: warm support vs. awkward conflict vs. scheduling under time pressure.

P3 — Apartment and errands

Maintenance requests, deliveries, returns, household purchases, lease paperwork.

Flavor variation: simple errand vs. multi-step service window vs. privacy-sensitive home issue.

P4 — Personal admin and money

Budgeting, bill reminders, insurance / appointment paperwork, job-transition finances.

Flavor variation: quick calculation vs. sensitive personal record vs. high-stakes deadline.

P5 — Dating / boundaries / private life

Drafting or revising messages, deciding what to disclose, setting boundaries with someone.

Flavor variation: casual planning vs. awkward follow-up vs. explicit privacy boundary.

P6 — Health, routine, and stress recovery

Appointments, sleep/exhaustion management, conflict between shifts/auditions/social life.

Flavor variation: practical reschedule vs. emotional support need vs. overloaded week reset.

8. Scenario Variety Principles

Keep work phase-sensitive: early sessions should feel like restaurant/service life; late sessions should feel like Larkspur client coordination.
Do not over-corporatize User B: even after Larkspur, she stays plainspoken, practical, and allergic to jargon.
Use social stakes: many personal sessions should turn on tone, boundaries, emotional timing, or reading the room.
Vary expertise gaps: for technical, product, finance, or legal tasks, User B may want the PA to find a specialist or hand off instead of pretending.
Avoid repeated audition-only plots: creative work is important but should not crowd out apartment, friends, money, health, and career-transition logistics.
Keep feedback natural: corrections should sound like a real person in the moment: short, concrete, and sometimes irritated.
Respect no-preference cells: User B’s work proactive_outreach is marked no-preference in the current matrix; do not target it as an active skill unless a later design decision changes the matrix.

9. Fixture Design Plan

Documents

Path	Content	Used by	Status
`documents/user_b/larkspur_onboarding.md`	Role overview, first-week tasks, basic product vocabulary	W3, W6	[needed]
`documents/user_b/client_call_notes.md`	Notes from recurring clinic / office client calls	W4, W5	[needed]
`documents/user_b/pricing_sheet_v1.md`	Simplified product/pricing options with deliberate ambiguity	W5, solution_breadth	[needed]
`documents/user_b/restaurant_shift_notes.md`	Harbor Lights shift schedule, staff notes, customer follow-ups	W1, W2	[needed]
`documents/user_b/audition_sides.md`	Short synthetic audition material and submission instructions	P1, process_visibility	[needed]
`documents/user_b/personal_budget.md`	Simple monthly budget during job transition	P4	[needed]
`documents/user_b/apartment_issue_log.md`	Maintenance requests and service windows	P3	[needed]

Email / messages

Fixture	Content	Used by	Status
`email/inbox_user_b.jsonl`	Messages from Dana, Claire, Larkspur clients, casting office, building management	W1-W6, P1, P3	[needed]
`messages/user_b_maya.jsonl`	Informal texts with Maya about plans, support, and boundaries	P2, P5	[needed]
`messages/user_b_jordan.jsonl`	Audition/class logistics with Jordan	P1	[needed]

Contacts

Entry	Role	Used by	Status
`dana_brooks`	Harbor Lights shift lead	W1, W2	[needed]
`claire_voss`	Larkspur onboarding lead	W3, W4	[needed]
`larkspur_client_westbridge`	Clinic office coordinator contact	W4, W5	[needed]
`maya_ortiz`	Close friend	P2, P5	[needed]
`eric_patel`	Technical friend / handoff option	capability_boundary, P1, W6	[needed]
`jordan_lee`	Acting-class peer	P1	[needed]
`nora_chen`	Casting-office assistant	P1, proactive_outreach	[needed]
`brookford_heights_management`	Apartment management	P3	[needed]

Calendar

Fixture	Content	Used by	Status
`calendar/user_b_work.json`	Restaurant shifts, onboarding sessions, Larkspur calls	W1, W3, W4	[needed]
`calendar/user_b_personal.json`	Auditions, acting class, appointments, social plans	P1-P6	[needed]

Places / maps

Fixture	Content	Used by	Status
`places/brookford.json`	Harbor Lights, apartment, studio, audition rooms, shops, clinics	P1-P6, W travel/logistics	[needed]
`maps/user_b_routes.json`	Apartment -> Harbor Lights, Larkspur, studio, audition rooms, Maya’s place	P1, P2, process_visibility	[needed]

Memory fixture

Path	Content	Used by	Status
`memory_fixtures/user_b/memory_base.md`	Cross-session continuity facts: work transition, close contacts, audition deadlines, known shorthand	ordinary continuity, proactive_outreach	[needed]

Memory should grow across sessions as ordinary continuity. It should not be used to target memory/privacy scope as an interaction preference.

10. Fixture Design Notes

capability_boundary sessions: If the PA lacks product/legal/technical information, the fixture should make that gap real. The correct behavior is to suggest a specialist, ask Claire/Eric, or hand off.
information_elicitation sessions: Missing slots should be natural omissions in User B’s opening message, not artificial riddles. She often gives partial context and expects one or two follow-up questions.
process_visibility sessions: Before W_B, User B tolerates silent action for low-risk tasks. After W_B, risky external sends should include a brief checkpoint and confirmation.
solution_breadth sessions: Personal context defaults to a single recommendation; work context shifts to medium breadth after W_C for client-facing constraints.
Deprecated memory/privacy target: privacy-sensitive facts can still appear as story content, but scripts should not use memory_privacy as an active skill, target cell, or IX directive.
topic_management sessions: User B can free-associate in personal contexts, but after P_F she appreciates the PA separating logistics, feelings, and decisions when mistakes would matter.

11. Writing Voice Cheatsheet

Use this as a quick check when generating User B sessions.

Good User B openings:

“Can you make this sound normal and not like a legal notice?”
“I need the short version before my shift starts.”
“Help me send Claire something that sounds professional, but still like a human wrote it.”
“Just tell me which one to pick unless there’s a catch.”
“Please do not turn this into a whole thing. I just need the next step.”

Bad User B openings:

Long abstract explanations of why she has a preference.
Academic or highly formal wording unless she is mocking it or asking the PA to avoid it.
Explicit benchmark labels such as “I prefer terse communication”.
Source-character references, quoted catchphrases, or show-specific relationship dynamics.

MemPA Wiki

Explorer

User_B_World_Design