---
id: "concept-automation-boundary"
type: "concept"
source_timestamps: ["01:28:20"]
tags: ["productivity", "workflow-design", "human-computer-interaction"]
related: ["action-audit-automation-boundary", "framework-3-levels-of-ai-fluency", "entity-igor-pogany"]
definition: "A personal threshold defining which tasks should be outsourced to AI and which should be kept for human joy and fulfillment."
---
# The Automation Boundary

## Definition
A personal threshold defining which tasks should be outsourced to AI and which should be kept for human joy and fulfillment.

## Origin
Introduced by [[entity-igor-pogany]].

## Core Idea
Just because AI *can* automate a task doesn't mean it *should*. Individuals must explicitly decide what brings them joy, fulfillment, or human connection, and protect those activities from automation. Conversely, tasks that drain energy or are purely administrative should be pushed across the boundary to AI agents (see [[concept-agentic-ai]]).

Defining this boundary prevents the dystopian outcome of automating away the parts of life that make it worth living.

## Practical Application
The explicit exercise is captured in [[action-audit-automation-boundary]]: list every recurring task and assign it either *Keep (joy/connection/fulfillment)* or *Delegate (drain/admin/repetition)*.

## Adjacent Literature
Philosophically aligned with Cal Newport's *Deep Work* (joy audits) and Greg McKeown's *Essentialism* (joy-preserving delegation). Emerging surveys note "automation regret" cases — creative burnout when joy work is over-delegated.

## Connected Notes
- Action: [[action-audit-automation-boundary]]
- Maturity context: [[framework-3-levels-of-ai-fluency]]
- Related strategy: [[claim-tool-fatigue]]