Open standards & artifacts for accountable systems.

Specification sheet

Permanent link /mechanisms/patterns/progressive-consent

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. Includes 3 steps, 3 reusable assets, and 4 snippet blocks.

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  -

Specification overview

At-a-glance details for planning and handoffs.

Capture the scope, assets, and validator handshakes before diving into the steps.

Spec essentials

What ships with this mechanism

  • 3 steps with checklist-ready owners.
  • 3 reusable assets for briefs and runbooks.
  • 4 reuse-ready snippet blocks.
  • 3 glossary anchors for shared terms.

Filters & validators

Where this spec sits in the system

Tagged in 2 filters with 1 linked validators.

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.

3 steps with checklist-ready owners, plus linked assets for handoffs.

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.

Reuse-ready snippets

Copy policy, audit, and incident language.

Use these snippets in requirements, audits, and postmortems with the mechanism permalink.

Policy requirement

Policy requirement (MEC-02 Progressive consent prompts)
- Stage consent requests with clear revocation paths and visible opt-out impacts.
- Document safety-valve defaults that preserve privacy when consent is withheld.
Reference: https://ethotechnics.org/mechanisms/patterns/progressive-consent

Product requirement

Product requirement (MEC-02)
- Each consent request includes purpose, duration, and revocation instructions.
- Opt-out paths remain visible and do not degrade core safety access.

Audit evidence checklist

Audit evidence checklist (MEC-02)
[ ] Consent journey map shows each ask, rationale, and rollback path.
[ ] Opt-out copy kit deployed across UI, email, and help surfaces.
[ ] Safety-valve defaults verified in staging and production.

Postmortem trigger

Postmortem trigger (MEC-02)
Trigger review if opt-out actions fail, are ignored, or re-enable without notice.

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.

Anti-patterns

Common failure cases and counterfactuals

Use these to avoid superficial compliance and clarify what success requires.

One-shot consent bundles

Asks for every permission at once without explaining timing or scope.

Counterfactual: Requests are staged with clear rationale, timing, and reversible defaults.

False-positive warning: Bundling can be acceptable if the scope is minimal and opt-outs are explicit.

Opt-out that does not stick

Offers a toggle but automation continues or re-enables without notice.

Counterfactual: Opt-outs pause automation and are logged with a visible confirmation.

False-positive warning: Some baseline data use can remain if it is disclosed and required for service safety.

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.