Open standards & artifacts for accountable systems.

STD-01 reference

Permanent link /standards/std-01-minimum-binding-set

STD-01 minimum binding set

The minimum binding requirements per right for STD-01, including clause references and insufficient implementations.

How to use

Block symbolic compliance.

Each right requires multiple binding conditions; no single UI tweak should qualify as compliance.

Read STD-01

Scholarly metadata

Authorship

Contact: standards@ethotechnics.org

Publication details

  • Published: Feb 1, 2026
  • Last updated: Feb 1, 2026
  • Version: v1.0.0
  • DOI: Pending Zenodo deposit

License: CC BY 4.0

Credit Ethotechnics Institute Ethotechnics Standards Office, include the page title + version, and link to the canonical permalink.

Archive snapshot: Wayback capture

Changelog

  • v1.0.0 · 2026-02-01 — Published minimum binding sets for all seven temporal rights.

Principles

Minimum binding means multiple enforceable commitments.

Use this appendix to enforce STD-01 without symbolic adoption.

  • All requirements in a right must be met to claim compliance.
  • Each requirement must map to a documented mechanism or policy control.
  • Insufficient implementations are explicitly excluded from compliance claims.

Clause references map to the canonical standard at STD-01 — The Temporal Bill of Rights.

Per right

Minimum binding sets by article.

Every right requires multiple binding controls, not a single surface fix.

Clause references

Stoppability

§1.1 · §1.2 · §1.3

Minimum binding set

  • A visible, always-available stop control for every active process.
  • State preservation with a durable pause token that restores progress.
  • A permanent exit on every screen; no forced tunnels without escape.

Insufficient implementations

  • A hidden or delayed cancel link that appears only after a timeout.
  • A stop button that deletes progress or forces a restart.

Clause references

Exit (Resignation)

§2.1 · §2.2 · §2.3

Minimum binding set

  • Exit flow with equal or less friction than entry, measured by steps and time.
  • One-step exit when entry was one-step, with no retention gating.
  • Immediate confirmation that account, subscription, or contract is closed.

Insufficient implementations

  • Exit paths that require support tickets or scheduled calls.
  • Mandatory surveys or retention scripts before exit is accepted.

Clause references

Bounded duration

§3.1 · §3.2 · §3.3

Minimum binding set

  • Hard clocks for every pending or review state with a public maximum duration.
  • Automatic escalation or failure state when the clock expires.
  • Declared time-to-completion before commitment, including worst-case ranges.

Insufficient implementations

  • A generic “we’ll email you” without a duration commitment.
  • Soft internal SLAs without user-facing time guarantees.

Clause references

Reversibility

§4.1 · §4.2

Minimum binding set

  • A grace window that allows reversal without staff intervention.
  • Default soft-delete or reversible states for destructive actions.
  • Explicit countdowns or timers for the reversal window.

Insufficient implementations

  • A help-center article that says reversals are “case by case.”
  • Reversal windows that require administrative overrides to access.

Clause references

Non-coercive waiting

§5.1 · §5.2 · §5.3

Minimum binding set

  • Live queue position and ETA visibility during waits.
  • No fake progress indicators or looping placebo activity.
  • Async callback or notification option for waits longer than five minutes.

Insufficient implementations

  • Unlabeled spinners with no ETA or queue transparency.
  • Hold-forever queues that reset if a user disconnects.

Clause references

Human override

§6.1 · §6.2

Minimum binding set

  • A named appeal path to a human reviewer with response time commitments.
  • Clear statement of institutional liability for automated decisions.
  • Appeal intake that is reachable from the decision surface itself.

Insufficient implementations

  • A generic support inbox with no appeal routing or SLA.
  • Automated denials that provide no human escalation option.

Clause references

Transparent burden

§7.1 · §7.2

Minimum binding set

  • Published time-tax metrics tied to real user workflows.
  • Impact statements for major releases that measure added burden.
  • A governance review when burden increases beyond declared thresholds.

Insufficient implementations

  • A one-time survey in place of ongoing burden measurement.
  • Release notes without quantified time or effort impacts.

Citations

Cite this minimum binding set.

Use the citation block for audits, procurement, and policy references.

Copy citation (APA/BibTeX)

Cite this minimum binding set Formats: APA, MLA, Chicago, BibTeX, RIS

Version

v1.0.0

Last updated

Feb 1, 2026

DOI

Pending Zenodo deposit

APA

Ethotechnics Standards Office. (2026). STD-01 minimum binding set. Ethotechnics Institute. https://ethotechnics.org/standards/std-01-minimum-binding-set

MLA

Ethotechnics Standards Office. "STD-01 minimum binding set." Ethotechnics Institute, 2026, https://ethotechnics.org/standards/std-01-minimum-binding-set.

Chicago

Ethotechnics Standards Office. "STD-01 minimum binding set." Ethotechnics Institute. Feb 1, 2026. https://ethotechnics.org/standards/std-01-minimum-binding-set.

BibTeX

@misc{std_01_minimum_binding_set,
  title={STD-01 minimum binding set},
  author={Ethotechnics Standards Office},
  year={2026},
  howpublished={Ethotechnics Institute},
  url={https://ethotechnics.org/standards/std-01-minimum-binding-set},
  version={v1.0.0}
}

RIS

TY  - WEB
TI  - STD-01 minimum binding set
AU  - Ethotechnics Standards Office
PY  - 2026
UR  - https://ethotechnics.org/standards/std-01-minimum-binding-set
ER  -

See also: Standards · Mechanisms