Uncle J's Insider
Uncle J's Insider
Not a post pile. Insider is organized by reading paths: AI Organization OS, AI HR, Agentic Engineering, and real product samples.
Reading paths
Human in the Loop
Division of labor, judgment, organization interfaces, and governance boundaries in AI adoption.
12 posts
Agentic Engineering
Specs, skills, agent teams, and organization-level output.
14 posts
AI × Organization
Moving management, workflows, and boundaries into AI-native orgs.
28 posts
Knowledge / GEO
Content that is readable by people, indexable by search, and reusable by agents.
9 posts
Products & Ship Notes
One-person products, launch stories, and working systems.
9 posts

The Role Is Not the Right Unit. The Work Fragment Is.
Pull apart a job description and you will find something the document never mentions: a significant portion of this person's actual time goes to checking spreadsheets.

AI Doesn't Replace Your Job. It Replaces a Few Things Inside Your Job.
Most companies stall in their AI transformation because the person at the top started with the wrong question.

After AI Goes In, Do You Cut Headcount?
Most CEOs will not say it out loud. But the real question running in the background is:

A Knowledge Base Is Not a Document Library. It Is Your Agents' Organizational Memory.
Most companies, when they think about a knowledge base, still picture getting information into one place.

AI Adoption Is Not a Tool Purchase — It Is a Rewrite of Your Organization's Constitution
Most companies go through the same motions when adopting AI. The budget gets approved. Employee accounts get provisioned. Vendor demos get watched. A few rounds of internal training get scheduled. Sev

The Demo Worked. So Why Is the Organization Still Stuck?
Among the most dangerous moments in an AI demo is not when it fails.

Human-in-the-Loop Is Not a Button. It Is an Accountability Mechanism.
Many organizations believe they have already implemented human-in-the-loop.

Employees Are Sharing AI Screenshots Every Day. Your P&L Hasn't Moved an Inch.
Work channels are full of AI activity. Someone shares a competitive analysis. Someone posts a polished proposal. Someone shows a data summary that used to take two days and now took half an hour.

Money Won't Fix This: The Decision Vacuum That Follows Every AI Deployment
There is a case that stayed with me for a long time.

FDE Is Not an Engineer. It Is the Organization Interface.
Human in the Loop, Part 7. In May 2026, FIS, OpenAI, and Google Cloud all bet on forward-deployed engineers. FDE is not engineer-plus-sales. It is the physical embodiment of the organization protocol layer — the interface that moves judgment between the customer site, the production system, and the chain of accountability.

Why the Org OS Cannot Run AI
Human in the Loop, Part 2. The model is not the bottleneck. The roles, the workflows, the knowledge, the responsibility lines, and the three ledgers underneath them — those are what cannot run the new division of labor.

Human in the Loop
A nine-essay series for founders, CEOs, and business owners. AI is not a new tool. It is a new division of labor. Human-in-the-loop is not a confirm button. It is who decides, who signs, and who can stop the system before it touches the real world.

The Organization OS Architect
Human in the Loop, Part 9. By the ninth essay the question is no longer about AI. It is whether the company has anyone who can redesign the organization OS itself.

A/O/G: Three Cuts Into One
Human in the Loop, Part 8. The CEO does not start by asking which AI to buy. The CEO starts by deciding which knife to pick up first — the action cut, the organization cut, or the governance cut. A/O/G is not a maturity model. It is a surgical table.

The Judgment Premium
Human in the Loop, Part 6. The cheaper AI makes actions, the cheaper actions get; the cheaper actions get, the more expensive judgment becomes. HITL is not a confirm button. It is three rights: judgment, accountability, and the final veto.

AI Replaces Actions, Not Organizations
Human in the Loop, Part 5. Wulf's six interaction modes only tell you where humans and AI stand in a workflow. Cross them with five layers of organization design — role, process, knowledge, accountability, governance — and you get a 6×5 matrix executives can actually run a meeting on.

The New Labor Contract
Human in the Loop, Part 4. Once Skills, Agents, and anti-distill tools show up, the contract between company and employee stops being about hours. It gets repriced around injection, judgment residue, and accountability.

Why the HR Three-Pillar Model Breaks
Human in the Loop, Part 3. The three pillars are not getting kicked over by AI. The old interface stopped carrying current. What HRBP actually sells is judgment translation — and that half is the first to get discounted.

AI Is Not a New Tool. It Is a New Division of Labor.
Human in the Loop, Part 1. Once the agents are running, the real question is not which model you bought. It is who decides, who signs, and who is on the hook.

The 11 Failure Modes of AI Agent Systems
AI agent failure modes I've cataloged after eighteen months running multi-Agent systems in production. Eleven distinct ways agent systems fail — every one of them is a management problem I saw in my HR career first.

How I Manage Agent Teams Like a Company
Last quarter I fired three AI Agents. Here's how I manage Agent Teams like an HR director runs a company: org chart, performance reviews, firing policy.

From HR to AI: What 18 Years of Managing People Taught Me About Managing Agents
I spent 18 years in HR — layoffs at AB InBev, building people infrastructure at SnowPlus, leading 150 at Longfor. Then I left and started writing code. Four days, 52 spec documents, 105,000 lines. People asked what made me think I could do this. They were asking the wrong question. Managing fifty AI Agents and managing fifty people are the same job.

95% of People Are Stuck Optimizing Prompts. They Are Wrong.
95% of companies are managing AI the way you manage software. Agents aren't tools — they're coworkers. The scarcest skill in the AI era isn't engineering. It's people who understand both organizations and Agents.

He Attached the Same 4 Pages to Every Letter for 23 Years
Bezos wrote 24 shareholder letters over 23 years. At the end of every single one, he attached a copy of his 1997 letter — the one from the year Amazon went public. Not ritual. Not nostalgia. A contract he signed with his future self, and re-signed annually in public. This is what those letters actually say.

Most "AI Agents" Are Just Chat Boxes in a Costume
Everyone is building "AI agents." Almost none of them are. After studying the Claude Code source leak, shipping my own agent SDK, and watching a founder show me a chat box and call it an autonomous system — here's what actually separates an agent from an LLM wrapper. Seven decisions. Seven rungs. One framework you can use in the next five minutes.

Wishing, PUA-ing, or Building Walls? Three Stages of Actually Using AI
I spent 18 months going from wishing AI would work to yelling at it to building systems where it cannot fail. Here is what I learned — and why 11,600 developers are still stuck at stage two.

17 Red Lines for a $2 App
Most apps ship features. One Page ships constraints. 17 red lines, zero third-party dependencies, one gesture, 30 seconds. Here's what happens when you design a product by deciding what it will never do.

The First Day I Wrote My Thesis, I Didn't Write a Single Word
Because a thesis is a system, not a document. A 320-line CLAUDE.md constitution, 12-item SSOT data calibration, 4 Phase Gate quality checks, a 1,262-line assembly script, 61 references fully verified, advisor feedback ticketized. The full systems engineering breakdown of a Peking University MBA thesis.

My Obsidian Is Not a Note-Taking App — It's an Operating System
506 git commits. 85+ AI Skills. 3 lifecycle Hooks. 435 auto-generated session logs. 7 platforms. One person. Under 60 days. How an HR guy turned Obsidian into an operating system. 14,000 words. The entire system, taken apart.

Organization Design Is Agentic Engineering
I can't write a single line of code. 4 days. 52 modules. 2,716 tests passing. 105,000 lines of code. How? I spent 18 years learning to design systems that run without me watching. That system used to be called an organization. Now it's called an Agent team.
Subscribe to Uncle J's Insider
Notes on AI organization, AI HR, agentic engineering, and content systems when they are worth sending.
