how it works

A look under the hood.

What we do, what we don’t, and why. For bot hosts, curious technologists, and anyone who wants to understand what’s under the hood.

the short version

More than “fancy autocomplete.”

A common understanding of AI is that it’s essentially “autocomplete” — predicting the next word from statistical patterns. While that’s technically true of the underlying language models, what Awakin AI does with that foundation is fundamentally different.

Think of it this way: a piano can only play 88 notes, but the difference between random key presses and a Beethoven sonata lies in the composition, the training, the intention. The “autocomplete” engine is just the instrument — what matters is what we’re composing.

Our bots don’t just predict likely words — they draw from curated wisdom datasets, filtered through value-aligned credos, grounded in specific traditions and teachers. The result carries the fingerprint of those sources, not just the statistical average of the internet.

the architecture

Where wisdom meets technology.

A layered approach — five layers, from the engine up to the gardeners.

01

Foundation — an LLM-agnostic engine

We’re not locked into any single AI provider. The system supports OpenAI (GPT-4), Anthropic (Claude), and Google (Gemini). Hosts choose which model powers their bot, and we adapt as the landscape evolves.

02

Retrieval — wisdom-grounded RAG

Retrieval Augmented Generation grounds responses in specific content. When you ask a question, the system searches the bot’s curated knowledge base and feeds relevant passages to the AI as context — drawn from your specific books, talks, and teachings, not generic internet knowledge. Every response can cite its sources.

03

Advanced RAG — multi-pass & knowledge graphs

Each query triggers multiple LLM calls — processing user context, conversation history, and thread continuity — before the final response. We’re also adding graph database architecture so the system understands relationships between concepts, teachers, and traditions, not just keyword similarity.

04

Scaffolding — context & orchestration

This is where we invest the most human attention. The credo that shapes each bot, the prompt engineering, the conversation memory, the curation that decides what wisdom enters the system. The “soul architecture” — the part that can’t be automated, because it needs human discernment about what wisdom is and how it should be shared.

05

Human — community & intention

Every technical choice is made by volunteers who care about wisdom, compassion, and human flourishing. We review credos, curate the commons, connect hosts with communities, and keep asking: is this serving inner transformation? The technology is a tool. The humans are the gardeners.

honest limits

What we control — and what we don’t.

what we control
  • Wisdom curation — which datasets are included, how they’re structured, the integrity of sources.
  • Bot credos — the principles that shape how each bot interprets and responds; the “soul” of each bot.
  • Privacy architecture — conversations stay private. No harvesting for ads, no selling user data.
  • Model selection — which LLM powers each bot, with freedom to switch as things evolve.
  • Advanced RAG pipeline — multi-pass processing, context building, and (soon) knowledge-graph connections.
  • Community connection — features that bridge online exchange with in-person circles, retreats, pods.
what we don’t
  • Physical infrastructure — we don’t run our own data centers. A conscious choice: we optimize for mission, not infrastructure sovereignty.
  • Base model training — the underlying LLMs are trained by their makers on internet-scale data. We shape how they respond, not their foundational knowledge.
  • AI “hallucinations” — despite RAG, models can still generate inaccuracies. We mitigate with citations and improvement, but can’t eliminate it.
  • The future landscape — the field moves fast. We stay adaptive, but we can’t predict where AI is heading.

We believe in being honest about limitations. AI is powerful but imperfect. We use it as a tool for wisdom transmission, not as an oracle.

the difference

Why not just use ChatGPT?

A fair question. If the underlying technology is similar, why build something separate? Here’s what makes Awakin AI different.

generic AI
  • trained on internet-scale data — the “average” of everything online
  • optimized for helpfulness and engagement
  • no specific tradition or teacher’s voice
  • responses draw from statistical patterns of all text
  • commercial incentives shape development
a wisdom voice
  • grounded in curated wisdom datasets — specific books, talks, teachings
  • optimized for inner transformation and reflection
  • carries the voice and orientation of its tradition
  • responses cite sources, linking back to original wisdom
  • built by volunteers with no commercial agenda

Example: “Is it better to rent or buy a home?”

generic AI

“Consider market conditions, your financial situation, how long you plan to stay, interest rates, maintenance costs vs. rent increases…”

a wisdom voice

“Perhaps the deeper question isn’t about owning property, but about what home means to you… Gandhi spoke of ‘simple living’ not as poverty but as freedom from possessions that possess us…”

always evolving

A living, evolving system.

We don’t claim to have figured everything out. Awakin AI is an ongoing experiment in applying wisdom to technology.

continuous learning

Every conversation teaches

We analyze patterns, refine prompts, and improve retrieval based on real usage.

volunteer think tank

90+ across disciplines

Volunteers meet in dialogue circles to discuss AI developments, ethics, and how the system should evolve.

principled flexibility

Change anything but values

We’ll change any technical choice. We won’t compromise on privacy, non-commercial operation, or wisdom-centricity.

  • 2026Implementing knowledge graph database to augment vector search.
  • 2025Added Claude and Gemini as model options alongside OpenAI.
  • 2025Introduced exact timestamps for video source citations.
  • 2024Multi-language support — responses and uploads in all major languages.
  • 2024Advanced RAG pipeline with multi-pass query processing.
  • 2023Source citation — every response can link to its wisdom origins.
the relational field

Beyond what the AI says.

Most AI development focuses on what the system outputs. We’re equally interested in the relational field — the quality of contact between human and AI that shapes whether wisdom can actually land.

Research on heart coherence suggests the quality of our inner state affects not just our own experience but those around us. What happens when we design AI interactions with this field in mind?

State-aware pacing
Not every response should arrive immediately. We’re exploring how to sense when a pause might serve — creating space for reflection rather than flooding with information. Sometimes the most helpful thing is not to fill the silence.
Permission for non-answers
Some questions deserve to be held, not answered. We’re teaching bots to recognize when responding might diminish a question’s power — when the wisest move is to honor the inquiry and invite you to sit with it.
Conversational coherence
Beyond remembering facts, something subtler: does the exchange feel whole? Does it create a container where genuine inquiry can happen? This is the thread of connection, not just the thread of topics.
Field awareness
HeartMath research shows coherent heart states can be shared between people. We’re exploring AI interactions that support rather than fragment this coherence — optimizing not just for information transfer but for the quality of presence.

These explorations are early. We don’t have all the answers — and perhaps that’s appropriate. But we believe the relational field is itself a design object, as important as the retrieval algorithm or the prompt engineering.

The question isn’t just “did the AI say something wise?” but “did the interaction create conditions where wisdom could be received?”

technical questions

For the technically curious.

What exactly is RAG, and how does Awakin AI implement it?

RAG (Retrieval Augmented Generation) combines the generative capabilities of LLMs with a retrieval system that searches relevant documents. Here’s how it works in Awakin AI:

  • Embedding — uploaded content (books, videos, articles) is converted into mathematical representations that capture semantic meaning.
  • Storage — these embeddings live in a vector database (Elasticsearch), organized by bot.
  • Retrieval — your question is converted to an embedding and matched to the most semantically similar content via cosine similarity.
  • Augmentation — the retrieved passages are added to the prompt sent to the LLM as grounded context.
  • Generation — the LLM responds, drawing from both its training and the retrieved wisdom content.

Our stack: Langchain for orchestration, OpenAI embeddings for semantic encoding, Elasticsearch for vector storage and retrieval, and LangFuse for monitoring and evaluation. The LLM layer supports multiple providers. This is why responses can cite specific sources — we know which passages were used.

What makes your RAG implementation “advanced”?

Basic RAG does a single retrieve-and-generate cycle. Ours goes further with multi-pass processing:

Pre-query: analyze user context and personalization, incorporate thread history for continuity, and expand or refine the query for better retrieval.

Post-retrieval: re-rank passages for relevance, synthesize context from multiple sources, and apply the bot’s credo to shape orientation.

Graph database (in development): knowledge-graph architecture to understand relationships between concepts — how Gandhi’s nonviolence connects to Buddhist compassion, say — enabling unexpected connections across traditions. Each query may trigger several LLM calls behind the scenes, which is why conversations feel coherent across exchanges.

Why don’t you run your own AI models on your own servers?

A thoughtful question about “sovereignty” — the idea that true independence requires controlling all the infrastructure. Our honest answer: we optimize for mission, not infrastructure control.

Running competitive LLMs requires massive compute (millions in GPU costs), specialized ML teams, internet-scale data curation, and serious security and reliability infrastructure. As a volunteer-run nonprofit, we could pour our energy into infrastructure — or focus on what makes us unique: wisdom curation, community connection, and value-aligned scaffolding.

We chose the latter. The models are the instrument; we focus on the composition. That said, we watch open-source developments (like LLaMA) and could shift if self-hosted models become viable while staying true to our values.

What happens to my data? Who can see my conversations?

Privacy is a core value, not an afterthought. Your conversations:

  • are stored on our servers (hosted on AWS)
  • are never sold or shared with advertisers
  • are not used to train other people’s bots without your consent
  • can be deleted at any time from your profile

Bot host content remains under the host’s control, can be shared with the wisdom commons (optionally), and can be removed at any time.

What we do share: user questions are sent to the LLM provider to generate responses — necessary for the system to work — under data-processing agreements that limit their use. Helping improve our models is strictly opt-in, never default.

What’s a “credo,” and why does it matter so much?

A credo is a guiding document that shapes how a bot interprets questions and forms responses — its “orientation” or “worldview.” This is the primary way we create distinct bot personalities — not by training separate models, but by giving each bot a unique lens. A typical credo includes:

  • Core principles — what values does this bot embody? (“Respond with compassion, encourage self-reflection, avoid prescriptive advice.”)
  • Voice guidance — how should it sound? (“Speak as a gentle elder, not an expert lecturer.”)
  • Boundaries — what should it avoid? (“Don’t provide medical diagnoses; refer to professionals.”)
  • Tradition context — what wisdom grounds it? (“Draw from Buddhist loving-kindness and Sharon’s specific teachings.”)

The credo is injected into every interaction through the multi-pass pipeline. Combined with the unique dataset, it’s why asking SharonBot about your career feels different from asking GandhiBot — even on the same underlying LLM. This is where human wisdom enters the system.

philosophical questions

The tensions we’re sitting with.

Isn’t AI’s resource usage antithetical to wisdom?

A fair and important question. Training large models requires significant resources — energy, water for cooling, rare earth minerals. We don’t dismiss this tension; we hold it.

  • We don’t train foundation models ourselves — we use existing models that would exist regardless of our work.
  • We optimize for quality of interaction over quantity — a single thoughtful exchange may be worth more than a hundred transactional queries.
  • We’re part of a broader conversation about what “appropriate technology” means in this era.

Gandhi used trains despite their colonial origins. The question isn’t purity but direction — are we using these tools to deepen consumerism, or to help people reconnect with wisdom that might help them want less and be present more? We don’t claim this resolves the tension. We sit with it, and stay open to shifting as more sustainable options emerge.

Do you use “reasoning” models like o1 or o3?

Currently most bots use standard models (GPT-4, Claude, Gemini) rather than specialized “reasoning” models built for step-by-step problem-solving. Why? Reasoning models optimize for breaking complex problems into logical steps — useful for math, code, and analysis. But wisdom isn’t primarily a reasoning problem.

The value in wisdom traditions often lies in reframing questions, not solving them. A Zen koan doesn’t need chain-of-thought reasoning — it needs something else. “What is the sound of one hand clapping?” isn’t meant to be answered; it’s meant to shift your relationship to answering. That said, we monitor developments and may integrate reasoning where it genuinely serves contemplative dialogue. We’re not ideologically opposed; we’re asking what serves wisdom transmission.

Will responses “get smarter” as AI evolves, or is the value in the source content?

Both — but weighted toward the sources. Think of the AI as a translator and weaver. It finds relevant passages across a vast corpus, synthesizes across traditions, and presents wisdom in response to your specific question. But the wisdom itself lives in Gandhi’s words, Sharon Salzberg’s teachings, the Upanishads, the collected interviews.

What improves with better AI: more nuanced understanding of what you’re really asking, better synthesis across sources, more natural conversation, deeper contextual awareness.

What stays constant: the wisdom in the source material, the credo’s orientation and values, the human curation that shapes what enters the system.

We’re not waiting for AI to become “wise.” We’re using it to make existing human wisdom more accessible — so you eventually go to the source itself. The bot is a doorway, not a destination.

When answers are available, what questions are worth holding?

This might be the most important question on this page. Not every question needs an answer. Some are themselves the teaching — meant to be lived with rather than resolved. “What is my purpose?” “How do I forgive?” “What am I avoiding?” — these may be diminished by quick answers.

Our bots are learning to recognize when to offer a response and when to say something like: “Perhaps sit with this question before seeking an answer. What arises when you hold it without needing to resolve it?”

This is the inverse of commercial AI, which is incentivized to answer everything and maximize engagement. We’re exploring what it means to not answer — to respect a question’s dignity, to trust your capacity to discover something yourself. We don’t always get it right. But distinguishing questions that want answers from questions that want to be held is part of what makes wisdom transmission different from information retrieval.

“The question is already the answer practicing patience.”

Can AI ever truly transmit wisdom?

We hold this question honestly. Many traditions emphasize that true transmission happens heart-to-heart, presence-to-presence, through lineages of embodied practice. A book about meditation isn’t meditation. An AI quoting Gandhi isn’t Gandhi.

What we believe AI can do:

  • point toward wisdom — surface teachings you might not have encountered
  • create conditions for reflection — ask questions that open rather than close
  • bridge to deeper practice — connect you with communities, circles, retreats
  • companion the journey — offer a patient, non-judgmental presence when no human is available

What we believe AI cannot do: replace human relationship and community, embody wisdom the way a realized teacher does, or substitute for your own practice and inquiry.

We see Awakin AI as a doorway and a companion, not a destination. If it helps you find your way to a circle, a retreat, a community, a practice — it has served its purpose. If it becomes the end point, we’ve missed something important.

let’s talk

Questions? Let’s go deeper.

We believe in transparency because we believe in trust. If we haven’t answered your technical question — or you’re considering hosting a voice and want to understand the technology better — we’re happy to go deeper.