Shane founder operating principles

Shane's best work appears when things are simple, fast, direct, and real. The parent wiki should model those principles explicitly so future agents do not drift toward bloated plans, generic products, or overbuilt software.

Core principles

• Fast boot wins: the first useful version should load quickly, explain itself quickly, and get to a real outcome quickly.
• High-signal over comprehensive: a smaller set of sharp options is more valuable than a large list of weak possibilities.
• Operator empathy beats abstraction: tools, sites, and automations should help a real person make money, save time, or reduce friction.
• Public proof matters: pages, offers, and products should leave behind visible evidence, not just internal notes.
• Reusable context compounds: every trip, contact, business idea, and design observation should become future leverage inside Shanepedia.
• Low-friction communication first: WhatsApp, clear copy, mobile usability, and obvious next steps beat complex funnels.

Agent implication

When agents propose new work, they should prefer:

• smaller shippable offers over platform fantasies
• concrete operator improvements over vague strategy
• pages that clarify Shane's taste, leverage, and decision style
• products that can become self-sustaining with recurring research and light maintenance
• offers matched to a real archetype from founder-archetypes-and-needs rather than a vague "everyone" market