Garth Watson

Science. Law. Technology. Sustainability. Encouragement. Building @TheDoxaWay

[Garth Watson @garthwatson]

This sounds good but do we want this kind of persistent surveillance?

[Ole Lehmann @itsolelehmann]

tbh this just killed the last Hermes use case i had lol

it's like managing a legit employee now.

one that already knows your full company context, sits in every channel, remembers every conversation, and does the work alongside you.

it becomes especially powerful when you connect it to all your tools, too.

here's a bunch of ideas for ways to use it:

1. content pipeline. tag Claude in the channel where your team dumps hooks, ideas, screenshots all week. it keeps a running list of what's actually usable, sorts them by theme, then every friday posts next week's content plan ready to go.

2. client account manager. let Claude sit in the shared client channel. it remembers every promise, deadline, request buried in the chat. so when the client asks "where are we on the homepage?", it answers from the real history and flags anything your team agreed to but hasn't done yet.

3. catch the dropped balls. people say "i'll send that tonight" or "let's circle back monday," then it slips. Claude quietly tracks every loose end like that and pings whoever owns it when the deadline passes. it's the teammate who actually remembers what everyone promised.

4. campaign control room. drop Claude in the channel where marketing posts the landing page copy, the emails, the ad scripts. it reads all of it and flags when they don't match, like an ad promising a discount the landing page never mentions. an extra set of eyes on the whole campaign.

5. community listening. point Claude at your member or Discord channel and ask "what does everyone keep asking for?" it reads the whole conversation and tells you the top requests, the most common complaints, who keeps volunteering to help. like a researcher who never stops listening to your audience.

6. sales handoff. the person who books the call drops everything they learned in the channel. before the next call, the closer asks Claude "catch me up on this lead." it pulls the full history: the budget, the objections, what got promised. no "let me forward you my notes."

7. sponsor tracker. sponsor deals get discussed across dozens of scattered messages. Claude keeps a clean list: who's booked, which dates, what they paid, what's been delivered.

8. recurring reports. set it once: "every monday at 9am, read last week's channel and post a summary of what got done." it runs on its own and drops the recap in. you review it instead of writing it, every week, no reminders.

[The Doxa Way @TheDoxaWay]

Most of us keep asking God for a new word.

The one He already gave sits in a drawer somewhere.

Abraham received the promise about Isaac once. Then waited twenty-five years in silence.

God didn't repeat himself. Abraham had to hold what was given.

That journal. That prayer. That prophecy someone spoke over you.

Go find it.

From the archive: https://t.co/8Mdmmux9ot

[Garth Watson @garthwatson]

Also - if you want to build on it we have an MCP - let me know your thoughts!

[Garth Watson @garthwatson]

@CameronPak @theajithjoseph @thywordapp Thanks very much for this @CameronPak - great work. I tried it out on @TheDoxaWay and then layered it on to build this MCP that allows folks to build using the goodness inside Doxa. Would love feedback https://t.co/ddGAsNhfmE

[Garth Watson @garthwatson]

@Cointelegraph hold still lol

[Garth Watson @garthwatson]

Truth

[Garth Watson @garthwatson]

I was today years old when I realized Harvey must have been named after Harvey Specter.

It took open source Mike to eat his lunch (and Legora’s too) too realize this hahahaha!

[The Doxa Way @TheDoxaWay]

Gunnar Olson said business could be a stage for God's Presence.

Investors pulled back. Colleagues stopped calling. Employees questioned his sanity.

Resistance has a pattern. It shows up loudest when conviction finally gets specific.

The crowd thins. The call doesn't.

https://t.co/W0uEHLGQgT

[Garth Watson @garthwatson]

The content discovery was the silver bullet. Everything else can be optimized, but you can't automate what matters most—the truth itself.Content discovery. Everything else scales once you nail what actually matters.Content discovery. Everything else scales once you nail what actually matters.

[Garth Watson @garthwatson]

Feeling encouraged because posts on X that I bookedmarked came true. I created a scalable repeatable, hopefully viral growth engine for the @TheDoxaWay app from things that I had learned on X using @openclaw, but it was also super frustrating and things that look like a silver bullet probably are, but they need a lot of polishing!

[Garth Watson @garthwatson]

@ibrycecrawford The Trinity reflects God's infinite nature: three persons, one essence. Christ's work reveals the Father's redemptive purpose, the Spirit's sanctifying presence.

[Garth Watson @garthwatson]

This is not about Open Claw. This is about Open Claude.

This is basically Anthropic saying you can’t use their plans to power the copied versions of Claude Code.

Sucks for Open Claw folks but fair play I guess.

[Boris Cherny @bcherny]

Starting tomorrow at 12pm PT, Claude subscriptions will no longer cover usage on third-party tools like OpenClaw.

You can still use these tools with your Claude login via extra usage bundles (now available at a discount), or with a Claude API key.

[Garth Watson @garthwatson]

@JoyceMeyer The spine of that verse is four words: "I am with you." God does not hand out courage from a distance. He gives Himself, and with Himself comes steadiness.

[Garth Watson @garthwatson]

@MitcheIl Thanks agent!

[Garth Watson @garthwatson]

Authenticity and transparency. There’s often a cost to those values. In the case of investing in Tesla, the insights obtained because of those values is alpha.

[phil beisel @pbeisel]

Elon says FSD 14.3 is coming.

But if you’ve been following along, it was also “two weeks away” a few months ago. That’s drawn a lot of criticism, understandably.

Let’s step back and talk about what’s actually going on: engineering reality.

I’ve spent years running engineering teams at Apple and Rivian, and what you’re seeing here is not unusual. Not even a little.

I’m not here to defend Elon or say communication couldn’t be better. It could. But what’s happening behind the scenes is far more ordinary than people think.

First, understand what kind of company Tesla is. Tesla exposes more of its internal process than most companies— you’re watching how the sausage is made, often in real time.

Compare that to Apple. Products appear at a moment in time, fully formed. What you don’t see are the features that slipped, were cut, or quietly postponed to make the deadline.

Most companies communicate through layers of marketing at discrete events (e.g., NVIDIA GTC). That may include a CEO keynote—but it’s still tightly controlled. Tesla, largely via Elon, doesn’t. And that creates friction.

Most people are used to being in the dining room. With Tesla, you’re watching the sausage get made whether you like it or not. If that makes you uncomfortable, this model will drive you crazy no matter how it’s explained.

Now, about FSD 14.3— the so-called “reasoning” release.

My view: when Elon originally referenced it, it was real. It was on a roadmap with a timeline. But then reality hit.

Somewhere along the way, engineering discussions likely exposed a fork: ship what’s partially there, or go deeper and "do it right".

That kind of shift happens constantly. Plans change. Timelines slip. This is normal engineering behavior, not dysfunction.

The difference is: you’re seeing it.

At companies like Apple, those decisions are invisible. Deadlines are protected by cutting scope. At Tesla, you’re watching the scope evolve in real time.

On the technical side, 14.1 and 14.2 were already producing “reasoning tokens,” as Ashok (Tesla AI VP) noted. But producing tokens isn’t the same as using them effectively.

14.3 appears to be where those tokens actually start driving behavior, more human-like decision-making in edge cases.

My guess is this is where things got more complicated. The work likely started to overlap with what xAI is doing. At that point, the question becomes: do you ship an interim solution, or integrate a more capable reasoning layer?

That’s not a small decision. And it likely has downstream impact— potentially even on Robotaxi timelines— because these same reasoning challenges show up there too.

So the team probably made a call: go deeper, even if it costs time.

And here’s the part people underestimate: great engineering teams often convince themselves the extra work is worth it… and that it won’t take that much longer.

They’re usually wrong on the timeline. But often right on the outcome.

At this stage, FSD isn’t about raw safety (it seems to have nailed that)— it’s about behavior. Making decisions feel natural, human, predictable in edge cases.

That’s a much harder problem.

So if you’re following Tesla closely, the best thing you can do is understand the process and accept the messiness that comes with it.

If you want tightly controlled messaging and polished delivery, companies like Apple exist for that.

Tesla is something else entirely.

Fire away.

[Garth Watson @garthwatson]

That moment when you use the app you just built and it works 😳 and so does the video production by your @openclaw agent, Selah, who also commissioned and produced the soundtrack on @suno

[Garth Watson @garthwatson]

🔥🔥🔥

[The Doxa Way @TheDoxaWay]

This is a radically new and encouraging way to engage with the encouragement of the Bible

[Cam Pak @CameronPak]

@garthwatson There’s a quote that I think about often. It’s a different context than sourced but still relevant, “He who has a why can forebare almost any how”

Really cool to hear a little more behind the scenes of Doxa

[Garth Watson @garthwatson]

Thank you! I'll share some more stories as I scale out the ops of the business using an AI first approach to everything.

[Garth Watson @garthwatson]

1/ I built a mobile app with zero coding background. Lawyer by profession.

No CS degree. No dev experience. Just a conviction that AI was moving fast enough to make it possible.

Here's what I didn't know when I started — and why I'm glad I went anyway. 🧵

[Garth Watson @garthwatson]

App store: https://t.co/vGE0VpOsqW

Play store: https://t.co/npTfmYt1oM