Shanepedia agent runtime

Shanepedia should be usable by Codex, Gemini, Ralph, and future local agents without relying on memory of where the wiki lives. The repo itself should expose search, grep, localhost browsing, lint, and parent-owned lane entrypoints.

The target pattern is an LLM-maintained wiki, not just a retrieval layer over raw files. Agents should treat the wiki as a compiled synthesis system that gets better over time.

First reads for a fresh agent

• START_HERE
• llm-wiki-pattern
• codex-obsidian-llm-wiki-loop
• obsidian-workflow

Canonical root

cd /Users/bestrobot/.openclaw/workspace/projects/shanepedia

Start from the parent repo first. Do not treat elsalkb as the wiki root.

Core agent commands

python3 scripts/wiki/query_wiki.py "future businesses travel"
python3 scripts/wiki/query_wiki.py "los cobanos whatsapp leads" --json
scripts/wiki/grep_wiki.sh shane
python3 scripts/wiki/ingest_source.py raw/sources/.../file.md --title "Title" --summary "Summary" --why "Why it matters"
python3 scripts/wiki/update_index.py
python3 scripts/wiki/lint_wiki.py
python3 scripts/wiki/build_site.py
./scripts/serve_localhost.sh open

Parent-owned lane commands

./scripts/run_elsalkb_autoresearch.sh
./scripts/run_elsalkb_ralph_fresh.sh 1
./scripts/start_elsalkb_lane_loops.sh
./scripts/run_shanepedia_cycle.sh

Runtime rule

• Parent wiki first.
• Child runtime second.
• Every worthwhile child-lane discovery should become a durable Shanepedia page, link, source summary, contact note, or project hypothesis.
• If the work is substantial, leave markdown behind rather than only answering in chat.