Diana Snodgrass — Institutional Knowledge Transfer & AI Second Brain

Analysis prepared by Michelle  |  April 8, 2026  |  Confidential — CAA Internal
The Short Version: This is absolutely doable, and it's exactly the right time to start. Diana's knowledge falls into two buckets: the stuff that can be captured (processes, rules, precedents, vendor contacts, decision logic) and the stuff that can't (judgment calls built from 20 years of reading a room, relationships, and institutional intuition). A well-designed second brain can handle 70–80% of what Diana does day-to-day. The other 20% is why you keep her part-time in 2027.

1. What CAN Be Captured vs. What Can't

Good candidates for capture

Hard to capture

Bottom line: processes, rules, and reference material transfer well. Wisdom and instinct don't fully transfer anywhere — that's what part-time coverage in 2027 is for.

2. How Knowledge Capture Works — Self-Directed Sessions

Rather than structured facilitator-led meetings, Diana works through prepared prompt questions on her own schedule. The goal is roughly three hours per week — but that doesn't need to be three continuous hours. It can be 15 minutes in the morning, an hour at lunch, a half-hour at the end of the day. The work is cumulative.

How it works in practice: Each domain comes with a prepared set of prompt questions. Diana answers them in whatever format is most natural to her — typed notes, voice memo, even a quick email. The answers get captured, organized, and eventually loaded into the knowledge base. Her job is to answer. Someone else's job is to organize and maintain what she produces.

Recommended domains

What each domain's prompt set covers

  1. Process flows — "Walk me through step by step what happens when…"
  2. Decision logic — "When you see X, how do you decide between Y and Z?"
  3. Reference material — vendors, contacts, account numbers, portal access
  4. Context and history — "Why do we do it this way? When did that change? What happened that time we got this wrong?"
  5. Edge cases and exceptions — "What are the situations that don't follow the normal process?"

Prompt questions are released one domain at a time — not all at once. Starting with the highest-risk domains (legal and compliance first, not the easiest ones) ensures that if the timeline compresses, the most important material is already captured.

3. The Avatar Concept

A static document library is useful. An AI agent that answers questions the way Diana would is transformative.

The goal is to build a Diana Second Brain Avatar — an AI agent loaded with everything captured through the prompt sessions. CAA staff who relied on Diana for guidance could ask the avatar directly: "What do I do when an employee requests FMLA for a mental health reason?" or "Who do I call if we have a workers' comp situation in Georgia?" and get answers grounded in Diana's actual knowledge and CAA's actual practices.

Why this beats a knowledge base: Nobody searches a knowledge base when they're in the middle of a situation. They ask a person. The avatar preserves that interaction model — it feels like consulting Diana, not searching a filing cabinet. That's the difference between a system people actually use and one that goes stale after six months.

What the avatar can do

What it won't replace

Architecture

The avatar runs on a RAG (retrieval-augmented generation) architecture — the same proven approach used for Professor Cody (building codes AI). Diana's captured knowledge lives in a vector database; the avatar retrieves relevant material and uses it to answer questions accurately rather than hallucinating. New material added over time automatically improves the avatar's responses.

Note: Naming the avatar "Diana" — or any variant using her name — should be confirmed with Diana directly before deployment. Most people feel honored by the idea of their knowledge living on this way, but it's worth a conversation first.

4. Ownership and Maintenance

The knowledge base needs a keeper — someone who reviews what Diana produces, organizes it, keeps it current as things change, and decides what goes into the avatar. Laws change, plans renew, policies evolve. A knowledge base that doesn't get maintained becomes unreliable fast.

Initially, Rusty serves as the keeper: reviewing captured material, making judgment calls about what belongs in the system, and maintaining quality control. Over time, as the system matures, that role can be delegated or distributed. But having clear ownership from day one is what separates a functioning system from an abandoned one.

5. Technology Options

OptionDescriptionBest ForComplexity
A — Doc Library + AI ChatOrganized folders + Notion AI, M365 Copilot, or custom GPT with uploaded docsStarting point; low cost; no codingLow
B — Custom RAG (recommended)Vector DB (ChromaDB) + Claude/GPT-4 retrieval layer — same architecture as Professor CodyMore control, better accuracy, supports the avatar concept fullyMedium
C — Searchable WikiNotion, Confluence, SharePoint — no AI layerFast to build; no AI value until laterLow
Recommendation: Target Option B from the start — the avatar concept requires it, and CAA already has the infrastructure (ChromaDB, OpenClaw agents). Start building the document library now and stand up the RAG layer once enough content exists to make it useful. Don't let technology selection slow down the knowledge capture work — the two happen in parallel.

6. Realistic Limitations

The avatar will handle well

It will struggle with

7. Recommended Phased Approach

Phase 1 Inventory & First Domain — April–June 2026
Map all of Diana's domains. Prioritize by risk. Release first prompt set (legal/compliance). Diana begins answering on her own schedule. Rusty reviews and organizes responses.

Phase 2 Deep Capture — July–October 2026
Release prompt sets domain by domain. Diana works through them at ~3 hrs/week. New questions added as gaps surface. Avatar architecture stands up once enough content exists.

Phase 3 Build & Test the Avatar — October–November 2026
Load captured knowledge into the RAG system. Test with real questions from staff. Gap-fill based on what it can't answer. Refine with Diana before she transitions.

Phase 4 Handoff & Validation — December 2026
Diana reviews the full system. Final gaps addressed. Avatar goes live for CAA staff. Diana moves to part-time, available for complex calls the avatar can't handle.

Phase 5 Part-Time Overlay — 2027
Diana available for judgment calls. Avatar handles routine. Her hours used to update and refine based on what's actually being asked.

8. Timeline Reality Check

Nine months (April through December) is workable but not comfortable. Realistically:

Where it goes wrong

Where you can accelerate

Next step: Release the first domain prompt set — Legal & Compliance — and let Diana begin. Everything else follows from there.

Charles Abbott Associates  |  Prepared by Michelle, April 8, 2026  |  Confidential