Edition 001 // JAN 22, 2026

Edition 001

Human Agency in an Evolving Agentic World

01 // The Signal

The Illusion of Lost Control

Four diagnostic questions revealing where you're gaining control vs. creating dependency in an agentic world.

If you're experiencing a low-grade sense that control is slipping through your fingers, you're not imagining things.

Every time you delegate a decision to an AI that you used to make yourself. Every time you automate judgment you used to exercise manually. You feel it—a subtle erosion of agency, dressed up as efficiency.

The disorientation runs deeper than productivity anxiety. It's the creeping realization that the very mechanisms you're adopting to enhance control may be systematically redistributing it away from you. To vendors. To platforms. To systems you don't fully understand and can't audit.

Most people respond by either resisting adoption entirely or embracing it uncritically. Both miss what's actually happening. The pattern isn't "adopt or resist"—it's understanding where control shifts, why it matters, and how to maintain agency when your tools become agents.

The Control Framework

Control in an agentic world operates across four dimensions. These questions reveal exactly where your agency is expanding and where it's contracting.

Question 1: Who owns the execution layer?

When an AI executes work on your behalf, who controls the infrastructure, data, and decision logic?

What this reveals:

Own the execution layer (self-hosted, internal systems) = structural control maintained
Vendor owns it (SaaS, API dependencies) = control traded for convenience
The more critical the work, the more ownership matters

Look for: Whether you can export, audit, or migrate without losing capability.

Question 2: Where does judgment actually reside?

Distinguish between delegation and abdication. Are you delegating execution while retaining judgment, or abdicating decision-making authority itself?

What this reveals:

Delegation preserves control: you review, approve, own outcomes
Abdication surrenders control: system decides, you accept outputs
The transition often happens gradually and invisibly

Look for: Whether you're asked to review decisions or merely notified of them.

Question 3: What dependencies are you creating?

Some dependencies strengthen your position (learning skills, building knowledge). Others weaken it (platform lock-in, opaque algorithms, proprietary formats).

What this reveals:

Strengthening: you become more capable independent of the vendor
Weakening: you become more dependent, knowledge stays with vendor
Your dependency pattern determines long-term agency trajectory

Look for: Whether capability increases independent of the vendor or only through them.

Question 4: What's your fallback position?

If the system fails or the vendor changes terms, can you continue the work?

What this reveals:

Strong fallback: you retain skills, data, and processes to continue independently
Weak fallback: unable to operate without specific tool or platform
No fallback: capability itself becomes inaccessible

Look for: Whether you're building resilience or single-point vulnerability.

Application: The Writing Team

A marketing team adopts AI writing tools. Productivity increases 300%. Output quality remains high. Management is pleased.

Six months later:

Execution ownership: The vendor owns models and infrastructure. When the vendor updates their model, output style shifts. The team has optimized for vendor-specific patterns, not writing itself.

Judgment location: Initially, writers reviewed carefully. But as trust built and deadlines compressed, reviews became cursory. The transition from delegation to abdication happened gradually. Writers became editors of AI output rather than authors using AI tools.

Dependencies created: Junior writers never developed foundational skills—structuring arguments, developing voice. Senior writers' skills atrophied through disuse. The team's capability became inseparable from the vendor's platform.

Fallback position: Weak. If the vendor disappeared, productivity would drop 70% and quality would suffer as rusty skills ramped back up. Junior writers, who never developed base competencies, would struggle significantly.

Pattern revealed: What looked like enhanced control (faster output, higher productivity) actually created systematic vulnerability. The team traded agency for throughput.

Assessment: Where Do You Stand?

Assess your three most critical AI-dependent tools against these risk profiles.

High Risk: Control loss is happening now

Don't own execution layers for critical work
Judgment transferring to systems without explicit approval
Dependencies weakening your independent capability
Weak or no fallback positions

Medium Risk: Manageable vulnerability

Own most critical execution layers
Judgment clearly remains with you
Dependencies primarily strengthening capability
Fallback positions maintained and exercised

Self-Assessment Questions

For each critical tool:

Can you export all data in usable formats?
When did you last override an AI recommendation?
Are your skills improving through AI use or atrophying?
Could you perform this work manually if needed?

If you answered "no" to most questions, you're experiencing systematic control loss.

Actions: What To Do This Week

High Risk: Urgent intervention

Audit Your Critical Stack (2 hours)

List every tool handling critical decisions or execution
Answer the four framework questions for each
Identify greatest control vulnerability

Test One Fallback (3 hours)

Choose one AI-automated task
Run it manually for the week
If you struggle with quality (not just speed), capability has eroded

Restore Active Judgment (ongoing)

For one AI-dependent process, review the last 10 decisions
If you overrode fewer than 2-3 recommendations, judgment is transferring
Establish explicit review criteria

Medium Risk: Maintain position

Document What's Working (1 hour)

Write down why you're maintaining control better than most
This becomes your playbook as pressure to automate increases

Strengthen Your Weakest Link (ongoing)

Identify your most vulnerable control dimension
Shore it up: practice fallback capabilities, audit execution ownership

Test Override Authority (this week)

Deliberately override one AI recommendation
Explain reasoning to your team
Model that authority means taking responsibility for decisions

From Anxiety to Agency

The anxiety you felt at the beginning—the sense that control is slipping—was accurate. It is slipping. For many people. In many contexts. Often invisibly.

But you now have a framework for understanding exactly where and why. The four diagnostic questions aren't abstract philosophy—they're practical tools for auditing your agency before it becomes irreversible.

The pattern is clear: Tools that increase efficiency don't automatically increase control. Often, they trade one for the other.

You have clarity now about what control means in an agentic world, how to assess your position honestly, and what specific actions restore and preserve agency.

The low-grade anxiety transforms into precise diagnosis. You can see what's happening. You understand the trade-offs. You know what to do about it.

This is the difference between anxiety and agency.

02 // Domains

BUSINESS

The Dependency Trap

Where organizational capability actually resides and why "the system will handle that" signals dependency, not efficiency.

Your competition is moving faster. Producing more with fewer people. Every earnings call reinforces the message: adopt AI aggressively or fall behind.

But something feels off. Your team asks fewer questions. Junior employees aren't developing skills. Institutional knowledge is dispersing—not failing catastrophically, just slowly migrating from people to platforms.

You've heard yourself say "the system will handle that" more this quarter than all of last year.

The Hidden Restructuring

Here's what's actually happening: You're not just adopting tools. You're restructuring authority.

When your sales team uses AI for lead prioritization, and the algorithm changes how it ranks prospects, your team can't explain why their pipeline shifted. They were optimizing for the vendor's black box, and the box changed.

When your customer service team uses AI for increasingly complex interactions, service reps stop developing problem-solving skills. When complex cases arise that AI can't handle, they struggle—they've lost practice with judgment-intensive work.

The critical question isn't "Are we using AI effectively?" It's "Where does organizational capability actually reside?"

If the answer is increasingly "in our vendors' platforms," you're not building competitive advantage. You're building dependency.

This Week's Action

Conduct a judgment audit. Pick one AI-assisted decision process. Review the last 10 decisions: how many times did your team override AI recommendations?

If it's fewer than 2-3 times, judgment has transferred from your people to the algorithm.

Establish explicit review protocols:

Define what you're evaluating and why
Make criteria explicit
Make rejection as easy as acceptance

FAMILY

The Formation Crisis

Children learning algorithmic optimization as baseline. What you're modeling about agency, judgment, and who's in charge.

Your household technology is increasingly agentic. Smart home systems. Calendar apps coordinating schedules. Educational apps adapting to learning pace. Each promises to reduce mental load and create quality time.

And they deliver—the house is more comfortable, schedules coordinate smoothly, kids learn effectively.

But your children are learning something else too: that algorithms make better decisions than people.

They defer to apps for choices they used to make themselves. "The app says I should do this next." Your teenagers trust AI recommendations without questioning underlying logic. Your younger kids expect everything to be personalized, adaptive, optimized—and show frustration when human interactions don't match algorithmic responsiveness.

The Formation Question

Here's what matters: Your children aren't experiencing a transition from human agency to algorithmic optimization—they're experiencing algorithmic optimization as the baseline.

The patterns you're choosing to adopt are the patterns they're learning as foundational.

When family schedules optimize automatically and everyone adapts to system logic, what are your kids learning about who's in charge? When entertainment consumption is algorithmically curated without intervention, what are they learning about judgment and curation?

They're learning that optimization is the goal, algorithmic direction is normal, and human judgment is secondary to system efficiency.

The Capability Transfer

Your family uses an AI home manager that coordinates everything automatically. Kids never learn to manage their time, negotiate shared resources, or coordinate with family members—the system does it for them.

If it disappeared, basic household coordination would collapse. Not because of complexity, but because the skills were never developed.

Strong families in 2026 won't be the ones with the best technology. They'll be the ones who maintained agency through technology adoption.

This Week's Action

Implement one manual day. Choose one day this week where the family makes key decisions without algorithmic assistance.

Practice these without digital assistance:

Manual schedule coordination instead of app management
Manual entertainment selection instead of algorithmic recommendations
Manual task coordination instead of smart automation

Observe what's difficult—that reveals where capability has eroded.

Make this positive, not punitive: "Today we're practicing being in charge of our own schedule."

FAITH

Conviction vs. Convention

Exercising dominion through technology adoption or practicing abdication with theological language. The contradiction becomes visible.

Theologically, you believe humans are made in God's image—creative, responsible, authoritative agents called to exercise dominion. You believe faithful stewardship means taking responsibility for outcomes.

But in practice, you're adopting technologies that systematically redistribute agency away from humans.

The tension is sharp: your convictions say human agency matters supremely. Your context says algorithmic optimization delivers superior results.

Most people compartmentalize—maintaining theological convictions about human nature while adopting technologies that contradict those convictions in practice.

Eventually, the contradiction becomes visible: either your theological convictions about human agency shape how you adopt technology, or they're abstract beliefs disconnected from practice.

The Dominion Mandate

"Then God said, 'Let us make mankind in our image, in our likeness, so that they may rule... Be fruitful and increase in number; fill the earth and subdue it." (Genesis 1:26, 28)

This is foundational: humans are called to exercise dominion. Not domination (exploitation), but dominion (responsible rule). The mandate is to subdue—bring order, cultivate, shape the environment toward flourishing.

You can't "rule over" what you don't understand. You can't "subdue" through passivity. You can't exercise dominion by deferring to algorithmic optimization.

The question becomes: are your technology choices consistent with exercising dominion, or are they patterns of abdication?

Joseph's Pattern: Preparation During Abundance

"Seven years of great abundance are coming... but seven years of famine will follow them. Let Pharaoh appoint commissioners to take a fifth of the harvest during the seven years of abundance." (Genesis 41:29-34)

Joseph's wisdom: act on what you know to be true before metrics force you to. Prepare during abundance, when preparation costs less.

You're in a period of abundance. AI tools work. Efficiency gains are real. This is precisely when you should be building fallback capabilities, auditing control positions, establishing practices that will serve you when conditions change.

Faithful stewardship means maintaining the agency to actually steward. If you've ceded judgment to algorithms, you're not stewarding—you're burying your talent.

This Week's Action

Articulate one authority boundary. Identify one area where human judgment must remain primary in your ministry or spiritual practice.

Communicate why it matters theologically:

"We maintain human oversight here because formation happens through presence, not optimization"
When ministry technology decisions arise, explicitly reference theological convictions
"We're choosing this because it preserves human judgment in relationships"

Demonstrate that conviction trumps convention, even efficient convention.

Integration: The Same Conviction

The pattern is identical across all three domains:

Business: Are we building organizational capability or vendor dependence?

Family: Are we developing children's agency or algorithmic dependence?

Faith: Are we exercising faithful stewardship or optimizing efficiency?

All three reduce to one question: Will we maintain meaningful human agency in an increasingly algorithmic world?

The conviction that drives business restructuring around preserved agency should enable family boundary-setting around the same principle. The theological conviction about human dignity should shape both career decisions and children's formation.

This is integrated living: one framework, applied faithfully across every context where you exercise leadership.

Weekly Actions

You don't maintain agency through one dramatic decision. You maintain it through consistent practices across all domains.

This Week in Business: Conduct one judgment audit. If your team overrode fewer than 2-3 AI recommendations in the last 10 decisions, judgment is transferring. Establish review protocols.

This Week in Family: Implement one manual day. Make key family decisions without algorithmic assistance. Observe what's difficult—that reveals where capability has eroded.

This Week in Faith: Articulate one authority boundary. Identify where human judgment must remain primary. Communicate why it matters theologically, not just practically.

These aren't separate initiatives. They're three expressions of one commitment: to maintain meaningful agency in every domain of life.

Small actions compound. Across all three domains. Starting this week.

03 // Op-Ed

Shaping What Could Be

Control through power and position—but whose? God's subdue mandate means breakthrough beyond your capacity, not only fauthfulness within it.

Control is viewed differently from person to person.

What I believe is that control is correlated to two things: power and position. Where there is more power and authority in position, the ability to control increases accordingly.

The question becomes: how do we control what is not in our total power and position to do so?

The Subdue Mandate

"Then God said, 'Let us make mankind in our image, in our likeness, so that they may rule... Be fruitful and increase in number; fill the earth and subdue it." (Genesis 1:26, 28)

God's command to Adam wasn't suggestion—it was mandate. Subdue the world. Exercise dominion. Shape creation toward flourishing.

This is the answer: the power and position available to us extends beyond what we possess independently. It includes what God makes available through faith.

When you exercise control by faith, you're accessing divine authority to shape reality beyond your natural capacity.

Living Beyond Yourself

The frameworks revealed where control resides and how to maintain agency. But the deeper question is: control toward what end?

Preserving agency for autonomous self-sufficiency is one answer. Exercising dominion as faithful stewardship under God's sovereignty is another.

The first leads to optimization within existing capacity. The second leads to breakthrough beyond imagination.

Control by faith can lead to a reality beyond what you could have thought possible had you not ventured out in faith.

Because of God's power and position available to us, we should pursue shaping the world at every level.

This is the architecture of authority: human agency exercised through divine empowerment.

Not control despite dependence on God, but control through it.

That's the difference between managing what exists and subduing what could be.