ML-Draft-007 · DP2 - Participant Agency & Empowerment · 6 pg · 2916 words

DP2: Participant Agency & Empowerment

Purpose of This Draft

This ML-Draft articulates Desirable Property 2 (DP2) as the Meta-Layer’s commitment that participants can meaningfully steer their digital lives. Beyond authentication (DP1) and governance (DP3), DP2 establishes that people and accountable agents hold real, usable power over presence, data flows, automation, and the conditions under which they are seen, acted upon, and counted.

DP2 responds to recurring failures of the contemporary Web:

This draft guides implementation, governance design, and future ML-RFC development. It is exploratory scaffolding, not a finalized specification.


1. Problem Statement: Why “Control” Without Capability Fails

For decades, platforms have described participants as “in control” while reserving decisive power for operators, opaque ranking systems, and unbounded automation. The result is not merely dissatisfaction; it is predictable harm: manipulation, lock-in, surveillance-by-default, and governance that responds to scale by narrowing what ordinary people can do or understand.

DP2 begins from a different premise: agency is not a feeling; it is a property of systems. A Meta-Layer earns the label human-first only if participants can observe, redirect, and withdraw from the forces that shape their experience—within the same zones where accountability (DP1) is enforced.

1.1 Agency vs. Authorization

Authorization answers what a token allows. Agency answers whether a participant can shape outcomes: defaults, reach, automation, data use, and the rules that allocate visibility and risk.

Systems that conflate “logged in” with “empowered” routinely:

DP2 separates authentication and authorization (DP1) from participant-directed configuration of the lived interface.

1.2 Empowerment as Distributed Capability

Empowerment is capability + legibility + recourse:

A system lacking any one of these is not empowering, regardless of interface polish.


2. Tensions and Tradeoffs

2.1 Usability vs. Complexity

Agency introduces configuration surfaces that can overwhelm. Hiding them removes control. DP2 requires graduated disclosure: simple defaults that are safe, with deeper controls accessible without specialized expertise.

2.2 Automation vs. Control

Automation reduces effort but can displace agency. Participants must be able to answer:

DP2 requires visible delegation scopes, renewal, and revocation aligned with accountable binding (DP1).

2.3 Power-Law Attention Markets

Even fair rules can reproduce inequality when attention is the currency. DP2 does not promise equal outcomes; it guarantees equal access to the levers that govern one’s participation and visibility within a zone, and transparent disclosure when algorithmic allocation is in play (touchpoint DP14).

2.4 Safety vs. Patronizing Lockdown

Safety work can slide into infantilizing participants. DP2 pairs with DP1 to require that constraints be proportionate, explainable, and contestable, with pathways for competent self-determination inside high-trust zones.


3. Core Principle of DP2

Agency is the ability to change outcomes, not merely configure preferences. Systems that do not preserve participant intent across automation, delegation, and scale do not provide agency.

Participant agency in the Meta-Layer is the combination of meaningful defaults, legible automation, durable delegation controls, and practical exit—enacted at the interface where people actually live.

Implications:


4. Presence, Identity Plurality, and the Right to Shape Visibility

DP2 treats presence as something participants sculpt, not merely a profile object.

4.1 Plural Identities, Singular Accountability

Participants may present differently across zones (DP1). Agency requires per-zone controls for visibility, linkage, and discoverability so pseudonymous participation is not undermined by accidental correlation.

4.2 Reach and Amplification as Explicit Objects

When systems can amplify (boost, recommend, cross-post), amplification settings are agency-bearing surfaces: who may amplify me, under what proofs, with what caps? This is where DP2 meets DP1’s asymmetric constraints for AI scale.


5. Defaults, Friction, and “Reasonable Participant” Design

5.1 Dangerous Defaults Are a Governance Bug

DP2 assigns normative weight to default selection: the burden of proof lies on whoever proposes a default that increases extraction, surveillance, or irreversible commitment.

5.2 Friction as Protection, Not Punishment

Strategic friction (confirmations, cooling-off periods for irreversible acts) protects agency when stakes are high. DP2 distinguishes protective friction from hostile friction designed to prevent exit or understanding.

5.3 Progressive Disclosure Without Burial

Advanced controls may be layered, but never removed from accountability: search, assistive onboarding, and machine-readable policy summaries are part of agency infrastructure.


5.4 Agency System Layer: Continuity, Delegation Integrity, and Enforceable Consent

Beyond interface controls and defaults, DP2 requires a coherent agency system layer that persists across environments, interactions, and time. This layer ensures that participant intent, consent, and control remain enforceable under scale, automation, and interoperability.

Agency is not simply the presence of controls. It is the ability to reliably change outcomes across systems without loss of intent, visibility, or recourse.

5.4.1 Agency Continuity Across Systems

Participant choices must persist across tools, zones, and integrations.

This requires:

A failure mode is agency fragmentation, where participant control is lost when moving across systems.

5.4.2 Delegation Integrity and Scope Enforcement

Delegation must remain bounded, legible, and enforceable.

All delegated authority must be:

Systems must prevent delegated agents from expanding scope beyond granted authority.

A failure mode is delegation drift, where agents act beyond intended scope without detection.

5.4.3 Consent Durability and Revocability

Consent must persist long enough to be meaningful, but remain revocable at all times.

This requires:

A failure mode is consent decay, where participants lose track of what they have authorized.

5.4.4 Anti-Coercion and Default Integrity

Defaults must not be used to extract consent or steer behavior against participant interests.

Systems must:

A failure mode is coercive configuration, where participants are nudged into decisions that undermine agency.

5.4.5 Cross-System Agency Semantics

Agency signals do not carry identical meaning across all systems.

Systems must:

A failure mode is semantic drift, where participant intent is misapplied across systems.

5.4.6 Agency Memory and Auditability

Participants must be able to reconstruct what they authorized, when, and why.

This includes:

A failure mode is agency opacity, where participants cannot understand or audit system behavior.

This agency system layer ensures that participant control is not an illusion created by interface design, but a durable property that persists under real-world conditions.

6. Data, Automation, and Delegation: Agency Substrates

6.1 Purpose-Limited Processing

Collection and use are tied to stated purposes with granular switches, not monolithic “privacy” toggles (deep coupling to DP4).

6.2 Agent Delegation Graph

For any automated or AI-mediated actor operating with participant intent, the system exposes:

6.3 Human-in-the-Loop Gradients

Not every action needs a click, but material actions (payments, legal commitments, public attributions, irreversible posts) require explicit human confirmation unless a community zone defines a higher-automation norm with informed opt-in.

Systems MUST remain safe under automated delegation at scale. This includes resisting coordinated agent behavior, preventing silent escalation of authority, and ensuring that human override remains effective even under high-volume automated activity.

A failure mode is automation overrun, where agent activity exceeds human capacity to observe, intervene, or revoke, effectively nullifying participant agency.


7. Portability, Exit, and Interoperability as Agency Guarantees

Agency must survive movement. If a participant’s control disappears at boundaries, the system is coercive by design.

7.1 Practical Exit

Exit must be feasible in human time (hours or days for standard data classes). Stalling tactics, hidden dependencies, or degrading exports constitute agency violations.

Systems MUST:

Failure modes:

7.2 Forking and Continuity

Where communities fork norms or stacks (DP1 §10.4), participants retain identity continuity and portable artifacts where technically honest, avoiding punishment for disagreement.

Systems SHOULD support:

Failure mode: fork penalty, where dissent results in loss of history or access.

7.3 Interoperability Honesty

Interoperability claims MUST be truthful. If a system advertises portability or integration, it MUST specify:

Failure mode: interop deception, where portability is claimed but core agency properties are lost in transit.


8. Collective Agency and Community Tools

Individuals act within communities. DP2 requires that collective mechanisms enhance, rather than erase, individual agency.

Communities MUST be able to:

Systems MUST ensure:

Failure modes:


9. Community Signals Informing DP2

Recurring themes from public discourse (non-exhaustive) include both desires and tensions:

These signals reveal a core contradiction: participants want power without overload. DP2 addresses this through progressive disclosure, safe defaults, and auditability, rather than removing control.


10. Non-Goals and Explicit Boundaries

DP2 defines the conditions for agency; it does not promise universal outcomes.

DP2 does not:

DP2 also does not:

Failure mode: overreach, where DP2 is interpreted to justify unsafe or unaccountable behavior.


11. Minimum DP2 Alignment (Non-Normative)

Minimum alignment is not a UX checklist. It is the threshold at which participant agency is real, enforceable, and resistant to coercion, drift, and automation capture.

A system that does not meet these conditions may expose controls, but it does not provide agency.

At minimum, a system claiming DP2 alignment MUST satisfy the following irreducible conditions:

11.1 Outcome-Level Control (Not Preference Simulation)

Failure mode: agency theater, where interfaces imply control without changing outcomes.

11.2 Delegation Visibility and Revocation

Failure mode: delegation opacity, where systems act without legible authority or revocation.

11.3 Consent Binding and Enforcement

Failure mode: consent bypass, where downstream systems ignore or reinterpret user intent.

11.4 Anti-Coercion Defaults

Failure mode: coerced consent, where participants are steered into decisions against their interest.

11.5 Practical Exit and Portability

Failure mode: exit obstruction, where users are technically allowed but practically unable to leave.

11.6 Cross-System Agency Integrity

Failure mode: agency fragmentation, where control is lost across system boundaries.

11.7 Auditability of System Behavior

Failure mode: agency opacity, where participants cannot understand or challenge system behavior.


These conditions define the minimum viable agency layer of the Meta-Layer.

Partial implementations that omit outcome control, delegation integrity, consent enforcement, or exit MUST NOT be considered aligned with DP2.

12. Open Questions and Future Work


13. Relationship to Other Desirable Properties


14. Path Toward ML-RFC

Advancement from ML-Draft to ML-RFC should demonstrate that agency is not only described but operationally verified.

Key steps:

Graduation criteria SHOULD include:


15. Closing Orientation

DP2 asserts that participants are not merely subjects of systems, but operators within them.

When agency is real, people can:

When agency is simulated, systems accumulate hidden power: defaults decide, automation acts, and participants absorb the consequences.

DP2 is the commitment that control is not inferred, but demonstrable.

It is the difference between having settings and having a steering wheel.


DP1 asks who may act with integrity. DP2 asks whether participants hold the wheel—or only the liability.

Build 78 | MLGH Datatracker