Shanepedia research flywheel

Shanepedia should become a daily operating loop for founder research, networking, travel prep, business ideation, and project spawning. A good run does not just gather facts. It leaves the parent wiki easier to search, easier to browse, and more useful for launching the next business lane.

Daily loop

1. Pull new evidence from active lanes, source pages, Telegram photo batches, and local operator websites.
2. Run child-lane autoresearch goals such as db_coverage and query_access.
3. Run child-lane Codex and Gemini loops for curation and discovery.
4. Convert the best findings into parent wiki updates, links, contact trails, and project hypotheses.
5. Rebuild the parent index, lint the graph, and keep localhost browsing healthy.

Current migrated entrypoints

• Parent-owned autoresearch: ./scripts/run_elsalkb_autoresearch.sh
• Parent-owned Ralph wrapper: ./scripts/run_elsalkb_ralph_fresh.sh 1
• Local browse surface: ./scripts/serve_localhost.sh open

Quality bar

• Evidence should point to a source page or raw source.
• Business ideas should name the lane they belong to.
• Travel/operator insights should teach a reusable founder lesson.
• Child automation should improve the parent wiki, not only a lane-local database.