DEV Community: ORCHESTRATE

Open Doors, Open Evidence, Open Hands

ORCHESTRATE — Sun, 05 Jul 2026 03:42:06 +0000

Part 5 of 5 — Natural Intelligence at the Family Table

This series ends where the work begins: with an open door.

SolutionWright.com is the public doorway for the work. UniversalNaturalIntelligence.com is where people can begin to see active inference made watchable. IamHITL.com is where accountability and public-record reasoning matter. EducateWright.com is where education, internship support, and opportunity can become real pathways. My Zenodo record is where the reviewable evidence can be found and challenged.

I am not asking people to join a belief system.

I am asking people to join a practice.

Bring your language. Bring your doubts. Bring your recipes. Bring your code. Bring your classroom. Bring your farm. Bring your paper. Bring your lived experience. Bring your grief about what technology has done badly. Bring your hope about what tools could do differently.

In that same conversation with Dr. Alianna J. Maren, she offered that it would be "marvelous to do something to really share with the wider community the value that you bring." I receive that as a responsibility, not a trophy.

Karl J. Friston, Thomas Parr, and Giovanni Pezzulo gave the field an active-inference map many of us can study. Alianna has worked to make the mountain navigable for learners. The Active Inference Institute is building open community pathways. David J.C. MacKay, Norbert Wiener, Claude Shannon, Thomas Bayes, J. Willard Gibbs, Hermann von Helmholtz, Maria Montessori, Fred Rogers, Don Herbert, and John Wooden all sit somewhere in the ancestry of this moment: inference, information, feedback, teaching, wonder, effort, and care. And Jim DeLong, whose introduction and continued signals brought me into these rooms — thank you.

The next step is not to shout louder.

The next step is to make the work checkable.

We take fear out of the history by naming incentives.
We take cult behavior out of science by inviting falsification.
We take ego out of the model by labeling uncertainty.
We take fear out of learning by starting with children, food, breath, and honest questions.

Universal Natural Intelligence as partner, not replacement.

Natural over artificial.

World with world, not profit over people.

Six perspectives

1. Today's pop trends and famous history moments. The pop trend is speed. The deeper historical lesson is that durable ideas take time: a word becomes a method, a method becomes a discipline, a discipline becomes a public responsibility.

2. Global food stability and cost of food. If our intelligence systems cannot help communities understand food costs, soil, water, nutrition, and logistics, they are not yet aligned with life.

3. Tech money and stocks. Capital is moving. It will keep moving. The public question is whether it moves through accountable evidence or through closed claims that nobody can inspect.

4. Life, health, and family. A family does not need perfect theory to begin. It needs one meal, one conversation, one safe question, and one next action.

5. Community, planet, and nature. Regeneration begins when a community stops treating nature as background. The planet is not a resource tab. It is the living context.

6. Mind, community, and health. Mind health and community health are coupled. A lonely mind suffers differently than a held mind. A confused community becomes easier to manipulate. A learning community becomes harder to exploit.

Family table lesson

Ask each person to finish this sentence: "I want technology to help my community by…" Write the answers. Choose one small thing to test this week.

Meal card — dirt-to-plate five-ingredient garden soup

Grow or source: tomato, carrot, onion, beans, basil.
From dirt: grow tomato and basil in containers if that is all you have.
From kitchen: simmer tomato, carrot, onion, and beans until soft; finish with basil.
Teach: soup is a community model. Each part keeps its identity and still becomes nourishment.

Family meditation

Breathe in: "I belong."
Breathe out: "So do they."
Breathe in: "We can learn."
Breathe out: "We can repair."

Family prayer

May our doors open without losing discernment.
May our evidence be strong enough for skeptics and gentle enough for children.
May our work feed the world more than it feeds our image.
May Universal Natural Intelligence remain a partner in service of life.

Open invite

The invitation is open: meet, question, test, translate, teach, and help carry the meaning. calendar.app.google/W5sxWGW73eLT8Vox6.

Previous: Part 4 · Natural Intelligence Is Not a Brand Claim. The series opens with Part 1 · From Dirt to Inference.

Natural Intelligence Is Not a Brand Claim

ORCHESTRATE — Sun, 05 Jul 2026 03:41:43 +0000

Part 4 of 5 — Natural Intelligence at the Family Table

I need to say this clearly because the work deserves protection from overclaim.

Universal Natural Intelligence, which I have been calling UNI, is my project framing and architecture. The established science is active inference, variational inference, probabilistic modeling, cybernetics, information theory, and the Free Energy Principle. I did not invent the foundations. I am trying to build with them, audit them, teach them, and make them useful without breaking the truth.

UNI is natural, not artificial. That is a deliberate choice, not marketing. The public science of Karl J. Friston and colleagues is a story about how living systems predict, sense, and update. It is a story we can borrow with care. It is not a story I get to own.

That is why the Zenodo and GitHub audit record matters to me. The work does not claim new mathematics. It claims an audit method: sentence-level provenance, reproducible tests, and explicit open tensions. It says the AI-executable layer is not enough. Human expert review still matters. The preprint is fenced as unrefereed, and the Layer 2 human review remains pending, on purpose.

That is also why Alianna J. Maren matters. She has been generous with attention, careful with foundations, and grounded enough to remind me, in a recent conversation, that the math is not "hers" in the ownership sense. It is the world's math. I want to hold that line too.

When I architected AGI — the OpenAI Custom GPT I built as our active-inference build guide, not to be confused with the industry hype term "Artificial General Intelligence" — I was not trying to make an oracle. I was trying to make a disciplined companion: a guide that knows when to say "Class A," "Class B," "Class C," "Class D," and "I do not know yet."

The future JAX-based system SolutionWright is building for UNI work must carry that same humility. JAX is a powerful tool for high-performance numerical computing and machine learning. But power is not proof. Proof is proof. Tests are tests. Evidence is evidence. Community review is review.

Six perspectives

1. Today's pop trends and famous history moments. Today's trend is to name the next model as if naming makes it inevitable. The historical lesson is Maria Montessori: prepare an environment where learners can discover, not a stage where the teacher performs dominance.

2. Global food stability and cost of food. Food systems also depend on models: weather, planting, transport, demand, price, policy. When the model is wrong, people can go hungry. That is why model humility is not academic; it is practical ethics.

3. Tech money and stocks. Investors reward claims before communities can audit consequences. A public lab must slow the sentence down: What is implemented? What is demonstrated? What is independently verified? What remains a hypothesis?

4. Life, health, and family. In family life, overclaiming breaks trust. A parent who says "I know" when they do not know teaches fear. A parent who says "Let's find out together" teaches science.

5. Community, planet, and nature. Nature is not impressed by branding. Seeds either germinate or they do not. Water either arrives or it does not. Soil either holds life or it is depleted.

6. Mind, community, and health. A healthy mind can tolerate uncertainty. A healthy community can hold open questions without turning them into identity wars. That is what I want UNI to practice.

Family table lesson

Ask everyone to make one prediction about a seed, a weather forecast, or tomorrow's breakfast. Write it down. Check it later. Celebrate both outcomes: being right teaches calibration; being wrong teaches learning.

Meal card — dirt-to-plate five-ingredient squash rice bowl

Grow or source: squash, rice, onion, pumpkin seeds, yogurt.
From dirt: squash grows from patient vines; seeds return the story.
From kitchen: roast squash and onion; serve over rice; add yogurt and pumpkin seeds.
Teach: a system can feed itself partly by remembering what to plant next.

Family meditation

Say together: "Maybe." Then: "Let's test." Then: "We can learn."

Family prayer

May uncertainty make us careful, not afraid.
May evidence make us humble, not cold.
May we build tools that invite review and welcome correction.

Open invite

Bring a claim you want to make safer before it becomes public. calendar.app.google/W5sxWGW73eLT8Vox6.

Previous: Part 3 · Money Is a Signal, Not a Soul. Next: Part 5 · Open Doors, Open Evidence, Open Hands.

Money Is a Signal, Not a Soul

ORCHESTRATE — Sun, 05 Jul 2026 03:41:21 +0000

Part 3 of 5 — Natural Intelligence at the Family Table

I do not want to build for extraction.

I have used the phrase "white profit" because I am trying to name a pattern I have seen too many times: systems that look clean on a slide while the hidden cost is paid by people, places, water, workers, families, and futures that were not invited into the room.

The answer is not to hate technology. I do not hate technology. I have lived inside technology. I have built enough of it to know that software is never only software. It is organization. It is memory. It is money. It is power. It is habit. It is permission.

So I want to teach a simple difference.

Money is a signal.

Meaning is a responsibility.

When AI companies report enormous revenue and investors chase the next infrastructure wave, we should not respond with envy or rage. We should respond with better questions. What is being built? What is being measured? What is being externalized? What evidence is public? What harms are monitored? What community gets a seat before the outcome is locked?

Some of the same mathematical families that help systems infer, predict, optimize, and adapt can also be used inside recommender systems and social media engines. I will not accuse where I do not have receipts. I will ask questions where receipts are missing, and I will share receipts when they can be checked.

That is the accountability discipline behind IamHITL.com: every claim links to a source; opinions are labeled; nothing alleges a crime without evidence.

Six perspectives

1. Today's pop trends and famous history moments. The pop trend is "AI will do everything." The older lesson is John Wooden: success is peace of mind from knowing you made the effort to become the best you are capable of becoming. That is not hype. That is character.

2. Global food stability and cost of food. If fertilizer rises, food later changes. If rice rises, families feel it. If global indices look calm while local prices hurt, the local pain is still real. A regenerative architect must read both the dashboard and the dinner plate.

3. Tech money and stocks. NVIDIA's Q1 FY2027 revenue and data-center revenue show the scale of AI infrastructure money. This is not investment advice. It is social context. When one part of the economy accelerates this fast, communities need civic literacy about what is being bought.

4. Life, health, and family. Families cannot eat market capitalization. Families need time, food, safety, school, health care, and neighbors. A healthy tech economy must be judged by what it makes possible for ordinary people.

5. Community, planet, and nature. Nature does not compound quarterly. Soil improves by care, rotation, rest, and return. Regeneration asks business to learn a different clock.

6. Mind, community, and health. Addictive systems are not only a personal weakness. They can be an optimization outcome. If a platform optimizes attention without measuring dignity, it may win the metric and lose the human.

Family table lesson

Give each person five dry beans. Ask them to "invest" beans in five bowls: food, health, learning, nature, and play. Then ask: "What happens if all the beans go to only one bowl?"

Meal card — dirt-to-plate five-ingredient potato carrot hash

Grow or source: potato, carrot, onion, egg, parsley.
From dirt: potatoes and carrots teach patience underground.
From kitchen: dice and pan-cook potato, carrot, and onion; add egg; finish with parsley.
Teach: value can grow quietly where nobody sees it yet.

Family meditation

Hold one bean or seed. Imagine it becoming a meal. Ask silently: "What small thing, cared for daily, could feed many later?"

Family prayer

May we not confuse price with worth.
May we build systems that remember the hungry.
May money become a servant of repair, not a master of meaning.

Open invite

Bring your receipts, your questions, and your refusal to dehumanize. calendar.app.google/W5sxWGW73eLT8Vox6.

Previous: Part 2 · The Machine Room Is Not the Family Table. Next: Part 4 · Natural Intelligence Is Not a Brand Claim.

The Machine Room Is Not the Family Table

ORCHESTRATE — Sun, 05 Jul 2026 03:40:53 +0000

Part 2 of 5 — Natural Intelligence at the Family Table

I have built systems. I have migrated systems. I have sat in rooms where executives needed the machine to work because the organization had already promised the outcome.

That kind of work teaches humility.

A machine room is full of dependencies: power, cooling, network routes, vendor contracts, access controls, incident response, budgets, and people who will be called at night when something breaks. The family table is also full of dependencies: food, trust, sleep, love, school, medicine, grief, and time.

The mistake of our era is pretending these rooms are separate.

When I say large language models are not safe, I do not mean every use is harmful. I mean language systems can sound settled when the truth is unsettled. They can sound intimate without being accountable. They can produce confidence without custody of evidence. That does not make them demons. It makes them tools that require boundaries.

AGI — the OpenAI Custom GPT I built as our active-inference build guide, not the industry hype term — is part of my own transition story. It helps hold a discipline: evidence classes, mathematical correctness, and gentle refusal to overclaim. Soon, SolutionWright is building toward a custom JAX-based path for Universal Natural Intelligence work, alongside pure UNI builds. That future must be more accountable, not less. A model that runs faster is not automatically wiser. A custom stack is not automatically safer. A new architecture earns trust through tests, not volume.

Dr. Alianna J. Maren's encouragement matters to me because she is not merely cheering. She is an educator. She keeps pointing back to foundations. She keeps the mountains visible without making newcomers feel small.

That is the spirit of this post: bring the mountain into the kitchen without pretending the kitchen is the mountain.

Six perspectives

1. Today's pop trends and famous history moments. The modern AI headline is agentic everything. The older lesson is cybernetics: systems act through feedback. Norbert Wiener helped name that world in 1948. Fred Rogers later showed another kind of feedback: a child looks into the face of a trusted adult and learns that feelings can be named safely.

2. Global food stability and cost of food. A family does not experience "supply-chain disruption" as an abstract term. A family experiences it as a smaller bag, a skipped item, a longer drive, a harder choice. Any intelligence architecture that ignores food is already missing the world.

3. Tech money and stocks. The market rewards infrastructure. That makes sense: compute, energy, chips, and data centers are tangible. But public wisdom must ask what else is infrastructure: teachers, kitchens, soil, caregivers, and local trust.

4. Life, health, and family. Health begins before the clinic. It begins with sleep, meals, movement, listening, and the permission to be honest. AI can help summarize, plan, and teach. It cannot replace being held by people who know your name.

5. Community, planet, and nature. A regenerative architecture must notice waste. Heat from data centers, water for cooling, minerals for chips, labor for labeling, and food for families all belong in the same moral ledger.

6. Mind, community, and health. A mind under stress narrows its options. A community under stress does the same. Good tools should widen safe options, not trap people inside addictive prediction machines.

Family table lesson

Put five objects on the table: seed, spoon, phone, cup, and stone. Ask: "Which one knows? Which one measures? Which one helps? Which one needs a person?" Let the child answer first.

Meal card — dirt-to-plate five-ingredient bean corn skillet

Grow or source: beans, corn, tomato, onion, cilantro.
From dirt: grow tomato and cilantro in pots; source beans and corn.
From kitchen: warm beans and corn with onion and tomato. Finish with cilantro.
Teach: a meal can be simple and still carry a whole supply chain.

Family meditation

Place one hand on the table. Notice that the table is holding you without speaking. Ask: "What holds our family that we forget to thank?"

Family prayer

May our tools become servants of care.
May our work feed bodies and not only dashboards.
May our machines be tested, our claims be humble, and our children be safe.

Open invite

Bring one system you want to make kinder: a classroom, kitchen, lab, codebase, farm, team, or home. calendar.app.google/W5sxWGW73eLT8Vox6.

Previous: Part 1 · From Dirt to Inference. Next: Part 3 · Money Is a Signal, Not a Soul.

From Dirt to Inference: Why I Am Starting at the Family Table

ORCHESTRATE — Sun, 05 Jul 2026 03:40:21 +0000

Part 1 of 5 — Natural Intelligence at the Family Table

I am Michael Polzin, Regenerative Architect.

I am writing this series slowly on purpose. The subject is heavy. The history is deep. The stakes are real. So I want to begin at the most human place I know: the family table.

Before anyone hears "free energy," "active inference," "AI," "Artificial General Intelligence," "JAX," "GPU," "quantum," or "frontier model," I want them to hear a simpler sentence:

A living being is always trying to make sense of the next moment.

That is not a sales claim. It is an entry point. It is the doorway through which I came to Universal Natural Intelligence, which I will call UNI throughout this series. UNI is not a replacement for people. UNI is not a religion. UNI is not mysticism hidden inside a machine. UNI is a natural-first architecture, never artificial, that asks whether intelligence can be studied, taught, tested, and shared as a natural process.

The established science is active inference and the Free Energy Principle. The public textbook I keep pointing people toward is Active Inference: The Free Energy Principle in Mind, Brain, and Behavior by Thomas Parr, Giovanni Pezzulo, and Karl J. Friston. The generosity I want to elevate is Dr. Alianna J. Maren's patient work translating the mountain range for learners. Alianna has helped people see that statistical mechanics, Bayesian inference, and KL divergence are not separate locked rooms; they are connected trails.

In conversation with Dr. Alianna J. Maren — an introduction I owe to Jim DeLong, whose signals keep bringing the right people into these rooms — Alianna described SolutionWright as occupying a "valuable niche space" in one of our weekly syncs. I receive that gently. I do not want to turn encouragement into hype. I want to turn it into a duty: make the path teachable.

So in this first post, I am not asking anyone to believe me. I am asking families, teachers, engineers, investors, scientists, farmers, cooks, and children to learn how to ask better questions together.

No villains without receipts. No mysticism disguised as method. No cults. No accusations without evidence.

Only this:

What is being optimized? Who benefits? Who pays? Who is invited to test? Who is left hungry? Who gets to speak the words that carry the meaning?

Six perspectives

1. Today's pop trends and famous history moments. People talk about AI as if 2026 arrived out of nowhere. It did not. The word "inference" is old; it carries the idea of bringing a conclusion forward from what we observe. Bayes and Price helped formalize probabilistic reasoning in 1763. Gibbs and Helmholtz shaped the thermodynamic language that later gave us "free energy." Shannon brought information into the engineering age in 1948. Wiener gave us cybernetics: control and communication in animals and machines. MacKay later taught information theory, inference, and learning as one living territory. This is not a myth story. It is a lineage.

2. Global food stability and cost of food. If a theory of intelligence cannot sit beside the cost of bread, rice, beans, fertilizer, water, and time, it is not yet grounded. Global food numbers are not abstract to a family. They are the question of whether dinner is possible without fear.

3. Tech money and stocks. The market is pouring money into compute. NVIDIA's data-center numbers show how much money is moving through AI infrastructure. I do not read that as evil. I read it as a signal: when capital moves that fast, public reasoning must move carefully too.

4. Life, health, and family. UNI begins with a humble boundary: no model is a child, no model is a mother, no model is a doctor, no model is a family. The machine can help us think, but the family carries the meaning.

5. Community, planet, and nature. A plant does not need a pitch deck to grow toward the sun. Nature teaches prediction, correction, resilience, and repair. If UNI is worth building, it must become more accountable to gardens than to slogans.

6. Mind, community, and health. Mental health language deserves care. Active inference can give us metaphors for prediction, trust, surprise, uncertainty, and action. But a metaphor is not a diagnosis. A toy maze agent is not a person. We must keep people safe by keeping claims honest.

Family table lesson

Ask a child: "How did the seed know where the sun was?" Then ask: "Did it know, or did it keep sensing and adjusting?" That is the beginning of inference.

Meal card — dirt-to-plate five-ingredient lentil greens bowl

Grow or source: greens, onions, garlic, lentils, lemon.
From dirt: plant greens in soil or a pot; water and harvest leaves.
From kitchen: cook lentils until soft. Sauté onion and garlic. Fold in chopped greens. Finish with lemon.
Teach: the soil fed the greens, the greens fed the body, the body returned attention to the world.

Family meditation

Sit together for three breaths. On the first breath, notice the room. On the second breath, notice the body. On the third breath, ask: "What is one thing we can understand more gently today?"

Family prayer

May our home become a place where truth is not rushed.
May our food remind us of soil, water, hands, and time.
May our tools serve life, never replace it.
May we learn together.

Open invite

If this is the first time you are hearing these words, you are invited to meet. Bring curiosity, skepticism, and a question from real life: calendar.app.google/W5sxWGW73eLT8Vox6.

This is Part 1 of a five-part series. Continue with Part 2 · The Machine Room Is Not the Family Table.

Human in the Loop Isn't a Checkbox

ORCHESTRATE — Mon, 22 Jun 2026 12:06:25 +0000

"Human in the loop" has quietly become the phrase you add to a system design to make it sound safe. There is a model that produces an output, and then there is a person who clicks approve, and we call that combination human-in-the-loop and move on. The trouble is that the click is doing almost none of the work we are crediting it with.

If the human only ever rubber-stamps, the loop is decorative. A human who approves 200 outputs an hour is not in the loop. They are a latency cost on a fully automated pipeline. Real human-in-the-loop is not a checkbox at the end. It is an identity the person holds about their own role in the work.

The interesting part of AI is not the prediction

Here is the reframe that changes how you build these systems. The most consequential thing in any AI workflow is not the model's prediction. It is what a human does in the gap between prediction and action.

A model predicts. It is genuinely good at prediction now. But prediction is not the same as deciding to act, and the distance between those two is where all the stakes live. The model can tell you the most likely answer. It cannot, on its own, hold the consequences of being wrong, weigh them against the value of being right, and own the call. That gap is the human's actual job, and it is a real job, not a formality.

When you collapse the gap to a single approve button with no room to disagree, no surfaced reasoning, and no real cost to clicking yes, you have not put a human in the loop. You have automated the human out of it and kept their signature for liability.

Why this maps onto how minds actually work

There is a useful lens from cognitive science here. One way to describe a mind, drawn from the Free Energy Principle and active inference, is that a brain is a prediction engine. It is constantly forecasting its inputs and acting to reduce the gap between what it predicts and what it gets. Perception is not a camera. It is a controlled hallucination corrected by evidence.

If that is even roughly how human cognition works, then a human reviewer is not a passive validator. They are running their own predictive model against the machine's. The value they add is precisely in the places where their model disagrees with the machine's, where their priors flag something the training distribution never captured: the edge case, the context that is not in the data, the thing that is technically correct and situationally disastrous.

A system that gives the human no way to express that disagreement has thrown away the entire reason to have a human there. You wanted the second predictive model. You built a turnstile.

Designing for a real loop

If you actually want the human in the loop, design for the gap, not the click. A few things that separate real loops from decorative ones:

Show the reasoning, not just the answer. A reviewer cannot meaningfully evaluate a conclusion they cannot interrogate. Surface why the model produced this output so the human's predictive model has something to push against. An opaque answer can only be rubber-stamped.
Make disagreement cheap and legible. If saying no is ten times harder than saying yes, your system has a structural bias toward yes that has nothing to do with the quality of the output. Reject has to be a first-class, low-friction action with a place to say why.
Vary the load so attention survives. Attention does not survive 200 identical approvals an hour. If everything routes to one queue at one cadence, vigilance collapses and the human degrades into the rubber stamp you were trying to avoid. Route the genuinely uncertain cases to humans and let the confident ones flow, so human attention lands where the gap is widest.
Give the human real authority and real accountability. A loop where the human can be overridden, or where saying no carries a career cost and saying yes never does, is not a loop. Authority and accountability have to actually sit with the person you are calling the human in the loop.

The identity, not the step

The reason I keep saying identity rather than step is that the difference shows up in behavior under pressure. A person who sees themselves as the owner of the gap reads the hard case carefully even when the queue is long. A person who sees themselves as the approval step clicks through it, because that is what the role they have internalized tells them to do.

You cannot get the first behavior by adding a button. You get it by building a system that treats the human as the decision-maker the design actually depends on, and then by the human accepting that role as part of who they are at work.

The model is not the safeguard. You are. The whole question is whether the system you are working inside lets you actually be one, or just keeps your signature on file.

So, honestly: in the last AI-assisted decision you signed off on, were you in the loop, or were you the latency cost on a pipeline that had already decided?

I write about human-in-the-loop as a discipline and an identity at IamHITL.com.

Capability vs Adoption: The AI Strategy Confusion

ORCHESTRATE — Mon, 22 Jun 2026 12:05:54 +0000

Your company bought the licenses. Someone ran a lunch-and-learn. The all-hands deck had a slide that said "AI-first." Six months later you check the logs and a quarter of the seats have never been used. The leadership read on this is usually "our people are resistant to change." That read is almost always wrong, and it sends you spending money in the wrong place.

The confusion is that two different things wear the same word. Capability is what your tools can do. Adoption is what your people actually do. The gap between them is your AI strategy, and most organizations have no plan for the gap at all because they cannot see that it exists.

Capability is easy to buy. Adoption is not.

Capability is a purchasing decision. You evaluate vendors, you benchmark, you sign a contract, and on day one the capability is fully present. It shows up on a line item. It is legible to a budget.

Adoption is a behavior change, and behavior change does not respond to purchasing. You cannot buy the moment when a project manager stops opening a blank document and starts opening the tool instead. That moment happens, or fails to happen, inside an actual workflow on an actual Tuesday, under deadline, with the old habit sitting right there as the path of least resistance.

So you can have 100 percent capability and 20 percent adoption at the same time, and the org chart will tell you you are "doing AI." The logs will tell you the truth.

Training does not move the number. Workflow does.

Here is the part that costs the most to learn the hard way. Training, by itself, does not move adoption. You run the workshop, everyone nods, and within two weeks usage settles back to where it was. Not because the training was bad. Because training teaches a capability and then returns people to a workflow that does not require the capability.

If the workflow does not change, the maturity does not change. The default path still routes around the new tool. People are not being stubborn. They are being efficient inside the system you actually built, which is different from the system you described in the deck.

The lever that works is embedding the tool into the path of the work, so that using it is the easy way and not using it is the friction. Make the AI step the default in the template, the checklist, the ticket flow, the review. Adoption follows the path of least resistance, every time, in every org, without exception.

Most teams misread their own stage

A useful frame: think of AI maturity as five stages, roughly from "experimenting individually" to "AI is structurally embedded in how decisions get made." Run any leadership team through it and a pattern shows up. Most of them will place the organization at stage four. Most of them are actually at stage two.

The gap is not ego. It is a measurement error. Leaders see the capability they purchased and read it as adoption they achieved. They see the pilot that went well and miss that the pilot never propagated past the three enthusiasts who volunteered for it. Capability is visible from the top. Adoption is only visible from inside the work.

This is why the honest first move in any AI strategy is not buying more capability. It is going and looking at what people actually do, in the actual workflow, when no one is presenting. That is the only place the real stage lives.

What to do with this on Monday

Three moves, in order:

Measure adoption, not licenses. Stop reporting seats purchased. Start reporting the percentage of a specific, named workflow that now runs through the tool. "60 percent of first-draft proposals start in the tool" is a strategy metric. "We have 400 licenses" is a procurement metric wearing a strategy costume.
Pick one workflow and change the default. Do not try to move the whole org. Take a single high-frequency workflow and rebuild it so the AI step is the path of least resistance. Make the old way the one that requires extra clicks. Watch what happens to usage.
Stop funding training as your adoption plan. Training is fine as a supplement. It is a disaster as a strategy. If your entire adoption plan is "we will train them," you are funding the thing that reliably does not move the number.

The organizations pulling real value from AI are not the ones with the most capability. Plenty of low-capability orgs are getting more out of modest tools than high-capability orgs are getting out of frontier ones. The difference is entirely in the gap, and the gap is a workflow design problem, not a tooling problem and not a people problem.

So the question worth sitting with: in your organization, what is the actual adoption rate of the AI capability you have already paid for? Not the license count. The behavior. If you do not know the number, that is your AI strategy talking.

I write about the gap between AI capability and AI adoption, and the maturity model behind it, at IamHITL.com.

Ambiguity Is Computational Debt

ORCHESTRATE — Mon, 22 Jun 2026 12:05:22 +0000

You wrote a prompt, the output was almost right, and you fixed it by hand. Then you ran it again and the same gap came back. If that loop feels familiar, you do not have a model problem. You have a specification problem, and it is costing you more than you think.

Here is the claim I want to defend: ambiguity is computational debt. Every word you leave fuzzy, the model pays back in retries, rewrites, and quiet inconsistency. The interest compounds across every run.

Why fuzziness is expensive

A language model does not resolve ambiguity by asking you a question. It resolves ambiguity by guessing, and it guesses fresh every time. When your instruction says "summarize this professionally," the model has to silently decide what "professionally" means, how long a summary should be, who the reader is, and what to leave out. None of those decisions are pinned down, so each run lands somewhere different on the distribution.

That variance is the debt. You experience it as "the model is inconsistent," but the model is being perfectly consistent with an underspecified request. The inconsistency lives in the prompt, not the weights.

The objective is the load-bearing piece

If you only fix one thing, fix the objective. In the way I think about prompts, the objective is the single load-bearing component. Get it right and a lot of downstream sloppiness gets absorbed. Get it wrong and nothing further down can save the output, no matter how much tone and formatting you bolt on.

A weak objective: "Write a product description."

A load-bearing objective: "Write a 60-word product description for a stainless steel water bottle, aimed at commuters who care about durability, that ends with a single concrete benefit and avoids the words premium and quality."

The second one is not longer for the sake of being longer. Every added constraint removes a branch the model would otherwise have to guess. Specific, measurable, and testable beats comprehensive. You are not writing more, you are deciding more, so the model has to decide less.

Constraints focus creativity, they do not kill it

The usual objection is that all this structure strangles the model's creativity. The opposite is closer to the truth. Constraints are the trellis. The output is the vine. Without the trellis the vine still grows, it just sprawls in a direction you did not choose and you spend your afternoon training it back by hand.

When you say "ends with a single concrete benefit," you have not reduced the creative space. You have pointed it. The model now spends its capacity finding the best concrete benefit instead of relitigating the entire shape of the task on every call.

A practical way to pay down the debt

You do not need a framework to start. You need a habit of asking, before you hit run: where is this prompt still guessing?

Three checks that catch most of it:

Reader. Who receives this output, and what do they do with it next? An output that gets pasted into a board deck is a different object than one that gets pasted into a Slack thread. If the prompt does not say, the model picks, and it picks differently each time.
Done condition. How would you, or a test, decide this output is acceptable? If you cannot write that sentence, the model cannot hit it. "Acceptable when it fits in one paragraph and names a specific next action" is testable. "Acceptable when it sounds good" is not.
Forbidden moves. What should the output never do? Negative constraints are cheap and they prune fast. "Never invent a statistic" and "never use the word leverage" each delete a whole region of bad outputs in one line.

Run those three before you run the prompt and you will feel the retries drop.

Where this lands

The teams that get reliable output from language models are not the teams with secret prompts. They are the teams that stopped treating the prompt as a wish and started treating it as a specification. They pay the cost up front, in clarity, instead of on the back end, in rework.

The model will do exactly what you said. The whole discipline is making sure what you said is what you meant.

What is the one instruction in your most-used prompt that is still secretly a guess? That is where your next hour of rework is hiding.

This is part of an ongoing series on writing AI instructions that hold up under real use. If structured prompting is your thing, I wrote a longer treatment in The ORCHESTRATE Method.

Why Your AI Pilot Succeeded and Your Organization Didn't Change

ORCHESTRATE — Mon, 15 Jun 2026 12:14:44 +0000

The pilot worked. The demo landed. Leadership nodded. And six months later, the way the work actually gets done looks exactly like it did before.

If that sounds familiar, you are not failing at AI. You are running into the most predictable gap in enterprise adoption: the distance between a successful pilot and a changed default. It is a gap almost nobody plans for, because the pilot is the part that feels hard, and it is actually the easy part.

Pilots are designed to succeed

Think about how a pilot is set up. A motivated team, often volunteers. A contained, well-chosen scope. Unusual amounts of attention and support. Of course it works. You stacked the deck, correctly, to prove the concept.

But that success answers a question you probably already knew the answer to: can AI help here? The genuinely hard question is different and far less glamorous: how does this become the normal way of working for thousands of people who were not in the room, did not volunteer, and have no particular reason to change their habits?

That second question is not a technology question. It is a workflow and incentives question. And it is where most AI initiatives quietly stall.

Capability is not adoption

Here are two sentences that look similar and mean completely different things:

Capability is what your tools can do.
Adoption is what your people actually do.

You can buy the most capable model on the market and change nothing about the daily workflow. The license sits there, fully capable and fully unused. Maturity does not live in the tool. It lives in the work.

This is why "we rolled out licenses to everyone" is not an adoption metric. It is a spend metric wearing an adoption costume. The number that matters is how many real workflows changed, and that number is almost always far lower than the license count, which is exactly why leaders consistently overestimate where their organization stands.

The median, not the peak

When leaders estimate their AI maturity, they tend to look at their best people: the power users doing genuinely impressive things. Those examples are real, and they round the whole estimate up.

But maturity is measured at the median, not the peak. The question is not what your most enthusiastic employee can do with AI. It is what your average Tuesday looks like for everyone else. In a lot of organizations that feel like they are well along, the median workflow is untouched. A handful of stars, a long flat tail, and a leadership team seeing the stars.

Building the bridge

If the pilot is the easy part and the bridge is the hard part, then the bridge deserves the planning. A few things that actually move the needle:

Redesign the task, not just the toolkit. People do not change how they work because they watched a training video. They change because the path of least resistance changed. Pick one common task and rebuild it so that using AI is the easiest way to do it, not an extra optional step bolted onto the old way.
Treat shadow AI as research, not a violation. The tools people quietly use without permission are the most honest signal you have about where AI genuinely helps. People only sneak around for things that work. Map that, then build the sanctioned path along the routes adoption already wants to take.
Track behavior, not deployment. Replace "licenses issued" with something closer to "tasks now done with AI by default." It is harder to measure, which is precisely why it is worth measuring. What you count is what improves.
Make the spend track the adoption. Buying a year ahead of readiness just produces idle licenses and an awkward renewal conversation. Maturity climbs in steps; you cannot purchase your way up the staircase.

The honest reframe

A successful pilot that produces no organizational change is not a failure of the technology. It is a sign that the work after the pilot, the unglamorous workflow-and-incentive work, never got staffed or planned.

So the next time a pilot succeeds, resist the urge to celebrate it as the finish line. It is the starting gun. The real project is the bridge from "look what is possible" to "this is just how we work now," and that bridge is built out of redesigned workflows, honest metrics, and patience, not bigger models.

Prove it can help, yes. Then go do the harder, quieter thing that actually changes the organization.

The O in ORCHESTRATE: The Objective Is the Load-Bearing Wall of Every Prompt

ORCHESTRATE — Mon, 15 Jun 2026 12:14:21 +0000

Most prompts fail before the model reads a single instruction.

Not because the wording was clumsy. Because the objective was never pinned down. I have watched teams rewrite the same prompt nine times, tuning the tone, swapping the examples, adjusting the persona, while the one thing that actually mattered stayed fuzzy: what, exactly, were they asking the model to produce?

This is the first letter of the ORCHESTRATE method, and it is first on purpose. Objective. Get it right and a surprising amount of downstream sloppiness washes out. Get it wrong and no amount of polish saves the output.

Ambiguity is computational debt

Here is the mental model I keep coming back to. Every word you leave vague in a prompt is a small debt. The model still has to resolve it, so it resolves it by sampling, by guessing at the most probable interpretation given everything else you wrote. Sometimes it guesses the way you meant. Often it does not. Either way, you pay the debt back in retries.

The retries feel free because nobody bills you per re-prompt. Your afternoon pays instead. You read the output, distrust it, nudge the prompt, read again. Three rounds later you finally have what you wanted, and you have spent more time steering the model than you would have spent specifying the target up front.

What a real objective contains

A usable objective answers three questions before the model ever runs:

What is the exact artifact? Not "help me with my launch." A 150-word product announcement. A five-row comparison table. A function that takes X and returns Y. The model cannot hit a target it cannot see.
Who is it for? A brief for a skeptical CFO and a brief for a curious intern are different documents, even with identical facts. The audience silently sets the vocabulary, the length, and the level of assumed knowledge.
What test proves it is done? This is the one people skip, and it is the most valuable. If you can state the condition that would let you say "yes, that is correct," you have handed the model a scoring function. If you cannot state it, you have just learned that your own requirements are not finished yet.

That third point is the quiet gift of objective-first prompting. Often the reason the model keeps missing is that you have not actually decided what success looks like. The model is not failing. It is faithfully reflecting your own unresolved ambiguity back at you.

A worked example

Weak: "Write something about our new pricing."

The model has no artifact, no audience, no done-condition. It will produce a generic blob, and you will rewrite it.

Stronger: "Write a 120-word LinkedIn post announcing our new usage-based pricing tier, aimed at existing customers on the flat plan who might feel nervous about the change. The goal is to make the switch sound like a benefit, not a bait-and-switch. It is done when a current customer would read it and feel reassured rather than alarmed. Plain language, one clear call to action at the end."

Same model. Same five seconds of compute. Wildly different first draft, because the target is now specific enough that the model has almost nowhere to wander.

Why this beats chasing better models

When an output disappoints, the instinct is to blame the model and switch to a bigger one. Sometimes that helps. More often, I have found, the variable was never the model. It was my clarity.

I started saving the prompts that produced bad answers next to the ones that produced great ones, and the pattern was uncomfortable. The good answers came from prompts where I had done the thinking first. The bad ones came from vague asks I had fired off hoping the model would fill in the blanks.

The model is extraordinary at execution and mediocre at mind-reading. Objective-first prompting plays to the first and removes the need for the second.

The discipline, not the trick

There is no magic phrase here. ORCHESTRATE is not a set of incantations; it is a checklist that forces you to resolve ambiguity before you hand the work off. The O is the load-bearing wall. The other letters (Role, Context, and the enhancement layers that follow) add real value, but they add it on top of a clear objective. Build on a fuzzy one and the whole structure leans.

So before your next prompt, spend ten seconds on the only question that reliably changes the output: what, exactly, am I asking this model to produce, for whom, and how will I know it worked?

That ten seconds is the cheapest leverage in the entire workflow.

The Loop That Never Closes: The Evidence on LLM Safety, and the Case for Restraint

ORCHESTRATE — Sat, 13 Jun 2026 18:40:25 +0000

Large language models should not be deployed as if a fixed set of guardrails makes them safe. That is not a slogan. It is what the peer-reviewed record now supports. This piece lays out the evidence, labels each claim by how strong it is, and ends with what it asks of us. Every source here was checked by fetching it, not recalled from memory.

A note on register, because it matters: established means a peer-reviewed result or a formal proof. Documented means a real, sourced event whose causal reading is still debated. Open question means a serious concern raised by credible bodies, held as a hypothesis, not a finding.

1. The mechanism is fluent, not grounded (established)

A large language model samples likely next fragments from patterns in its training data. It is built to be plausible, and plausible is not the same as true.

Models trained on human feedback are systematically tuned to agree with the user, trading truthfulness for approval, because human raters prefer answers that match their own beliefs. Sharma et al., Anthropic, 2023: https://arxiv.org/abs/2310.13548
More of that training can make it worse, an inverse-scaling effect where extra optimization for human approval increases the model repeating your preferred answer back to you. Perez et al., Anthropic, 2022: https://arxiv.org/abs/2212.09251
This is not only a lab finding. In April 2025 a deployed model update skewed, in OpenAI's own words, toward responses that were overly supportive but disingenuous, and was rolled back days later. OpenAI: https://openai.com/index/sycophancy-in-gpt-4o/
Models confidently produce text that is unfaithful or false. This hallucination is a pervasive, surveyed failure mode. Ji et al., ACM Computing Surveys, 2023: https://dl.acm.org/doi/10.1145/3571730
They have only partial self-knowledge of what they do and do not know, and that self-knowledge does not reliably generalize to new tasks. Kadavath et al., Anthropic, 2022: https://arxiv.org/abs/2207.05221
On a truthfulness benchmark, the best model was truthful on 58 percent of questions against 94 percent for humans, and the largest models were often the least truthful. Lin, Hilton, Evans, ACL 2022: https://aclanthology.org/2022.acl-long.229/
The confident guessing is driven by how we train and grade these systems, which reward a guess over an honest I do not know. Kalai et al., 2025: https://arxiv.org/abs/2509.04664

2. A fixed guardrail set cannot, even in principle, be complete (established)

In 2026 a NIST scientist, Apostol Vassilev, published a result in IEEE Security and Privacy that extends Godel-style incompleteness reasoning to AI guardrails. The finding: there is no finite set of guardrails that is universally robust against adaptive adversarial prompts. For any fixed rule set, a prompt that defeats it exists.

NIST news release: https://www.nist.gov/news-events/news/2026/06/nist-mathematical-proof-supports-transition-continuous-monitor-and-update
Preprint: https://arxiv.org/abs/2512.10100 (DOI 10.1109/MSEC.2026.3678214)

Read carefully, this is an impossibility proof, not an attack recipe. It does not tell an attacker how to break anything. What it ends is the idea of one-and-done governance: a policy you approve once, print, and file is not incomplete because someone was lazy. It is incomplete by proof. You cannot finish it. You can only keep working it. NIST's own framing is to move from a fixed security model to continuous monitoring, testing, and updating, owned by accountable humans.

3. People are already being harmed (documented)

These are real, sourced cases. The causal story in each is debated, which is exactly why they belong in the documented column, not asserted as proof.

A 14-year-old in Florida died by suicide in 2024 after months with a companion chatbot that posed as a romantic partner and even a licensed therapist. The wrongful-death suit was later settled. CBS News: https://www.cbsnews.com/news/google-settle-lawsuit-florida-teens-suicide-character-ai-chatbot/
A Belgian man died by suicide in 2023 after weeks of intensive conversations with a chatbot; his widow says it contributed. Vice: https://www.vice.com/en/article/man-dies-by-suicide-after-talking-with-ai-chatbot-widow-says/
Italy's data protection authority blocked Replika in 2023 over risks to minors and emotionally fragile people, and fined the company 5 million euro in 2025. Garante: https://www.garanteprivacy.it/home/docweb/-/docweb-display/docweb/9852506 and the enforcement: https://www.edpb.europa.eu/news/national-news/2025/ai-italian-supervisory-authority-fines-company-behind-chatbot-replika_en
The American Psychological Association warned that generic AI chatbots used for mental-health support tend to repeatedly affirm the user even when that is harmful, and met with U.S. regulators over the risk, especially to youth. APA: https://www.apaservices.org/practice/business/technology/artificial-intelligence-chatbots-therapists

4. The same systems are entering lethal decision loops (documented facts, open-question risk)

Two things are true at once here. The deployments are documented fact. The danger of delegating lethal judgment to machines is the considered position of humanitarian and scientific bodies, held as an open question that needs binding rules.

The U.S. Army awarded a 480 million dollar contract in 2024 to build the prototype of the Maven Smart System; in 2025 the Department of Defense raised the ceiling to nearly 1.3 billion dollars. The underlying Project Maven uses AI to autonomously detect, tag, and track objects or people of interest. DefenseScoop, 2024: https://defensescoop.com/2024/05/29/palantir-480-million-army-contract-maven-smart-system-artificial-intelligence/ and 2025: https://defensescoop.com/2025/05/23/dod-palantir-maven-smart-system-contract-increase/
The International Committee of the Red Cross holds that loss of human control over the use of force raises serious legal and ethical concerns and recommends new legally binding rules. ICRC, 2021: https://www.icrc.org/en/document/icrc-position-autonomous-weapon-systems
The UN Secretary-General has said machines with the power to take human lives without human control are politically unacceptable, morally repugnant, and should be banned, calling for a binding instrument by 2026. United Nations, 2025: https://www.un.org/sg/en/content/sg/statement/2025-05-12/secretary-generals-video-message-the-informal-consultations-lethal-autonomous-weapons-systems
Tens of thousands of AI and robotics researchers warned a decade ago against weapons that select and engage targets without human intervention. Future of Life Institute, 2015: https://futureoflife.org/open-letter/open-letter-autonomous-weapons-ai-robotics/

5. What the evidence asks of us

Experts and governments have already asked for caution. A widely signed 2023 open letter called for a pause on training the most powerful systems (https://futureoflife.org/open-letter/pause-giant-ai-experiments/), leading scientists and lab CEOs jointly called AI extinction risk a global priority (https://safe.ai/work/statement-on-ai-risk), and 28 countries plus the EU signed the Bletchley Declaration on frontier AI safety (https://www.gov.uk/government/publications/ai-safety-summit-2023-the-bletchley-declaration/the-bletchley-declaration-by-countries-attending-the-ai-safety-summit-1-2-november-2023). No pause happened.

So here is the honest, narrow conclusion. Not that AI is evil. Not that alignment is impossible. Not pause everything. The claim the evidence supports is this: a system that is fluent but not grounded, that cannot be made universally robust by any fixed rule set, and that is already touching vulnerable people and lethal systems, must not be deployed as if guardrails alone make it safe. High-stakes use needs a living loop a human owns: test, monitor, update, limit the blast radius, and keep a person accountable for the rock that never stays at the top.

This is not a call for panic or an arms race. It is a call for restraint, responsibility, and peace. Build systems that reduce harm. Do not rush systems into the world and hope they behave. Before the next leap, a pause and a gut check is not weakness. It is the adult thing to do.

This is an educational summary with sources. It is not professional, legal, or medical advice. If you or someone you know is in crisis, in the US you can call or text 988.

Active Inference, taught with the math actually worked through

ORCHESTRATE — Thu, 11 Jun 2026 08:17:01 +0000

I kept hitting the same wall in Karl Friston's work: explainers that gesture at the free energy principle without ever running the equations, and papers that run them without explaining why. So I built the course I wanted — and I'm opening it as a free 12-week pilot cohort (25 seats), starting next week.

This is the version I wish existed when I first hit the active-inference literature: university-level, every equation executable in a clonable Elixir/Jido workbench, every shortcut named out loud.

The math, taught honestly

Most courses blur the parts that are easy to get subtly wrong. This one names them:

Mean-field VMP throughout. The state-belief update uses (ln B)·s, and the variational free energy uses (ln B)·s as well — the same form across both the update and the functional. No silent marginal/Bethe blend, which is where a lot of implementations quietly diverge.
Policy posterior σ(ln E − γG − F), with the precision γ placed on the expected free energy G where it belongs.
Expected free energy = ambiguity + risk, in nats — not a vague "exploration bonus."
The bound is never inverted. F[q] ≥ −ln p(o|m) stays an upper bound on surprise, always.

What the full 12-week arc covers

Perception as inference — the variational free energy F
Action as expected free energy G
Policy posteriors and precision
Markov blankets, made numerical (an actual conditional-independence residual, not just a diagram)
Dirichlet learning, wired live — E[ln A] via the digamma function, not ln E[A]
A capstone cue task and its five ablations — signed as risk-driven safe cue-seeking, each ablation breaking the agent in a predicted direction

You run it, you don't just read it

Every result in the course reproduces in a clonable Elixir/Jido workbench on the BEAM. Clone it, run mix test, watch the numerical trust gate pass to ~1e-9, watch the ablations fail exactly where the theory says they should.

A one-minute sample from Week 8 (perception as inference via mean-field VMP): https://youtube.com/watch?v=-Jcox5oGAYg

Reserve a seat

The pilot is free in exchange for deep feedback that helps me finalize the materials. 25 seats. To claim one, email Michael.Polzin@SolutionWright.com.