Lucy — Control Center

Drafts awaiting your approval

Lucy emails freely inside the autonomous domains below. Anything outward-facing lands here (and pings you on WhatsApp) for a one-tap decision — approve, edit, or scrap. You can also reply approve 12 / edit 12: make it warmer / scrap 12 straight from WhatsApp.

Lucy's channels

Every medium Lucy can speak through. One person across channels is ONE contact with one continuous memory — a chat started on WhatsApp continues over SMS or email without losing the thread. Calendar and voice join this list next.

Hold calendar invites with outside attendees for my approval (recommended)

Email identity — lucy@intelgic.com

Lucy sends and reads mail as her own Google Workspace mailbox via a service account with domain-wide delegation — no password stored, revocable in one click from the Workspace admin console. She answers internal mail autonomously; the domains below define "internal".

Auto-answer inbound email (off: still recorded, just no auto-reply) Signature (HTML — appended to every email) Service-account JSON (paste to set or replace — never displayed again)

Memory controller

Global concepts are Lucy's app-wide, all-user memory: durable knowledge she extracts from conversations, reinforces over time, and injects into every chat and digest. Pin a concept to guarantee it's always in her head; edit or delete anything.

Learn new concepts from conversations automatically

Global concepts

	Concept	Content	Conf.	×

Memory upkeep

Nightly (02:00 America/Los_Angeles) Lucy merges near-duplicate concepts — contradictions resolve toward the newer statement with a dated note, genuinely unresolvable ones get flagged ⚠️ below for your review — decays concepts that haven't been used in two weeks, prunes dead ones, and compacts very long threads into rolling summaries. Memory that builds and stays fresh instead of silting up.

When	Kind	Merged	Decayed	Pruned	Flagged	Compacted

Engine — the replaceable brain

The engine is never hard-wired: point Lucy at any OpenAI-compatible endpoint and key here. Blank endpoint = api.openai.com; the key can also come from env var OPENAI_API_KEY (env wins). Stored encrypted at rest.

Voice / style Extra system prompt (appended to every turn)

CRM connection — crm.intelgic.ai

Lucy pulls the dashboard digest and live context from these endpoints. The API key can also come from env var CRM_API_KEY.

CRM connector enabled

Persona charter — the single source of who Lucy is

This document is compiled into Lucy's brain on every reply and is the only authority on her identity, role, voice, and boundaries — she is explicitly forbidden from assuming any role, title, or trait not written here. Edit it like a living document: every save is a restorable version. Markdown; the section structure (Identity → NOT → Mission → Voice → Rules → People) is the recommended shape.

Conversation threads

Lucy's episodic memory — one thread per conversation plus the pooled sales-group thread. One person is one thread across every channel.

Thread	Kind	Messages	Last activity

Contacts — who Lucy knows

Built automatically as people talk to her. Every address that belongs to the same human maps onto one contact and one memory thread.

Name	Addresses	Thread	Since

Incidents — first ping to all-clear

Every failure that produced a user-facing apology is tracked here until it's fixed. Lucy re-pings the contacts below while an incident stays open, probes herself for recovery every few minutes, and sends the all-clear when she's thinking again. From WhatsApp you can reply status, resolved, or mute 2h.

#	What went wrong	Fix	Seen	Status

Error alerts — who gets texted when something breaks

The moment a reply fails, Lucy texts the owner plus everyone below — in plain English, with the exact fix — and keeps re-pinging until it's fixed, then sends the all-clear herself once she recovers. Recipients can reply status, resolved, or mute 2h right in the chat, or just ask follow-up questions like any conversation. Customers never see an error: they get a graceful note instead.

Alert the contacts below (the owner number is always alerted) Contacts

Name	WhatsApp number (E.164)

Self-healing & the database

Watchdog self-checks every 15 min and WhatsApps the owner number once per new failure (and once on recovery). Failed sends retry with backoff; dead letters wait below for a manual retry — nothing is silently lost. Daily backups are integrity-checked with a 14-day rotation; a corrupt database restores itself from the newest good snapshot on boot. Lucy's database is her own — separate from the CRM and everything else — and the next-generation memory store (see BRAIN-ROADMAP.md) plugs into this room.

To	Kind	Last error	Attempts