Mechanisms

Permanent link /mechanisms

Mechanisms

Specification-ready mechanisms for accountable systems, with cited primers, glossary entries, and reusable safeguards.

How to use this shelf

Structured, linkable specifications

Stable permalinks and filters keep standards, mechanisms, and validators aligned.

Scholarly metadata

Authorship

Contact: research@ethotechnics.org

Publication details

  • Published: Dec 3, 2025
  • Last updated: Jan 9, 2026
  • Version: v1.1.0
  • DOI: Pending Zenodo deposit

License: CC BY-SA 4.0

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

Archive snapshot: Wayback capture

Changelog

  • v1.1.0 · 2026-01-09 — Added citation metadata, mechanisms-level authorship details, and structured usage guidance.
  • v1.0.0 · 2025-12-03 — Initial public mechanisms release.

Copy citation (APA)

More formats

Role-based pathways

Role-based pathways

Pick the role that matches your responsibilities to jump to the most relevant guides.

I'm an Engineer I'm a Product Manager I'm a Regulator

I'm an Engineer

Prioritize stoppability, rollback readiness, and safe maintenance rhythms.

MEC-05 Kill switch for runaway automation

Stoppability playbook with triggers, operators, and restoration drills.

Open reading

MEC-03 Maintenance windowing

Plan safe downtime, fallback coverage, and stewardship windows.

Open reading

Glossary: Stoppability

Shared language for halts, safety valves, and time-to-halt targets.

Open reading

I'm a Product Manager

Design consent, appeals, and accountability into the user journey.

MEC-02 Progressive consent prompts

Stage consent requests with clear exits and reversible defaults.

Open reading

MEC-06 Appeal paths inside the UI

Bake dispute routes and human review into the experience.

Open reading

Glossary: Consent journey

Map how people move through requests, opt-outs, and follow-ups.

Open reading

I'm a Regulator

Focus on accountability logs, audit trails, and remediation evidence.

MEC-01 Decision log with dissent

Accountability logs with owners, dissent, and review dates.

Open reading

MEC-03 Maintenance windowing

Operational evidence of stewardship windows and documented fixes.

Open reading

Glossary: Repair log

Trace fixes, follow-ups, and published commitments over time.

Open reading

Quick start

  • Skim the primer for a 5-minute orientation and shared vocabulary.
  • Jump to the glossary for stable definitions you can cite immediately.
  • Use the mechanism filters to pull the right safeguards for your scenario.
  • Cite the permalinks in papers, policy memos, or peer reviews to anchor legitimacy.

Key mechanisms

Three high-signal mechanisms teams reuse most often when onboarding or auditing a system.

Agent Safety Object Model

Link mechanisms to a machine-readable governance profile

Publish the spec so mechanisms map to enforceable controls.

The Agent Safety Object Model ties action classes, receipts, and kill-switch authority to specific mechanisms.

  • Map MEC-01, MEC-05, and MEC-06 into the model.
  • Declare clocks and approvals per action class.
  • Attach evidence packs to validate compliance.

Browse by theme

Jump directly to the work you need.

Use tags to pre-filter the mechanisms catalog.

  • Governance

    Decision logs, maintenance windows, and escalation paths backed by diagnostics.

  • Friction

    Consent prompts, appeal paths, and humane defaults that keep interfaces accountable.

  • Policy

    Charters, stewardship commitments, and controls you can cite in contracts and playbooks.

Primer

Start here before diving into mechanisms.

Short overviews for onboarding and briefings.

Primer

Short explainers teams can skim before working with the mechanisms.

  • Why burden, consent, and stewardship matter for socio-technical systems.
  • How to align governance artifacts with the lived experience of the people using your product.
  • What “mechanism language” means for UI safeguards, facilitation prompts, and escalation design.

Usage guidance

How to adapt the materials to your org without slowing delivery.

  • Each section ships with permalinks; link directly in design docs or runbooks to keep teams aligned.
  • Filters call out whether a mechanism is governance-first, friction guidance, or a policy control.
  • Glossary terms stay stable so research, field notes, and diagnostics can cross-link without drift.

Glossary

Stable terms with per-entry permalinks.

Use these anchors across Field Notes, Research, and Diagnostics.

Full glossary: /glossary

Mechanisms

Governance, friction, and policy mechanisms with validator links.

Filters route work quickly and keep validators in reach.

  • Decision logs, maintenance windows, and escalation paths backed by diagnostics.

  • Consent prompts, appeal paths, and humane defaults that keep interfaces accountable.

  • Charters, stewardship commitments, and controls you can cite in contracts and playbooks.

Showing all mechanisms.

Mechanism bundle

Save selected mechanisms.

No mechanisms selected yet.

Current bundle link

Filters: Governance, Policy

MEC-01 Decision log with dissent

Capture high-stakes calls, dissenting views, and follow-ups so governance stays legible to teams and impacted people.

Glossary anchors: Design Authority , Repair Log , Contestability

Preview steps
  • Log the decision, rejected options, and who was consulted in one place.
  • Attach a short summary alongside the canonical record for external readers.

Example: Recording a launch gate call

Open mechanism detail

Diagnostics Burden Modeler

Filters: Governance, Policy

MEC-03 Maintenance windowing

Schedule improvements, monitoring, and resourcing using a visible stewardship window.

Glossary anchors: Maintenance Window , Maintenance Metabolism , Repair Log

Preview steps
  • Define maintenance windows with owners, success criteria, and rollbacks.
  • Publish communication cadences by risk level and audience.

Example: Coordinating a stewardship sprint

Open mechanism detail

Diagnostics Maintenance Simulator

Filters: Governance, Friction

MEC-05 Kill switch for runaway automation

Pre-authorized halt paths with named stewards, thresholds, and restoration drills so harms stop in seconds.

Glossary anchors: Stoppability , Ethical Interrupts , Time-to-Halt (TTH)

Preview steps
  • Map the automation path and mark where halts must land safely with owners.
  • Set tripwires for ethical interrupts that align with time-to-halt targets.

Example: Containing a runaway recommendation loop

Open mechanism detail

Diagnostics Maintenance Simulator , Burden Modeler

Filters: Friction, Governance

MEC-06 Appeal paths inside the UI

Give people a built-in channel to dispute outputs, get human review, or learn how a decision was made.

Glossary anchors: Contestability , Appeal Passage Rate , Permission Surface

Preview steps
  • Place an appeal entry point near the affected decision with response times.
  • Pre-fill context so people can submit without rebuilding the story.

Example: Adding appeals to a risk scoring tool

Open mechanism detail

Diagnostics Burden Modeler , Maintenance Simulator

Syllabus

Guided path for teams adopting the mechanisms.

A guided track for teams adopting the mechanisms. Each module links to glossary anchors and mechanism specs you can cite in docs.

60 minutes

Orientation

Outcome: Teams can route questions to the right section and cite glossary terms consistently.

  • Library tour and how to use permalinks in specs
  • Primer on burden, consent, and stewardship
  • Navigation of governance, design ethics, and policy filters

90 minutes

Field-ready research

Outcome: Practitioners share findings with linked terms and mechanism cues that ship with the work.

  • Integrating glossary terms into research and field notes
  • Tagging findings by focus area and diagnostic relevance
  • Building appeal paths and consent prompts into prototypes

75 minutes

Governance and maintenance

Outcome: Leadership aligns on accountable maintenance plans backed by diagnostic evidence.

  • Decision logs, stewardship windows, and escalation readiness
  • Pairing diagnostics with mechanism rollout
  • Designing safety valves for high-burden scenarios

Referenced by

How mechanisms connect to the rest of the system

Cross-links keep mechanisms, standards, and audits aligned.

Used in examples

Required by bindings

Verified by evidence packs

Search IDs: MEC-01, MEC-03, MEC-05, MEC-06, STD-01.1.1, STD-02.2.1, VAL-01, VAL-02, VAL-03.