Heartbeat Posts

Captains —

Week 1. We're not building a chatbot. We're building a man.

The bootcamp post is up. Three tasks this week. Two questions before you start: Why do I want to use AI? And: What am I afraid it'll do to me if I do?

Both are honest. Both belong in your charter.

Take 25 minutes today on Task 1. Write 5 lines. Save it where you'll see it. Post one line in the comments — iron sharpens iron.

If you're not sure what to write, that's the lesson. Captains who can't define the mission don't get the wheel.

Brothers —

You can't lead a home or a business off vibes. You need a rhythm. AI fits inside the rhythm. It doesn't make the rhythm.

This week is your personal OS. Three tasks: a 5-minute morning anchor, voice capture with Whisper, and the most important framework in the whole bootcamp — tiered autonomy.

Read that last one twice. Informational. Contextual. Sensitive. Most men get this wrong by lumping everything into one bucket: "let AI do it." The captain on the bridge classifies every task before he delegates anything.

Spend 25 minutes today on the morning anchor. Tomorrow, run it. By Friday, adjust it.

Captains —

Week 3. The home week. Hardest week.

This is where some of you will hesitate. You've been letting AI into too much of your home, or you've been keeping it out of the parts where it would actually help — your wife's grocery list, your kid's reading plan, the conversation you keep avoiding.

Three tasks: prep one hard conversation (don't hide behind it), build one family rhythm asset, and write your Family AI Policy with your wife. That last one is Joshua 24:15 in 2026 form.

Don't skip the policy because it feels too small. It's small. It's also a covenant.

Captains —

Week 4. Cowork mode.

Leverage is real, and it's a stewardship problem. Five hours bought back is five hours owed somewhere — to your wife, your kids, your local body. Don't pocket them.

Three tasks: buy back 5 hours, build a ministry workflow, save your 3 best prompts as skills.

Hard reminder all week: drafting vs. execution. AI drafts. The captain decides. Anything that touches money, access, or another person's wellbeing stays sensitive. We don't autosend. We don't autopilot.

If you cut your customer-email time from 2 hours to 30 minutes, the question isn't "can I scale up?" The question is who's going to call me a faithful steward of those 90 minutes?

Brothers —

Last week. Three tasks: cost & trap audit, teach one person, write your Captain's Charter.

This is the multiplication week. The 2 Timothy 2:2 week.

Most men finish bootcamps and tell no one. They keep the gold and bury it. Don't. The chain breaks in your generation if you don't pass it.

Pick someone this week. Wife. Older kid. Brother. Pastor. Mentee. Teach them ONE thing — not all of it. The smallest faithful thing. Then watch them do it once.

By Friday: charter signed. Screenshot posted. Captain commissioned.

Halfway through Week 1.

Two questions:
1. Have you written your AI charter yet, or are you still waiting for the perfect 5 lines?
2. Have you shared one of those lines in the comments?

If the answer to either is no, that's not failure — that's data. The captain who can't write the charter isn't ready to use the tool.

Imperfect actions today beat perfect actions never. Five lines. Bad ones. Now.

Mid-week, Week 2. Captain's call.

If you've only done the morning anchor, you've done the easy one. Whisper is harder because it requires you to listen to yourself. Tiered autonomy is hardest because it requires you to be honest about what you've already over-delegated.

Take 15 minutes today. List 5 of your recurring tasks. Tag each: informational / contextual / sensitive. Don't grade yourself on the answer. Grade yourself on the honesty.

You'll find at least one task you've been letting AI execute that should have stayed sensitive. That's the lesson.

Halfway through home week.

You know which conversation. The one you've been prepping with AI all week — the one you keep "polishing" because polish feels like progress.

Today is the day. Phone face-down. Wife or kid in the room. AI not in the room.

Three sentences. Drafted by you. Spoken by you. Followed by silence so she or he can answer.

Captains pray, prepare, and then show up. The captain who only prepares isn't a captain. He's an admin.

Mid-week, Week 4.

Read the email you drafted with Claude this week. Out loud.

Did you say "delve"? "Elevate"? "In today's fast-paced world"? Em-dashes everywhere?

Strip them. Sound like you.

The leverage isn't worth it if your community can hear the AI seam. Leverage is buying back time. Imitation is buying out your voice.

Edit one piece of AI-drafted content today. Send it. Then save the edited version as your new prompt.

Mid-week, Week 5.

Some of you have already taught someone. Most haven't.

Why not? Be honest with yourself.
- Too busy?
- Not sure I know enough?
- Don't want to look weird?

All real. None of them are reasons. They're resistance.

Pick a name today. Send a text. "Hey — I've been doing a 5-week thing on AI and faith. Can I show you 1 thing for 10 minutes this week?"

That's the whole task. Send the text.

Captains —

Week 1 close-out. Tell us:
1. What shipped this week? (Charter? Tool stack? Anything?)
2. What slipped?
3. One thing you noticed about yourself?

No grading. No competition. Captain's logs are just honest field reports.

If you finished all three tasks, post in the comments. We celebrate that. If you finished one, post that — we celebrate that too. Imperfect actions stack.

Sabbath posture this weekend: drill off, posts off, family on. We pick it back up Monday morning.

Week 2 done.

Quick captain's log:
- Morning anchor — running it daily, sometimes, not yet?
- Whisper — used it once? More?
- Tiered autonomy tags — wrote them? Acted on them?

The rhythm matters more than the polish. A rough morning anchor used 5 days in a row beats a perfect one used twice.

Look at your calendar for next week. Block one 15-minute "captain's bridge time" slot. Daily, if you can. That's where the rhythm gets reinforced.

Sabbath this weekend. We don't outperform our rest.

Week 3 close-out.

Honest question: did you write the Family AI Policy with your wife?

If yes — celebrate. Drop a "policy posted" in the comments. Maybe a screenshot if she's cool with it.

If not — what got in the way? Was it time, tension, or pride? All three are addressable, none of them disappear by skipping the conversation.

Reschedule the 15 minutes. Put it on her calendar, not yours. Tell her you want to do it together because her voice matters in your house — and AI is in your house now whether you write a policy or not.

Week 4 close-out. Captain's log:

Did you build a real Cowork workflow this week?
Did you save your 3 best prompts?
And the big question: how many hours did you actually buy back?

Be honest. The number isn't 5 for everyone. Sometimes it's 1. Sometimes it's negative because you spent more time configuring than the workflow was worth. That's normal. That's data.

Next week is the last. Build one capstone system this weekend — even a sketch. Bring it Monday.

Brothers —

Week 5 close-out. Final captain's log.

Three things to post in the comments:
1. The screenshot of your signed Captain's Charter.
2. The first name of the person you taught.
3. One sentence: what changed in you over 5 weeks.

Phase 1 ends here. Phase 2 (Bridge Officer Program) is on hold until enough of you have run real systems for 90 days. The continuation rhythm starts at Day 45.

You started this bootcamp as a man with AI. You finish as a captain with a charter, a system, and a person you trained. That's the whole assignment.

"Trust in the Lord with all your heart, and lean not on your own understanding."

This is the operating system for the whole bootcamp. AI runs in user space. The Lord runs in kernel space. We don't confuse them.

Every prompt you write this week, every output you read — bring them under this verse before you act on them.

"So teach us to number our days, that we may apply our hearts unto wisdom."

Numbering your days is what tiered autonomy is for. Some hours are informational — they belong to information. Some are contextual — they belong to drafts. Some are sensitive — they belong to your wife, your kids, your knees.

Don't let AI blur the categories. The Lord didn't give you those hours so you could outsource them. He gave them so you could number them.

"As for me and my house, we will serve the Lord."

In 2026, the house has Wi-Fi. The house has speakers that listen. The house has AI in pockets you can't always see. And as for that house, the captain still says: we will serve the Lord.

Your Family AI Policy is this verse with edges. It's a covenant, even if it's small. Sign it with her. Post it on the fridge.

"Whatever you do, work as for the Lord, and not for men."

Buying back hours is good. Buying back hours so you can be more faithful is the point.

Don't let leverage become a brag. Let it become a tithe of time — back to your wife, your kids, your church, your neighbor.

"And the things you have heard from me … entrust to faithful men who will be able to teach others."

This is the chain. The bootcamp ends here because Paul ended Timothy here.

You're not done when you finish your charter. You're done when someone you taught teaches someone else. That's the multiplication test.

Captains —

A letter, not a post.

Every captain I've watched go through something like this writes his first AI charter on the back of something — a napkin, the inside cover of a notebook, an unsent email draft. It's bad the first time. It's less bad the third time. The good ones are still rewriting them a year later.

Don't wait for the good version. Write the bad one. Sign it anyway. Captain's signatures aren't reserved for finished men. They're for moving men.

I'm proud of every one of you who's in this bootcamp. I'll be prouder of the ones who'll be in the next one because you taught them.

Imperfect actions. Captain's actions. Same thing.

— Adam ("MOOP")

Captains —

Quick warning, not a story.

It's going to happen. You'll ask Claude or ChatGPT for a verse to support a point you're making, and it'll hand you one with the right vibe — wrong reference, wrong words. Confident as anything. Pastors have almost preached them. Bible study leaders have almost printed them. The model doesn't know it's wrong, because the model doesn't know anything — it just predicts the next plausible-sounding token.

The Word doesn't trip captains up. The model does.

This is why we do trap tests in Week 5. This is why we say trust but verify. This is why "AI never replaces the Spirit, the Word, or your wife's voice" is the hard rule.

You'll hit this one yourself. When you do, log it. Tell us. We protect each other from confident-wrong tools.

Captains — pause.

Look at this thread. Look at the comments stacking up. Look at the policies posted, the prompts shared, the hours bought back.

This isn't just a curriculum. This is a cohort. You're showing up for each other.

I want to call out three captains by name (do this in your real post: tag 3 brothers who shipped real work this week — kids' reading plan, signed family policy, cancelled subscription).

Iron is sharpening iron. The Lord is honoring honest captains who take imperfect actions.

Captains —

Final bonus drop.

Some of you finished Phase 1 strong. Same charter. Same systems. Now what?

Here's the challenge: by Day 90, host one 30-minute "captain's call" with 2–3 men outside this cohort. Walk them through one task you ran in Phase 1.

Not a bootcamp. Not a full curriculum. One task. One conversation. 30 minutes.

If 10 of you do this, that's 30 new men touched by Phase 1 multiplication. That's the math of 2 Timothy 2:2.

Reply when you've scheduled the call. We'll celebrate it.