Shanepedia founder portfolio system

Shanepedia is the parent operating system for Shane's life and business context. ElSalKB is one active lane inside that system. Local operator work such as los-cobanos.com is another lane. Future businesses should be added the same way: as linked child projects, not as replacements for the whole map.

Canonical model

1. Shane is the root entity.
2. Projects, businesses, trips, and operator relationships are child lanes.
3. Sources should be written once, then linked to whichever projects they inform.
4. Every project page should answer both:

• what local thing is happening?
• what reusable founder pattern does this teach?

Current active lanes

• ElSalKB: place, operator, travel, and business-intelligence lane for El Salvador.
• Operator site help: audits, funnel ideas, copy fixes, and WhatsApp/Bitcoin onboarding for businesses like Los Cobanos Tours.
• Founder identity and voice: Shane's public site, product taste, decision style, and working preferences.
• Future venture creation: business ideas, relationship follow-ups, and new micro-projects that can graduate into standalone efforts.

Daily operating loop

• Research: pull in new sources, site pages, screenshots, and Telegram media.
• Synthesis: update source summaries, entity pages, topic pages, and parent ops pages.
• Opportunity extraction: produce business ideas, partner leads, outreach drafts, or new project candidates.
• Execution: ship a page, message, offer outline, contact record, or micro-improvement for a real operator.

Recommended automation cadence

Shanepedia is now the top-level workspace. The current El Salvador lane still has its own child runtime, but the parent repo should own the orchestration entrypoints.

# parent cycle: maintain parent wiki + run current child lane
./scripts/run_shanepedia_cycle.sh

# parent-owned autoresearch for the current ElSalKB lane
./scripts/run_elsalkb_autoresearch.sh

# background launch for the current ElSalKB lane
./scripts/start_elsalkb_lane_loops.sh

# parent wiki maintenance only
python3 scripts/wiki/update_index.py
python3 scripts/wiki/lint_wiki.py

The child ElSalKB repo still owns its own trip database, autoresearcher, and Ralph configs for now. Those should be treated as lane-local runtimes under the parent Shanepedia control surface until more lanes exist.

Output rule

Every automated run should end in at least one durable Shanepedia improvement:

• a new or improved wiki page
• a new relationship/contact insight
• a new business or project hypothesis
• a tighter ranking, alias, or route path for future agent use