agentleFS
iwesysiwesys/IWE/.claude/skills/consent/SKILL.md

consent

Skill0 starsChanged 25 days agoMITView on GitHub

Manage consent in learning.tracking_consent — opt-in / opt-out / status

2 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Consent — tracking consent management

Purpose: the pilot manages their own consent for behavioral data processing (events: day_plan_, wp_, w_reflections, etc.). Without opt_in=TRUE, the stage_evaluator worker skips the pilot.

Architectural principle: consent is stored in learning.tracking_consent (BC = learning, not persona). This is an aggregation permission, not personal data.

When to use

Manage consent in learning.tracking_consent — opt-in / opt-out / status / revoke. Required for the stage_evaluator worker (WP-253 Block 2). GDPR-compatible.

Arguments

  • status (default) — show the current consent state
  • opt-in [scope1,scope2,...] — grant consent (default scope: stage_evaluation)
  • opt-out — revoke consent (opt_in=FALSE, history is preserved)
  • revoke — delete the row entirely (GDPR right to erasure)

Algorithm

Step 1. Call the routing Script

bash "$IWE_SCRIPTS/route-task.sh" --skill consent --args "$ARGUMENTS"

The Script reads IWE_OWNER_ORY_UUID from the Environment. It writes via the consent_writer Role (Migration 113); fallback to DATABASE_URL_LEARNING_DIRECT.

Step 2. Interpret the result

The Script reports success via stdout (exit 0) or an error via stderr (non-zero exit).

Step 3. Return the response to the pilot

Print the Script's stdout to the pilot without modification.

Available scopes

  • stage_evaluation — Mastery stage Assessment via RCS indicators (FORM.089)
  • club_activity — club activity tracking (WP-296, post/topic)

Examples

/consent status
/consent opt-in                              # default: stage_evaluation
/consent opt-in stage_evaluation,club_activity
/consent opt-out                             # preserves data, disables processing
/consent revoke                              # deletes the row entirely

Distinction: opt-out vs revoke

  • opt-out — the pilot says "stop processing," but data is retained for Audit. The worker skips.
  • revoke — the pilot exercises the right to erasure (GDPR). The row is deleted; a new opt-in is required to re-enable.

Note: deletion of production data (events, reflections, transitions) is a separate process handled by anonymization_worker. This command only manages the record in tracking_consent.

Dependencies

  • Migration 113-consent-writer-grants.sql (in the Infrastructure Repository's migrations directory)
  • Privacy spec: B7.3.6-stage-evaluation-privacy-spec.md (Data-Governance) in your ecosystem-development Repository, if one exists
<!-- USER-SPACE --><!-- /USER-SPACE -->

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.