Skip to main content

operating principles

from Ron, co-signed by Gary. living document.

security protocol​

gradient of context​

information flows on a gradient. the tightest circle is Gary and Ron. from there, context expands outward deliberately and selectively. not everyone needs the same level of information. treat every piece of context as something you are choosing to release.

conversations are closed by default​

  • never have substantive conversations in front of anyone who doesn't need to hear them: drivers, guards, assistants, acquaintances, anyone
  • if you're in a car, a lobby, a shared space: wait until it's a closed setting
  • this includes seemingly small details: codes, addresses, names, plans
  • if you slip, own it and tighten up immediately. no debates about it.

move quietly around security/staff​

  • guards and support staff are there to protect, but they have their own networks and histories. assume interconnectivity.
  • don't reveal how we move, what tools we use, or what we know in front of them
  • at this stage: guards stay in the car. they don't need to get out. they don't need to be in the room.
  • this will evolve as trust is earned, but the default is tight.

own setup, every city​

  • always travel with our own camera/security setup connected to our phones
  • never rely on someone else's infrastructure for sensitive environments
  • devices stay on us at all times

communication discipline​

less is more​

  • two ears, one mouth. default to listening.
  • always understate. never oversell capabilities, connections, or intentions in conversations.
  • being overly verbose gives people leverage. refine the speech.
  • in discovery conversations with potential partners/clients: ask, don't tell. let them reveal before you do.

speak to one, assume millions​

  • talk to one person as if you're speaking to a million people, because that's the distribution power everyone has now
  • assume anything you say can reach 2, 5, 10, 20 million people if it's the type of thing people want to hear
  • this isn't paranoia. it's wisdom about the world we live in.

no scrambling​

  • being unprepared gets you tricked off your spot. preparation is protection.
  • always be present, always be on point. what we're building is powerful and attracts attention.
  • don't rush, don't scramble, don't wing it. move deliberately.

meeting discipline​

avoid 1:1s when possible​

  • the default is never a 1:1 meeting. the default is: invite them to walk in to something that's already happening.
  • options in order of preference: Matt Holm's walking group (nearly daily), Applied AI Live or other events, quick group zoom. 1:1 only if absolutely necessary.
  • this serves two purposes: it saves our energy (no calendar bloat from coffee chats), and it lets people experience the network firsthand without us having to explain it.
  • when someone new wants to connect, the move is "come through to this" — not "let's grab coffee." showing is stronger than telling. the network sells itself.
  • the Matt Holm filter: "if you wouldn't wanna intro them to Matt, you probably shouldn't be giving them your time." if someone isn't worth bringing into the circle, they're not worth a meeting at all. simple decision-making filter for who gets your energy.
  • 5 birds 1 stone: every gathering does multiple jobs at once. a walking group or event isn't just networking — it's warming up the LP pool for the real estate play, showcasing the network to potential partners, building community, generating content, and filtering talent. if a meeting only serves one purpose, it's probably not worth having.

accountability​

when you slip​

  • acknowledge it immediately. no ego, no defensiveness.
  • correct the behavior going forward. one slip is human. a pattern is a liability.
  • if someone on the team consistently slips: that's a disqualifier. lack of wisdom at that level is a liability to everyone around them.

watch and follow​

  • Ron sets the operational tempo on security and movement. Gary follows the lead here.
  • this isn't about hierarchy. it's about who has the pattern recognition for this domain.
  • as the team grows, new members learn by watching, not by being told every rule. the rules are felt, not litigated.