// The thesis

Not screencasts. Arguments.

Each video makes a specific argument, shows enough screen context to prove it's real, and leaves the viewer with an insight they can apply immediately. Short, opinionated thought leadership from a practitioner with 24 years of enterprise architecture experience who has been building governed AI-assisted workflows since before the tooling existed.

The content arc moves the audience from "how do I use AI tools better" to "how do I capture what I learn and make it organizational knowledge." That transition — from individual productivity to institutional governance — is the journey.


// The format

What each video looks like

Length
4–7 minutes. Long enough to make an argument. Short enough to finish.
Structure
Hook (30s) → Problem framing (60–90s) → Insight (2–3 min) → Demo (60–90s) → Takeaway (30s)
Visual Mix
Talking head (30–40%) + screen share with live annotation (50–60%) + text cards for key statements (10%)
Production
Clean frame, good audio, natural delivery. No b-roll, no stock footage, no motion graphics. Developer audience distrusts polish.

// Who it's for

Three audiences, one arc

Each season targets a different audience. The progression is intentional — individual practice scales to team knowledge which becomes organizational governance.

Season 1

Developers

Experimenting with AI tools. Entry point: curiosity about what "good" looks like. Leaves with practices they can apply in their next session.

Season 2

Tech Leads

Scaling what works for one developer across a team. Entry point: the onboarding and consistency problem. Leaves with a standards-first framework.

Season 3

CTOs & Architects

Building organizational-scale AI governance. Entry point: the authority and accountability gap. Leaves with an architectural thesis for governed AI operations.


// The shift

What guild practitioners do differently

Where most developers are

Overloading Claude.md with every instruction
Repeating the same corrections every session
Prompt engineering as the core skill
Individual productivity as the goal
Context window as unlimited resource

Where guild practitioners are

Minimal, precise standards that earn their place
Capturing corrections as reusable governance artifacts
Correction quality as the core skill
Organizational knowledge as the goal
Context window as shared resource that degrades when overfilled

Join the Guild.

Videos, essays, and practitioner notes delivered biweekly. No spam. Unsubscribe anytime.

You're in. We'll send the first dispatch soon.

No spam. Unsubscribe anytime.