eling 0.2.2

Unified second brain for AI agents — 5-tier memory, HRR reasoning, 10 MCP tools, conditional verify-on-stop

🧠 Eling

Unified second brain for AI agents — 5-tier memory, HRR reasoning, 10 MCP tools, conditional verify-on-stop

"Eling" (Javanese): to remember, to be conscious, to be aware

---

✨ What is Eling?

Eling is a unified second brain for AI agents. It merges 5 memory tiers into one MCP server — no external databases, no cloud services needed for local operation.

🧠 Tier 5: NOTION   — online brain, human-readable (optional)
📚 Tier 4: KB       — FTS5 knowledge corpus
🕸️ Tier 3: CODE     — codegraph symbol intelligence
💎 Tier 2: FACTS    — SQLite + HRR + BM25 hybrid with trust scoring
📌 Tier 1: BUILTIN   — Hermes MEMORY.md / USER.md

All accessible via 9 MCP tools from a single stdio server:

Tool	Purpose
eling_remember	Store content — auto-routes to facts (short) or KB (long)
eling_recall	Cross-layer search with RRF fusion (BM25 + trigram + porter)
eling_reason	Compositional query tying multiple entities together
eling_probe	Get all facts about an entity
eling_reflect	Promote a high-trust fact to Notion as a permanent page
eling_sync	Bidirectional sync between memory layers
eling_stats	Show per-layer statistics
eling_think	Synthesis + gap analysis across layers
eling_export	Full brain export as JSON or Markdown
eling_verify	Query/record verification status (conditional)

🚀 Quick Start

pip install eling

# Run MCP server (stdio — plug into any MCP host)
python3 -m eling.mcp_server

# Or use the CLI
python3 -m eling --help

🔌 Hermes Integration

Eling plugs into Hermes Agent at 3 levels:

1. MCP Server — add to ~/.hermes/config.yaml:

mcp_servers:
  eling:
    command: python3
    args: ["-m", "eling.mcp_server"]
    enabled: true

2. Memory Provider — sets default brain for remember/recall:

memory:
  provider: eling

3. Plugin — registers eling_remember + eling_recall as quick tools:

plugins:
  enabled:
    - eling
  eling:
    home: /root/.eling

📋 CLI Commands

python3 -m eling remember   "I learned that..."
python3 -m eling recall     "what did I learn about X"
python3 -m eling probe      "X"
python3 -m eling reason     ["X", "Y"]
python3 -m eling reflect    1                 # promote fact_id 1 to Notion
python3 -m eling stats
python3 -m eling export     --format markdown
python3 -m eling sync       --direction push   # facts → Notion

🌐 Notion Setup (Tier 5)

Optional — skip this if you only need local memory.

1. Create a Notion integration at https://www.notion.so/my-integrations

   • Give it a name (e.g. "Eling Brain")
   • Copy the Internal Integration Secret (starts with ntn_)

2. Share a parent page with your integration

   • Open the page you want as your second brain root
   • Click Share → Invite → select your integration
   • Copy the page URL and extract the page ID (the UUID in the URL, e.g. 38f7b66e-c7e0-813f-85b0-d37cef59c1f7)

3. Set environment variables:

export NOTION_API_KEY="ntn_..."
export NOTION_PARENT_PAGE_ID="38f7b66e-c7e0-813f-85b0-d37cef59c1f7"

Note-taking behavior

Once configured, eling auto-creates a 📋 Task Logs child page under your parent on first use:

📋 Hermes Vault (parent page — your configured root)
  ├── 📋 Task Logs        ← auto-created by eling
  │   ├── 💡 Eling test ← child pages from eling_reflect / remember(layer="notion")
  │   └── 💡 Another note
  ├── 🔑 API Keys...
  └── ...

Two ways to add notes to Notion:

Method	Usage	Route
brain.reflect(fact_id) / eling_reflect	Promote a high-trust fact to Notion	→ auto-routes by category
brain.remember("text", layer="notion") / eling_remember with layer=notion	Store content directly as a Notion page	→ auto-routes by category

Auto-routing by category

Content is automatically detected and routed to the right child page:

Category	Triggers	Child page
project_summary	"project done/complete/selesai", "deploy success", "summary completion"	🎯 Project Summaries
credential	"api_key", "password", "secret", "token", "credential"	🔑 Credentials
address	"alamat", "address", "domicile", "tinggal di"	📍 Addresses
config	"config", "setup", "setting", "environment"	⚙️ Configurations
(uncategorised)	Everything else	📋 Task Logs

Example:

# Auto-routes to 🎯 Project Summaries
b.remember("Project done, deployed to production", layer="notion")
# Auto-routes to 🔑 Credentials
b.remember("DATABASE_URL = postgres://...", layer="notion")
# Auto-routes to 📋 Task Logs (no pattern match)
b.remember("General note", layer="notion")

All child pages under these category pages are full Notion pages — you can edit, move, share, or reference them normally.

Or pass them explicitly in code:

from eling.brain import Brain
b = Brain(
    notion_api_key="ntn_...",
    notion_parent_id="38f7b66e-..."
)
result = b.reflect(fact_id=1)
print(result)  # {"page_id": "...", "promoted": True}

# Or store directly as a note
result = b.remember("Quick note for Notion", layer="notion")
print(result)  # {"layer": "notion", "page_id": "...", ...}

Note: eling_reflect and remember(layer="notion") check availability at call time and return a clear error if any config is missing — no silent failures.

🛡️ Verify-on-Stop (Conditional)

Eling provides verify-on-stop nudges for AI agents that lack built-in verification (e.g., OpenCode, OpenClaw, Cursor, Windsurf). When running under Hermes, this feature automatically skips — because Hermes already has its own agent/verification_stop.py.

How it works

1. Auto-detection — Eling detects the host agent from environment variables (HERMES_SESSION_SOURCE → Hermes, OPENCODE_HOME → OpenCode, etc.)
2. File edit tracking — When code files are edited via hooks or MCP tools, eling records them in a verification ledger
3. Verification nudge — If code was edited but no passing tests/verification was recorded, eling produces a [System: ...] nudge message
4. Recording — Agents can call eling_verify MCP tool to record verification results (passed, failed, skipped)

Usage via MCP

// Query current status
{ "method": "tools/call", "params": { "name": "eling_verify", "arguments": {} } }

// Record a passing verification
{ "method": "tools/call", "params": {
    "name": "eling_verify",
    "arguments": { "status": "passed", "command": "pytest", "output": "364 passed" }
} }

Config

Key	Default	Env	Description
verify_on_stop	true	ELING_VERIFY_ON_STOP	Enable nudges for non-Hermes agents
verify_on_stop_max_attempts	2	ELING_VERIFY_MAX_ATTEMPTS	Max nudges per session
adapter	hermes	ELING_ADAPTER	Force adapter type

plugins:
  eling:
    adapter: auto       # auto-detect from env
    verify_on_stop: true

🏗️ Architecture

eling/
├── mcp_server.py     — JSON-RPC stdio server (9 tools)
├── brain.py          — Orchestrator: routing + RRF fusion + sync
├── config.py         — Layered config: env → json → defaults
├── hooks.py          — 15 lifecycle hooks + HookRegistry
├── privacy.py        — PII/secret stripping (19 patterns)
├── compress.py       — SHA-256 dedup + length compression
├── cli.py            — CLI client for all 9 operations
└── layers/
    ├── builtin.py    — Tier 1: Hermes MEMORY.md / USER.md loader
    ├── facts.py      — Tier 2: SQLite + HRR + BM25 + trust scoring
    ├── hrr.py        — Holographic Reduced Representations (optional numpy)
    ├── code.py       — Tier 3: CodeLayer wrapper
    ├── code_index.py — Pure-Python AST+regex code indexer
    ├── kb.py         — Tier 4: FTS5 + porter + trigram + RRF
    └── notion.py     — Tier 5: httpx Notion API client (lazy import)

⚡ Performance

• Lazy imports — numpy and httpx are imported only when their layer is first used, not at module load time
• import eling takes ~1.3s (was ~4.5s with module-level imports on Alpine)
• Pure-Python fallback when numpy unavailable (BM25-only retrieval still works)

📖 Documentation

• Architecture
• API Reference
• Migration Guide
• Hooks Reference

🤝 Credits

• HRR phase encoding + facts layer — adapted from holographic plugin by dusterbloom (Hermes PR #2351, MIT)

📜 License

MIT © 2026 PatrickNoFilter