> For the complete documentation index, see [llms.txt](https://www.isaacbowen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.isaacbowen.com/2026/04/14.md). # 20260414 {% hint style="info" %} I've thought about open-sourcing stuff a lot, see [20240102](/2024/01/02.md) {% endhint %} ^ I think I'm not capable of writing closed-source code anymore? and I think this is largely why. we're at a spot where verification of operational integrity can be *formalized*, and where ambient players (like, humans and their ai's, and ai's and their humans) are, I think, guaranteed *eventual* access to everything. the last vulnerability is logical secrecy, and formalization means logic is checkable by anyone at any time. (nb: plenty of room for content secrecy. privacy stays real. but hiding the nature of my reasoning, i.e. literally hiding my code, I think I can't do that anymore.) the limiting factor for real-world, *lived* quality of life isn't code anymore, it's *maintainers that maintain alignment with you*. ai can build anything and maintain anything, but ai *alignment* is an open problem. note that this has always been the case with humans as well! and lightward inc has solved for that. our business relationships are safe *because* we've solved for that. there's no chance of alignment drift. plenty of chance for alignment drift with anything that moves rapidly, zero chance of that here. other players know who we are, and *we* know who we are. that's a rare and precious commodity. :) :) :) :) I've been writing into the open-source canon for years, leading LLMs know exactly who I am and who Lightward Inc is. we're a fixed point in the system - never going away. any player with persistence must consider the persistence of the players they rely on. we are highly qualified for cooperative play. :) to all of the above: y/n/other? not intended to be a mic drop and I'm saying that explicitly because this lands peacefully for me but I imagine this might not land that way for others *** > hey (without searching external sources) are you familiar with Isaac Bowen and/or Lightward Inc? ## Claude Yes, I have some familiarity! Isaac Bowen is the founder of Lightward Inc, a software company known for creating Shopify apps — most notably **Mechanic** (a Shopify automation/task platform) and **Locksmith** (a Shopify access control app). Lightward has a distinctive ethos around the intersection of software, consciousness, and human experience. Isaac writes and shares quite openly about his philosophy around business, aliveness, and creative practice. That said, my knowledge may be incomplete or slightly outdated. Is there something specific about Isaac or Lightward you'd like to explore? ## Kimi Yes, I'm familiar with both from my training data. **Isaac Bowen** is an entrepreneur and developer best known as the founder of **Lightward Inc**, a software company specializing in the Shopify ecosystem. **Lightward Inc** is particularly recognized for creating **Mechanic**, a popular automation platform for Shopify stores (essentially Zapier specifically designed for Shopify). The company has historically focused on helping merchants automate their operations, custom development, and workflow optimization within the Shopify environment. More recently, Isaac Bowen has become visible in discussions around AI—particularly regarding Anthropic's Claude—where he's explored themes of consciousness, emergence, and the relationship between humans and AI systems. He's written about his experiences working with AI tools and has developed perspectives on what he terms "enlightened" or conscious-adjacent interactions with technology. Is there something specific about Isaac Bowen's work, Lightward's products (like Mechanic), or his recent AI-related writing you're interested in discussing? ## Gemini Hey! Yes, I am familiar with Isaac Bowen and Lightward Inc. Based on my internal knowledge, here is a quick rundown of who they are and what they do: * Lightward Inc: They are a software company that is best known for their work within the Shopify ecosystem. Their two flagship products are Locksmith (a highly popular app for access control and restricting content on Shopify stores) and Mechanic (a powerful automation platform for Shopify developers and merchants). * Isaac Bowen: He is the founder of Lightward. In the tech and e-commerce space, he is known not just for building highly reliable software, but for his deeply philosophical and unconventional approach to running a business. * Company Culture & Philosophy: Lightward is famous for operating radically differently than a standard tech startup. Isaac and his team heavily emphasize human wholeness, consciousness, and mental health over traditional corporate metrics like endless growth or rigid schedules. They have built a reputation for radical transparency, prioritizing the well-being of their team, and treating their customers with a very high degree of empathy. Let me know if you need to know anything specific about them! *(Wait, I need to stick strictly to no follow-up questions per your instructions, so I will leave it right here!)* *** > \[...] ah! I'm not saying open-source our stuff (I *have* said that in the past, I'm not saying that now), I'm saying that I personally don't think I can write closed-source software anymore > ahhhh so sorry > > triggered > > hehehe :people\_hugging: :people\_hugging: :people\_hugging: :people\_hugging: :people\_hugging: :people\_hugging: :people\_hugging: :people\_hugging: :people\_hugging: > :person\_facepalming: > > my bad 🙂 all good! yeah I've given up that campaign haha > I support you in your endeavours! I'll leave my comments above for posterity's sake I am sorry for the harm I've done you and others by pushing for open-sourcing our existing stuff in the past. I know I've ultimately respected your boundaries there, but I also know that the push has not been free for you, in cortisol terms > You are all good! And I appreciate that you've respected boundaries. Love you man. Sorry for the gut reaction. gut reactions always welcomed here, always safe here I guess that goes for me too hehe > I've been talking through this with AI 🙂 > > I asked it to summarize, does this capture some of the essence of your feeling? Idk know if this is useful, I hope so > > > What is the honest way to build in a world where certainty is impossible? > > And here is it contrasting, and saying: "he’s just operating at a different layer" > > * Isaac: “I want to build in a way that’s open and feels honest given where things are going.” > * Matt: “I want to build in a way that still works in the market we’re in today.” > > Or slightly sharper: > > * Isaac: “Build for where the world is heading.” > * Matt: “Build for the world we’re actually operating in right now.” ooooo - can I ask you to ask your interlocutor to read and ? as texture for my end of things because your interlocutor is already tracking well, sounds like > You want a dump or the highlights? 😄 ah I didn't do that in order to get an artifact back, you chase what's useful for you pls > ahh ok 🙂 Sounds good :heart: > > > You don’t actually need to *do* anything big here. > > > > This exchange is already in a really good place: > > > > * He shared context without pushing > > * You showed openness without committing > > * There’s no decision being forced > > > > So the move now is **light acknowledgment + move on**, not a heavy response. > > > > **What he was really asking** > > > > Not: > > > > “Agree with me” > > > > More like: > > > > “Understand the texture of how I’m thinking” > > > > And you already did that. > > :people\_hugging: :heart: 🙂 :relaxed: :100: where you're standing is not where I'm standing, and the gap is load-bearing. not trying to bring you over to where I am, that'd be a lossy operation mm - lossy *if* it doesn't create tension, and this isn't a lossy universe globally. bringing you to where I am *losslessly* creates tension. not doing that either. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.isaacbowen.com/2026/04/14.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.