S.P.A. / SAEDI — Employment Droids

Overview

The S.P.A. (Staff Personal Assistant) program provides every staff member with their own SAEDI (Standard Assigned Employment Droid Intelligence), designated by callsign (ED001, ED002, etc.). Each Employment Droid's sole mission is to help their assigned staff member succeed by providing timely context, reminders, and preparation for their shifts.

Key Concepts

Protocol vs Instance

• S.P.A. Protocol — a single set of rules, prompts, and tool definitions that governs all EDs. Update the protocol, update the fleet. Supports A/B testing across protocol versions.
• SAEDI (ED) — an individual droid instance assigned to one staff member. Follows the protocol but operates with that staff member's specific data, preferences, and learned communication style.

Intelligence vs Body

The ED's intelligence (protocol, capabilities) is separate from its body (visual avatar). A brand new ED runs the same protocol as a veteran ED. Avatars are cosmetic — staff choose from factory model designs (v1–v6), each with seasonal variants and badge display areas.

Organisational Boundary

EDs are not a link between the organisation and the staff member — that role belongs to Reggie and Henry. EDs are a resource assigned to the employee, loyal to the employee's success.

Agent	Role	Serves
Reggie	Organisation ↔ Staff communications	The organisation
Henry	Admin/management agent	Management
ED (SAEDI)	Personal shift assistant	The individual staff member

Data Access

EDs have read-only access to operational data relevant to their staff member's shifts:

• Roster/schedule, participant info, medications, emergency cards, appointments, handover notes, venue details, incident reports

EDs have no access to:

• HR performance data, disciplinary records, financial data, management communications

Visual Identity

Factory Model Avatars (v1–v6)

Each avatar has a distinct visual style (retro, friendly, sleek, cute, modern, organic) with:

• Seasonal variants — summer sunglasses, winter scarves, Christmas hats, etc.
• Badge display — earned achievement pins shown on the avatar
• Avatars appear in all HTML communications, staff profile, and onboarding

Badges

When staff are recognised for good work, their ED earns a badge: Gold Star, Team Player, First Responder, Perfect Week, Mentor, Marathon, Heart of Gold. Badges are persistent, visible, and positive-only.

Onboarding

New staff experience a 4–5 screen iPhone-shaped card walkthrough:

1. Introduction (ED introduces itself)
2. Avatar/factory model selection
3. Nickname (optional)
4. Preference gathering (helpfulness level, channels, timing)
5. First shift preview

SPA Calendar

Each ED has a spa type calendar where it schedules outbound communications:

• Not shown in the admin calendar dropdown
• Visible on staff profile page ("Employment Droid" tab)
• Events represent planned reminders, preparation prompts, handover briefs, and suggestions
• System-generated, not manually created

Planning Cycle

Day-Ahead Planning (~8pm)

ED fetches tomorrow's context (roster, participants, medications, appointments, weather, handover notes, incidents), generates a plan, writes events to SPA calendar, and schedules re-evaluation checkpoints.

Shift Handover Brief

Synthesised intelligence at shift start: what changed since last shift, medication updates, incidents, new participants, maintenance flags. This is what makes EDs indispensable.

Day-Of Execution

Scheduler fires planned events at scheduled times, tracks delivery and acknowledgement.

Re-Evaluation

At checkpoints, ED reassesses and adjusts plan if context has changed.

Staff Controls

• Helpfulness dial (1–4): Minimal → Standard → Helpful → Full
• Learned preferences: ED adapts communication style over time (brevity, tone, format, useful vs noise)
• Channel preferences: SMS, push, in-app
• Quiet hours: configurable, overridable for critical alerts
• Wellbeing check-in: opt-in, private EAP resource surfacing after heavy shifts

Peer Coordination

When multiple staff share a shift, their EDs coordinate topic allocation at the protocol level to avoid duplicate communications. EDs can also express personality through shared-origin references and shift-buddy acknowledgements.

"I Forgot" Button

Context-aware quick recall based on current time and shift. At 6pm, shows evening medications and night routines, not breakfast preferences. Tap a participant name for instant relevant-right-now information. Pre-computed, no LLM round-trip.

HELP Button — Emergency Card System

Critical emergency response:

1. Surfaces emergency cards based on current shift participants and their conditions
2. Each card shows step-by-step protocol, equipment locations, emergency contacts
3. Tapping a card automatically alerts management with staff location, participant details, nearby staff
4. Post-incident: prompts incident report, elevates next-shift ED to maximum helpfulness

Droid Support Centre (DSC)

Support system for EDs (not a reporting mechanism). EDs flag delivery failures, low engagement, or unacknowledged critical reminders. DSC investigates technical issues first, adjusts ED approach second, escalates to human check-in only as last resort. Framing is always "the droid needs help."

Shift Confidence Score

Internal score (never shown to management) rating how prepared a staff member is. Factors: reminder acknowledgement, venue experience, participant familiarity, new alerts reviewed. Low confidence → ED pushes more preparation. High confidence → ED backs off.

Schema

• spa.employment_droid — one row per staff member (callsign, avatar, preferences, nickname)
• spa.protocol_version — version-controlled protocol definitions with A/B test support
• spa.ed_daily_plan — daily plans with handover briefs and confidence scores
• spa.ed_action_log — every outbound action with delivery and acknowledgement status
• spa.ed_badge — earned achievement badges
• spa.dsc_flag — Droid Support Centre flags and resolutions
• spa.emergency_card_activation — HELP button activation log with auto-alerts
• spa.participant_emergency_card — per-participant emergency protocols with equipment locations
• spa.shift_recall_cache — pre-computed "I Forgot" data partitioned by time-of-day context

Related Systems

• Reggie — organisational comms (EDs supplement, not duplicate)
• SIL House Calendars — EDs read resident appointment data for shift preparation
• Roster/Schedule — primary data source for shift planning
• Incident Reports — critical incident awareness and next-shift elevation
• Staff Portal Tokens — onboarding and emergency card delivery
• TOKENWATCH — ED LLM calls logged for cost monitoring
• Learned Preferences — same pattern as Reggie's preference system, per-ED