ops
Shanepedia roadmap
Shanepedia should become a crawlable founder/operator wiki, not a project-local notebook. The current first pass is enough to ground agents in Shane's public voice, this trip's core preferences, and a few high-signal El Salvador entities, but those should now be treated as one lane in a broader system.
Highest-leverage next ingests
Current status: active planning
Next action: expand the founder, relationship, and portfolio layers without overfitting to one travel lane
- Public Shane corpus: blog posts, more public repo descriptions, business pages, and writing samples that sharpen voice and priorities.
- Project portfolio layer: current and future ventures, sites, offers, experiments, and why each exists.
- Relationship layer: hosts, guides, founders, collaborators, and repeat-worthy contacts with context on trust and future value.
- After-action layers: what actually happened on trips or projects, what delivered, what felt magical, and what was wasted motion.
- Inspiration layer: places, images, products, interfaces, and aesthetics that should inform future design, writing, or business work.
- Business-design layer: buyer archetypes, product lanes, and UX rules that agents can use when creating or improving businesses.
Operating rule
Every new source should answer one of two questions:
- does this help an agent understand Shane better?
- does this help an agent make better future decisions for Shane?
If the answer is neither, it probably does not belong in Shanepedia.
Scope correction
ElSalKB, Los Cobanos work, and future operator sites are examples of Shanepedia project lanes. They should not become the container for the whole wiki.