Agency and Automation

Short definition

A cross-project design lens for distinguishing helpful automation from loss of agency by asking which burdens can be removed while preserving meaningful ways to participate, delegate, refuse, inspect, contest, recover, and change course.

Its provisional shorthand is:

Automate necessity. Preserve possibility.

The phrase is not a rule that all necessary work should be automated or that manual participation is inherently better. The canonical treatment instead distinguishes unwanted friction, chosen effort, protective pauses, bounded delegation, affected-party authority, recovery, and the distribution of labor and gains.

Core distinctions

Agency can include doing something directly, receiving assistance, accepting a suggestion, delegating a bounded action, or relying on shared background infrastructure. Those modes are not a maturity ladder. Initiation, observation, execution, authorization, review, and recovery are separate dimensions, and the appropriate arrangement depends on the activity, stakes, affected parties, and ability to reverse or repair consequences.

A person's permission to automate their own work does not automatically authorize decisions, surveillance, commitments, or harms for other people. Automation should therefore be evaluated alongside authority, consent, fallback, maintenance, ownership, governance, and who absorbs hidden correction work.

Ecosystem use

  • Root Sequence: owns the shared public principle, distinctions, open questions, and evidence boundaries.
  • Being Humane Atlas: the public Root Sequence source names a human-scale applied route around relief, fatigue, refusal, dignity, and failover; substantive private treatment remains in the private layer.
  • Community Infrastructure: the public Root Sequence source proposes a project translation around bounded assistant authority, affected parties, and hidden labor; project-specific details and status remain project-owned.
  • Coherent World: the public Root Sequence source proposes a simulation translation comparing distribution under similar labor-saving capability; private simulation details and canon remain outside the public Wiki.

Project-specific requirements, implementations, tests, and canon remain with their projects rather than becoming properties of this Wiki identity.

Boundaries

The concept does not claim that automation automatically creates free time, material security, equality, or meaningful work. Those outcomes depend on ownership, governance, transition costs, ecological limits, maintenance, bargaining power, access to essentials, and the distribution of gains and losses.

The public source is explicitly an AI-assisted working principle awaiting author review. Its modes, safeguards, and compact wording are proposals rather than empirically validated universal rules.

Provenance

The durable Root Sequence treatment was formalized publicly on September 24, 2026 after a discussion about balancing automation of unwanted or compulsory burdens with chosen activity, limited energy, meaningful participation, and the possibility of delegation. The source records the author's direction separately from AI-assisted synthesis of modes, safeguards, and wording.

The title and shorthand remain origin-unverified; this Wiki entry does not claim historical originality for either phrase.

Canonical substantive home

The full principle, mode distinctions, delegation boundaries, recovery questions, distribution analysis, project translations, and open questions live in Root-Sequence/root-sequence/concepts/agency-and-automation.md.

The Wiki keeps the stable identity, compact definition, relationships, provenance, and routing.

Wiki connections

Project lenses

Related entities

Referenced by entities

Canonical substantive home

  • https://github.com/Root-Sequence/root-sequence/blob/main/concepts/agency-and-automation.md