STD-01 — The Temporal Bill of Rights

Related explainers

Use these short explainers when translating the rights for policy or product teams.

Execution vs redress clocks

Show the execution vs redress clock mismatch and highlight the irreversibility window that STD-01 is designed to constrain.

Preamble: The Doctrine of Finitude

We hold that human attention is a finite, non-renewable biological resource. In the Machine Age, the disparity between the infinite speed of automated systems and the fixed processing speed of the human mind has created a structural crisis of dignity.

When a system wastes human time through negligence, obfuscation, or coercive design, it is not merely a “bad user experience”; it is a Temporal Taking—an unauthorized extraction of life. It is measurable as a time tax with durable costs and documented burden.

To defend the human subject against the scale of the machine, we establish these seven inalienable rights. Any system that violates these articles is declared non-compliant with STD-01.

Clause schema (agent-readable)

Express every clause as a structured object so agents can validate compliance and request evidence.

{
  "std_id": "STD-01",
  "clause_id": "STD-01.C1",
  "requirement_type": "MUST",
  "subject": "interface",
  "condition": "active automated process",
  "obligation": "provide immediate exit control",
  "time_bound": "instant",
  "evidence_required": ["ui_state", "event_log"],
  "failure_mode": "forced tunnel"
}

Anti-patterns and counterfactuals

Use these to detect superficial compliance and clarify what success looks like.

• Hidden exit controls: A stoppability control exists but is buried behind multiple screens or support hints.
  Counterfactual: Exit controls are visible on every screen and halt the process immediately.
  False-positive warning: If the exit is labeled clearly and consistently, it likely meets the bar.
• Reversal without proof: Promises reversal but does not preserve state or provide a receipt that it happened.
  Counterfactual: Reversal preserves state, emits a receipt, and provides a clear next step.
  False-positive warning: Temporary preservation can be compliant if timelines are explicit and honored.

Article I: The Right to Stoppability

“No system shall force a user to complete a process they wish to abandon.”

1. §1.1 Immediate Cessation: Every active process must possess a clearly visible, universally accessible mechanism to halt operation immediately.

2. §1.2 Preservation of State: Halting a process must not result in the punitive destruction of data. The system must save the “Paused State” for a reasonable duration, allowing the user to return without penalty.

3. §1.3 The Prohibition of the Forced Tunnel: No interface may lock a user into a linear sequence without a permanent exit option available on every screen; “wizards” or “flows” are common examples.

Article II: The Right to Exit (Resignation)

“The user must always be able to leave.”

1. §2.1 The Universal Exit: A user must be able to sever their relationship with a system (delete account, unsubscribe, cancel contract) with equal or lesser friction than was required to create it.

2. §2.2 The One-Step Rule: If entry required one click, exit shall require no more than one click.

3. §2.3 Prohibition of Retention Scripts: Systems may not force users to navigate “retention flows,” “exit surveys,” or “confirmations of loss” as a prerequisite for exit. These act as Constructive Denial (blocking exit by inflating friction).

Article III: The Right to Bounded Duration

”No process may be infinite.”

1. §3.1 The Hard Clock: Every system state must have a defined maximum duration. “Pending,” “Processing,” or “Reviewing” states cannot persist indefinitely.

2. §3.2 The Timeout Guarantee: If a system cannot resolve a request within a declared timeframe, it must default to a failure state or a human escalation. It may not loop forever.

3. §3.3 Estimation of Burden: Before a user commits to a process, the system must declare the estimated time to completion. Concealing the duration of a task to secure engagement is a violation of consent.

Article IV: The Right to Reversibility

“To err is human; the system must forgive.”

1. §4.1 The Undo Window: For any action with consequential effects (deletion, transfer, publication), the system must provide a “Grace Period” during which the action can be reversed without administrative intervention.

2. §4.2 Non-Destructive Defaults: Systems shall not permanently destroy user data based on a single input. “Soft Delete” (archival) must be the default engineering state for all removal actions.

Article V: The Right to Non-Coercive Waiting

”Silence is not a valid status.”

1. §5.1 Visibility of Queue: When a user is placed in a waiting state, the system must provide accurate, real-time telemetry regarding their position and expected wait time.

2. §5.2 The Prohibition of False Activity: Systems shall not use “fake progress bars,” “placebo buttons,” or looping animations to simulate activity when the system is idle or stalled.

3. §5.3 Asynchronous Option: No user shall be forced to hold an active connection (keep a window open, stay on the phone) to maintain their place in a queue. Systems must offer callback or notification options for waits exceeding 5 minutes.

Article VI: The Right to Human Override

“The machine is a tool, not a judge.”

1. §6.1 The Escalation Path: Any automated decision that denies a user access, service, or property must include a clearly defined path to appeal to a human agent.

2. §6.2 The Liability of Automata: A system may not hide behind “algorithmic error.” The operating institution accepts full liability for the latency and errors of its automated agents.

Article VII: The Right to Transparent Burden

“The system must show the receipt.”

1. §7.1 The Cost of Compliance: Institutions must measure and publish the “Time Tax” their bureaucracy imposes on the public.

2. §7.2 Burden Impact Statement: Major system updates must be audited to ensure they do not increase the cognitive load or time requirement for existing tasks.