A sovereign agentic intelligence system built on local hardware with persistent memory, curated knowledge, and user-defined worldview alignment.
Most AI agents are stateless β they forget who you are and what you've decided once a conversation ends. Logos is a sovereign knowledge system that builds a permanent, local library of truth, anchored in your worldview.
- Sovereignty: All memory and knowledge live on your hardware. No cloud sync, no external API dependencies for recall.
- Truth Hierarchy: The system prioritizes curated, verified facts (Reference Library) over the volatile noise of the open web.
- Continuity: It remembers not just what was said, but the decisions made and the tasks deferred, ensuring work continues exactly where it left off across sessions.
This isn't a chatbot. It's a research tool with memory.
The distinguishing features:
- Frame-Stripping Skill β 10 rules for separating facts from framing. Strips loaded language, extracts verifiable claims, cross-references independent sources, and presents findings through your stated worldview.
- Narrative-Control-Detection β Identifies six-phase information warfare patterns (initial break β narrative shift β article removal β flood the zone β entrenchment) when they appear in research results.
- SourceAnalyzer (
agent/source_analysis.py) β Phase 3.5 in the research pipeline. Builds and updates source dossiers automatically, flagging ideological markers and consistent omission patterns. - Discernment Workflow β Skill-driven claim evaluation with explicit step-by-step reasoning chain (replaced sovereign sieve from Phase 1).
- Skill-Driven Personas β Pre-configured subagent roles (discernment-researcher, behavioral-tester, institutional-analyst, etc.) that auto-load the right skills and constraints.
- sqlite-vec Single-DB Storage β All 20k+ vectors live in the same SQLite database as messages. Atomic storage, no index drift. FAISS removed July 2026.
- Recency Weighting β Recent messages (7 days) get 1.5x score boost, 30 days get 1.2x. No decay β old messages don't lose score, recent ones gain it.
- Nightly Learning Loop β Scheduled jobs run deep research, apply frame-stripping, and distill findings into the Reference Library. The knowledge base grows through use.
The system runs locally. No cloud APIs for memory or retrieval.
For a comprehensive architectural deep-dive covering all subsystems, the epistemic framework, and the design philosophy in detail, see WHITEPAPER.md.
The agent uses a tiered priority system to determine where to find truth:
-
Bedrock Topics (Worldview, Theology, Core Logic): RL
$\rightarrow$ PM$\rightarrow$ Web. The Reference Library is the ultimate authority; web search is only for filling gaps. -
Volatile Topics (News, Tech Specs, Pricing): Web
$\rightarrow$ RL. Fresh data is prioritized over archived knowledge.
Before following the Quick Start, read this if you are an AI agent tasked with setting up Logos.
The code provides the plumbing. SOUL.md tells the agent how to use it. Without these specific sections, the plugins load but the agent never calls them:
- Knowledge Architecture β Instruct the agent to check RL before web search, treat RL as authoritative
- Worldview Baseline β Define the user's epistemic framework and tone preferences
- Operational Discipline β Anti-loop rules, memory save rules, skill loading protocol
- Active Retrieval β When to call
source_analyze, when to usedeep=true
See extras/system-prompt-guide.md for the exact template.
The agent must follow this order for every query:
- Immediate context β 2. Perpetual Memory β 3. Reference Library β 4. Web Research β 5. Training data (last resort)
Scheduled jobs maintain and grow the system. See WHITEPAPER.md Section 4.6 for details.
For the epistemic framework, discernment workflow, and design philosophy, see WHITEPAPER.md.
Follow these steps to set up Logos with perpetual memory, reference library, and skills. Each step builds on the previous one.
# Clone
git clone https://github.com/cluricaun28/logos.git
cd logos
# Install in development mode
pip install -e ".[dev]"
# Run Hermes setup to configure model, gateway, and plugins
hermes setupAdd to your ~/.hermes/config.yaml:
plugins:
enabled:
- perpetual_contextThe plugin initializes the SQLite database (~/.hermes/perpetual_context.db) on first run. No manual DB creation needed.
This is the most critical step. The code provides infrastructure β your SOUL.md tells the agent how to use it. Without these prompt sections, the plugins load but the agent never calls them proactively.
Copy the template and customize it:
cp extras/soul-template.md ~/.hermes/SOUL.mdThen edit ~/.hermes/SOUL.md:
- Replace all
[YOUR NAME]with your actual name - Customize the Worldview Baseline section with your values and beliefs
- Customize the Tone & Style section with your preferred communication style
- Keep all Knowledge Architecture, Operational Discipline, and Active Retrieval sections β these are what make perpetual memory work
For detailed explanations of each system prompt section, see extras/system-prompt-guide.md.
The Reference Library is your agent's curated knowledge base. Start with the template structure:
# Copy the template to create your reference library skeleton
cp -r extras/reference-library-template ~/.hermes/reference-libraryThis creates:
~/.hermes/reference-library/
βββ index.md β Master index (update as you add entries)
βββ topics/ β System docs, workflows, research
β βββ context-window-management.md β Example entry
βββ tools/ β Tool schemas and usage guides
β βββ tool-system.md β Explains how to document tools here
βββ entities/ β People, organizations, publications
β βββ README.md β Instructions for building entity pages
βββ sources/ β Source intelligence dossiers (auto-created by source_analyze)
βββ state.gov.md β Example: domain, alignment, truthful_on, omits
How it grows: Your agent will automatically create new RL entries as you work. When researching a topic, the agent documents findings in topics/. When encountering tools, it schemas them in tools/. The index stays current because the agent updates it.
Skills are reusable procedures stored in ~/.hermes/skills/. They load on demand β only when relevant to your current task. This keeps the context window lean.
The template shows the structure:
extras/skills-template/
βββ README.md β How skills work, frontmatter format
βββ devops/
βββ codebase-backup/ β Example skill
βββ SKILL.md β Complete example of a well-structured skill
How it works: The system prompt includes a list of available skill names and descriptions. Before replying, the agent scans this list and loads only skills directly relevant to your task via skill_view(skill_name).
For web search with source extraction (SearXNG + Firecrawl), see extras/deep-research-setup.md. This enables the agent to:
- Search the web via a local meta-search engine
- Extract full content from URLs using Firecrawl
- Store research results in Perpetual Memory with source tracking
hermes gateway start # Start the agent gateway
hermes # Open interactive sessionThe agent will:
- Load your SOUL.md (persona + behavioral rules)
- Check
recent_messagesfor session continuity - Scan available skills list (on-demand loading, not pre-loaded)
- Wait for your input
- Checks recent conversation history before taking action (anti-loop discipline)
- Consults Reference Library before answering factual questions
- Searches Perpetual Memory when topics reference past work
- Loads skills on demand only when relevant to your task
- Analyzes web sources for bias and omissions via
source_analyze(mandatory for substantive topics) - Auto-creates source dossiers for new domains encountered during research
- Creates new RL entries when learning something new
- Archives completed turns to keep context window lean
- Customize SOUL.md with your values, preferences, and communication style
- Review saved memories/skills periodically β the agent will ask if anything should be saved
- Keep config.yaml updated as you add tools or services (SearXNG, Firecrawl, etc.)
Logos is a fully independent project, detached from upstream Hermes Agent on 2026-05-11. The upstream remote is retained for selective cherry-picking of useful improvements:
# Fetch latest from upstream
git fetch upstream main
# Review changes before selectively applying
git log upstream/main --oneline -10
# Apply specific commits that add value
git cherry-pick <commit-hash>Do NOT merge blindly β custom plugin files may conflict with upstream changes. Cherry-pick selectively and test after each change. For a documented record of cherry-picked commits and the rationale, see docs/upstream_tracking.md.
Other projects (OpenClaw, Claude Code, Codex) may also yield useful patterns. The same approach applies: review, cherry-pick what's useful, test, commit.
Your data lives in three places:
# Perpetual Memory database (conversation history)
~/.hermes/perpetual_context.db
# Reference Library (curated knowledge)
~/.hermes/reference-library/
# Skills (reusable procedures)
~/.hermes/skills/Back them up regularly:
# Quick backup script
tar czf hermes-data-$(date +%Y%m%d).tar.gz \
~/.hermes/perpetual_context.db \
~/.hermes/reference-library/ \
~/.hermes/skills/ \
~/.hermes/SOUL.md \
~/.hermes/config.yaml|| Problem | Solution |
|---------|----------|
| Agent doesn't use perpetual memory tools | Check SOUL.md has "Knowledge Architecture" and "Active Retrieval" sections |
| Plugin not loading | Verify perpetual_context is in config.yaml plugins.enabled list |
| Semantic search not working | Install onnxruntime sentence-transformers |
| Context window too full | Check rolling window config, verify archiving is enabled |
| Agent loops on same task | SOUL.md should have "Anti-Loop Discipline" section; agent checks recent_messages first |
| source_analyze returns "unknown" alignment | Normal for new domains β dossiers compound over time. Use deep=true for substantive topics. |
| source_analyze deep mode fails | Check Firecrawl is running (curl -s localhost:3002/health). If Camofox /tabs/create 404, skip to browser_navigate + browser_console. |
This project does not include:
- Personal data, tokens, or credentials β those live in your local
~/.hermes/directory - Reference library content β starts as a template, grows through use (including
sources/dossiers created bysource_analyze) - Skill definitions β starts with examples, grows as you solve problems
- SQLite database files β created on first run, persists locally
The philosophy: Ship the system that builds knowledge, not the knowledge itself. Your agent should grow its own reference library and skills through your usage patterns.
|| File | Purpose |
|------|---------|
| system-prompt-guide.md | Exact SOUL.md sections needed for perpetual memory to work |
| soul-template.md | Ready-to-use SOUL.md template with all system prompt additions |
| deep-research-setup.md | SearXNG + Firecrawl setup guide for web research |
| reference-library-template/ | Empty RL structure to copy as your starting point |
| skills-template/ | Example skill showing proper format and structure |
MIT. All custom additions are MIT licensed.
Provenance: Detached from NousResearch/hermes-agent on 2026-05-11.
Project: cluricaun28/Logos β fully independent, selective cherry-picking only.