Specification sheet

MEC-02 Progressive consent prompts

Stage requests for data or automation over time, with reminders and exits that honor the consent journey.

Where it fits

Filters and handoffs

Tagged for Friction, Policy with validator handshakes.

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/BibTeX)

Cite this page Formats: APA, MLA, Chicago, BibTeX, RIS

Version

v1.1.0

Last updated

Jan 9, 2026

DOI

Pending Zenodo deposit

APA

Ethotechnics Institute Research Team. (2026). MEC-02 Progressive consent prompts. Ethotechnics Institute. https://ethotechnics.org/mechanisms/patterns/progressive-consent

MLA

Ethotechnics Institute Research Team. "MEC-02 Progressive consent prompts." Ethotechnics Institute, 2026, https://ethotechnics.org/mechanisms/patterns/progressive-consent.

Chicago

Ethotechnics Institute Research Team. "MEC-02 Progressive consent prompts." Ethotechnics Institute. Jan 9, 2026. https://ethotechnics.org/mechanisms/patterns/progressive-consent.

BibTeX

@misc{mechanism_progressive-consent,
  title={MEC-02 Progressive consent prompts},
  author={Ethotechnics Institute Research Team},
  year={2026},
  howpublished={Ethotechnics Institute},
  url={https://ethotechnics.org/mechanisms/patterns/progressive-consent},
  version={v1.1.0}
}

RIS

TY  - WEB
TI  - MEC-02 Progressive consent prompts
AU  - Ethotechnics Institute Research Team
PY  - 2026
UR  - https://ethotechnics.org/mechanisms/patterns/progressive-consent
ER  -

Glossary anchors

Link back to the definitions.

Jump to the glossary terms that frame this mechanism.

Steps

Put the mechanism in motion.

Start with the field cues, then use the assets to keep the work legible.

Assets

Keep outputs reusable.

Link or copy these assets into design docs, runbooks, and briefs so the mechanism travels with the work.

Consent journey map

Shows each request, rationale, and rollback path across the flow.

Opt-out copy kit

Short blurbs teams reuse in UI states, emails, and help docs.

Safety valve checklist

Confirms every step has a reversible, privacy-first fallback before shipping.

Example usage

Piloting a model-powered assistant

A concrete scenario to help teams see how the pieces fit together.

How it plays out

Product and legal teams stage data collection prompts over several sessions, preview how opting out affects recommendations, and keep a global “pause automation” control visible in the UI.

Validators

Pair validators with this mechanism.

Use these tools to size risk and keep the stewardship path visible.

Validator

LLM Capacity Benchmark

Lightweight evaluation to check if a model and its surrounding UI respect consent and context limits.