Home / Product / Features and Vision

The Personal Knowledge Base and Bespoke Audio Companion (the Golden Tier)

Updated Jun 20, 2026 · Affirmology_PersonalKnowledgeBase_GoldenTier_Concept_v1.md

The Personal Knowledge Base and Bespoke Audio Companion (the Golden Tier)

Jeff's vision, 2026-06-20: "Beyond the Structures we need a customized knowledge base, person-specific chatbot audio creation. That's what the golden tiers will use, and what people ultimately want. Credits to buy things like that. We need it now, for me and Sol, and it must not lose context, conversation, history, and truly help us on our path."

This is the top of the product, the difference between a template and a relationship. Structures are the same shape filled by any chart. The Golden Tier is a companion that KNOWS a specific person deeply and growing over time, and creates bespoke audios from that accumulated understanding. This doc captures the vision and specs the buildable CORE you need now: a persistent per-person knowledge base that never forgets.

Why this is the real product

• Structures scale reach. The Personal Knowledge Base creates depth and loyalty, and it is what a high tier is worth paying for.
• It is what people ultimately want: not a generic reading, but something that remembers who they are, what they are working through, and where they are going, and meets them there every time.
• It is the natural home for credits: bespoke creations (a custom audio, a deep reading, a new suite) are the premium units a member spends credits on.
• And it directly fixes the pain we hit today: the standing wealth context, the conversation, the history kept getting lost on restarts and chat clears. A companion on your path cannot forget your path.

The buildable CORE (needed now, for Jeff and Sol): the Personal Knowledge Base

A durable, server-side, per-person store that holds standing context and is ALWAYS available, independent of chat history. This is the foundation everything else sits on.

1. STORE: a knowledge_base table (in studio.db, mirrored to R2 for durability), keyed by person_id. Each entry: id, person_id, title, content, kind (standing_context | reading | goal | note | suite), pinned (bool), created_at, updated_at.
2. ALWAYS-INJECTED: on EVERY Hermes turn, load the person's PINNED knowledge-base entries into the system context, separate from and in addition to the chat history. So clearing the chat or restarting the server never loses the standing context. (This is the durability fix for today's pain.)
3. ADD / EDIT: a way to put things in, both a Hermes tool (save_to_knowledge_base {title, content, kind, pinned}, fired when the user says "remember this / keep this as my standing context") and a simple UI panel. The standing WEALTH CONTEXT Jeff pasted becomes the FIRST pinned entry for Jeff and for Sol immediately.
4. FEEDS AUDIO CREATION: when Casting or rendering, the relevant knowledge-base entries are part of the brief (ties directly to C24, the audio must use the brief), so audios are bespoke to the accumulated understanding, not just the bare chart.
5. PERSISTENT BY DESIGN: durable across restarts, deploys, and chat clears. Mirror to R2 so it survives a server rebuild. This is the opposite of the volatile chat history that has been failing.

How it relates to what exists

• It is the foundation of the LIVING PROFILE (C20): the Living Profile's lens traits and assessment data live in (or beside) this same per-person store. Start with the knowledge base; grow it into the full profile.
• It depends on C24 (the Cast must use the brief) so the knowledge base actually shapes the audio.
• It is the durable answer to the history-loss problem: standing context lives here, not in the fragile chat window.

The Golden Tier and credits (capture, design next)

• TIERS: the Personal Knowledge Base + bespoke creation is a premium/golden tier. Lower tiers get Structures; the golden tier gets the companion that remembers and creates bespoke.
• CREDITS: bespoke creations (custom audios, deep readings, new suites) are metered in credits the member buys. The hard per-user caps and the cost discipline from the audio cost memo apply. Design the credit model when we build the tier, but architect the knowledge base now so it is ready.

Build order

• NOW: the Personal Knowledge Base core (store + always-inject + add + feed-audio + R2 durability), and seed Jeff's and Sol's first pinned entry with the standing wealth context so nothing is ever lost again.
• NEXT: wire it into Cast (C24) so audios draw on it; add the UI panel to view/edit.
• THEN: grow it toward the full Living Profile (lens traits + assessment), and design the golden-tier credit model.

Net

The Structures are the catalog. The Personal Knowledge Base is the relationship. Build the persistent per-person store now, both because it is the foundation of the highest-value tier, and because it is the only real fix for the context-loss that has been costing us all day.