BLOCK V · Sovereign Stack · W11
Week 11

Sovereign Stack

A local-AI smoke test on your own hardware, your watchman's redlines wired architecturally, and one MCP server scoped and tested.

Proverbs 22:3 ↑

Watch · Listen

Week 11 in three or four minutes.

A short explainer and an audio companion for this week’s brief — watch before you start, or listen on the move.

▶ Watch the overview
A 3-4 minute walk-through of Week 11.
♪ Listen on the move
An audio companion for this week — for the commute or the gym.

The three tasks for this week

Each task is one twenty-to-thirty-minute action — the kind of work that ships before the day ends, not the kind that lingers on your todo list. Open it, do it, react ✓ in the cohort channel when it’s shipped.

WEEK 11 · TASK 1

Local AI Smoke Test

Install a local model. Run three prompts. Verify nothing left your machine.

There's a category of your life and work that should never touch a cloud server — and the only way to handle it is AI that runs entirely on your own hardware. This week you install Ollama or LM Studio, pull one model that fits your machine, and run three real prompts with the network watching. You verify, with your own eyes, that nothing left your machine.

Action checklist
  • Install Ollama or LM Studio (the Sovereign Stack page walks the options).
  • Pull one model sized to your hardware:
    • 32GB+ unified RAM: Qwen 3.6 or Gemma 4 26B-class.
    • Below that: Phi-4 Mini or a small Llama.
  • Run three real watchman prompts entirely locally.
  • Verify nothing left the machine — turn off wifi mid-session and confirm it still answers.
SOVEREIGNTY IS PROVEN, NOT ASSUMED
"It runs locally" is a claim until you've watched it answer with the network off. Prove it once with your own eyes, and then you can trust the boundary.
SCRIPTURE Proverbs 22:3 — "A prudent man foresees evil and hides himself." Some things you hide on your own hardware before there's ever a breach to react to. That's prudence, not paranoia.
Open the printable task card (PDF) →
WEEK 11 · TASK 2

Define Your Watchman's Redlines

Five categories that never leave your machine. Make it architectural.

Everything you've classified, bounded, and sealed across this course comes together here. This week you name the five categories of content that will never leave your machine — pastoral notes, your kids' health and education, family conflict, financial detail, business strategy — and you wire local AI to handle exactly those. The boundary stops being aspirational and becomes architectural.

Action checklist
  • Pull together your tier-Sensitive list (W1.T2), your Cowork redlines (W7.T1), and your counseling redline (W10.T2).
  • Name your five non-negotiable categories that never touch a cloud model.
  • Route those categories to your local model from W11.T1 — make it the actual tool you reach for.
  • Write the Redlines as a one-page standing order. This goes into your Adjutant next week.
ARCHITECTURAL, NOT ASPIRATIONAL
A redline you merely intend is a redline you'll cross under pressure. Wire it into how the tools are actually set up, so doing the right thing is the path of least resistance.
SCRIPTURE Proverbs 4:23 — "Keep your heart with all diligence, for out of it spring the issues of life." Guarding what's sensitive is guarding the heart of your home and ministry. Build the wall on purpose.
Open the printable task card (PDF) →
WEEK 11 · TASK 3

MCP Server Setup

Wire one local server. Validate it sees only what you scoped.

The frontier of the operator's stack in this era is connecting AI to your own tools and files under your own control — and the Model Context Protocol is how that's done safely. This week you install one local MCP server (Filesystem, Git, or Playwright), wire it to Claude Code or your workflow, and validate that it can see only what you scoped — nothing more. Security as the default, not the afterthought.

Action checklist
  • Pick one MCP server to start: Filesystem, Git, or Playwright.
  • Install it and wire it to Claude Code or your local workflow.
  • Scope it deliberately — point it at exactly one folder or repo, not your whole drive.
  • Validate the scope: ask it to reach outside the boundary and confirm it can't.
SCOPE TIGHT, THEN LOOSEN
Give a tool the narrowest access that lets it do the job, and widen only when you must. The watchman grants ground deliberately — he doesn't hand over the keys to the whole city to save a few minutes.
SCRIPTURE Luke 16:10 — "He who is faithful in what is least is faithful also in much." Faithful scoping of a small server is the same muscle as faithful stewardship of everything larger.
Open the printable task card (PDF) →

Watchman’s Drills

Optional depth · 90 seconds each

Three micro-reps for the week, one a day if it serves you. Skip without guilt — the drill is the rep, not the workout. Sundays off.

WATCHMAN’S NOTE

What I want you to know about this week.

Sovereignty is a prudence issue, not a paranoia one. The prudent man sees danger and takes cover; the simple keep going and pay for it. This week is optional depth for the man who’s crossed the hardware line: a local-AI smoke test on your own machine, your redlines wired in architecturally (not just promised), and one MCP server scoped and tested. Most men won’t need this. If you do, do it on purpose.

More from Adam — a story from the field and what trips most men up — lands here as the cohort runs.

RESOURCES FOR THIS WEEK

Scripture, a book, and the tools that fit.

Books and sermons here are clone-bot picks in Adam’s Reformed lane — pending his personal sign-off.

Weekly rhythm reminder

Mon — Open the week, ship T1 (20–30 min). Wed — ship T2. Fri — ship T3 and post a one-line close-out in the cohort thread. Saturday is the Watchman’s Audit and your reflection on the week. Sunday is rest — drill off, family first.

← back to the full syllabus · ↑ the Mission Log