Skip to main content

gary and ron: birthing industries & strategic architecture

2026-03-26

full conversation covering industry creation, competitive positioning, the gradient of context framework, puppeteering, and tactical opportunities.

part 1: birthing industries​

  • we're birthing industries, not building companies. the world economy is composed of industries that reflect the power structures and technologies of each age. we're building the infrastructure (game engine) that enables new industries to exist.

  • new roles, not just founder wealth. if a Pegasus only makes the founders rich, we failed. real Pegasus companies create new types of roles for thousands of people. the vinyl collector, the AI education specialist, the community architect. those roles only exist because someone built the industry first.

  • the sequence. build infrastructure, incubate industry, create roles, educate people into them (AAS), activate them onto the elevator.

  • the old incubator model can't adapt. they have relationships with the right schools but the wrong framework. capital but not calling. right concept, wrong execution. they take builders and try to make founders. we start with people called to reinvent their domain.

  • applied AI practitioners are the moat. not "builders" in the generic sense. the pipeline of practitioners who can implement within new industries. AAS builds the bench, Imagos puts people in the game.

  • the App Store analogy (internal only). the App Store enabled Snapchat, Instagram, Pinterest to exist as entire new industries. we're building the imagination economy equivalent. don't use this analogy externally because people hear "apps" and miss the point.

  • why we win. God + Pegasus framework + practitioner pipeline + university partnerships + execution configuration. others conceptually understand the opportunity but don't have the design to capture it.

part 2: gradient of context / vulnerability matrix​

the most important strategic architecture discussion in the conversation. how information flows and who gets what level of truth.

  • concentrated creative context. Gary and Ron hold the most concentrated creative context. they see the full game design: infrastructure layer, industry layer, role layer, education layer, spiritual layer. nobody else needs to see all of it at once.

  • gradient below them. people only need to know what they need to know for their role. this isn't deception; it's operational design. a movement builder doesn't need to understand cap table strategy. an applied AI engineer doesn't need to understand the puppeteering dynamic. giving people the full picture overwhelms them and diffuses their focus.

  • private truth and public truth. (Hillary Clinton reference.) not about lying. about recognizing that different audiences require different framings to be actionable:

    • public manifesto: "there's lots of money to be made, here's how to find your role in the imagination economy." aspirational, accessible, Pegasus-level framing.
    • partners/collaborators: enough context to see their specific opportunity and say yes. tailored to their domain.
    • core team: more strategic context, but still scoped to their function.
    • internal wiki: the full truth. this is the repository of what we're actually building and why.
    • Gary + Ron: the complete game design. full vulnerability, full context, full strategy.

  • vulnerability matrix. how much to share to get buy-in without over-sharing. the key question for every conversation: what does this person need to understand to take the action we need them to take? share that. not more. not less.

  • don't telegraph punches. this isn't about people stealing ideas. it's about being disarming. if people realize the level of consciousness and capability behind the operation, some will feel threatened, some will try to co-opt, some will want to slow things down. distill messaging to simple hooks: "come to an Applied AI event" or "come to an Imagos event." don't explain the whole plan. recruit people into the first function of the game.

  • the public manifesto stays at the Pegasus/game level, not the infrastructure/industry level. externally, we talk about supercharging companies. internally, we know we're birthing industries. externally, we talk about finding your role. internally, we're designing the roles that will exist.

part 3: puppeteering​

a loaded word, used deliberately. the concept of people voluntarily delegating strategic direction to Gary and Ron.

  • Seth Streeter literally said: "how would you like to puppeteer me?" people with resources and networks who recognize Gary and Ron's strategic capacity and voluntarily hand over the reins. this is the ultimate signal of trust. they see the game design capability and want to be placed within it.

  • consent-based vs non-consent. this is the critical distinction. the difference between what Gary and Ron do and what Joe (Gauntlet) does:

    • Gary and Ron do it with consent. people choose to delegate. they see the vision and want to be placed.
    • Joe does it without consent. psychological warfare. manipulating people into positions that serve his ego without them understanding what's happening.

  • done humanely, with soul. the puppeteering is in service of the person being puppeteered. Seth gets placed where his resources and network create maximum impact for everyone, including himself. the game design accounts for his flourishing, not just his utility.

  • the aquarium metaphor (Ron's insight). people in systems think they're exercising agency. but someone else sets the temperature, changes the water, cleans the tank. VCs made entrepreneurs feel like they needed them. the fish doesn't know it's in an aquarium. the key difference: Gary and Ron build aquariums where the fish thrive. the old guard builds aquariums where the fish serve the aquarium owner.

part 4: Joe / Gauntlet critique​

detailed competitive analysis. right idea, wrong people, wrong execution.

  • right idea, wrong people. Joe sees the opportunity (applied AI education, talent pipelines, community). but he's ego-driven and can't execute because he's building for his childhood self, not for what people actually need. he creates schools his childhood self would find cool rather than what the market requires.

  • terrible at hiring. the only thing that's actually working at Gauntlet is what Gary orchestrated. Joe's own hires and initiatives consistently underperform.

  • Gauntlet is doing free work for Imagos. they're paying people to come to Austin, building community, creating pipeline. Gary and Ron capture the best people out of that pipeline because those people recognize real capability vs performance.

  • psychological warfare without consent. Joe manipulates people into positions that serve his vision without them understanding or agreeing to the dynamic. this is the fundamental moral failure, separate from the execution failures.

  • corny factor. the aesthetic and energy are off. trying to be cool rather than being substantive. this matters because taste is a competitive advantage and Joe doesn't have it.

part 5: Yasmin opportunity​

a tactical opportunity that emerged. Yasmin brings cybersecurity and Africa connections.

  • cybersecurity connections. countries are literally being hacked and asking for help. Yasmin has direct relationships with governments seeking cybersecurity support.

  • Africa connections. presidents, top-down relationships. Yasmin has access to heads of state and senior government officials across the continent.

  • Oxford keynote May 1-2. Yasmin is keynoting at Oxford. credibility signal and networking opportunity.

  • cyber + applied AI interconnection. agents attacking systems is the frontier of cybersecurity. applied AI literacy is foundational to understanding and defending against agentic threats. the domains naturally overlap.

  • Ron already has Africa relationships. friends with sons of presidents. top-down relationships already in place. Yasmin doesn't create a new relationship channel; she warms up and validates an existing one.

  • don't create interdependency. go top-down with applied AI literacy first. don't make Yasmin a bottleneck or gatekeeper. she warms up relationships, provides tactical optionality, but the relationship architecture doesn't depend on her.

  • overlap in network = tactical optionality. when two people in your network both connect to the same target, you have options. you're never dependent on one path. this is a design principle, not just an observation about Yasmin.

part 6: communication strategy​

how to talk about what we're building without revealing the full architecture.

  • don't telegraph punches. not about idea theft. about being disarming. if people sense the level of consciousness behind the operation, it changes how they relate to you. some people are aware of capability and it makes them defensive or competitive.

  • distill to simple hooks. "come to an Applied AI event." "come to an Imagos event." one action, one frame. don't try to explain the game engine when you're recruiting someone to play the first level.

  • recruit people into the first function of the game. the first function is always something concrete and immediately valuable. an event. a workshop. a conversation. the deeper architecture reveals itself through experience, not explanation.

  • public manifesto stays at Pegasus/game level. the manifesto talks about supercharging companies, finding your role, the imagination economy. it does not talk about birthing industries, game engine architecture, gradient of context, or puppeteering. those are internal wiki concepts.

see also: