consent-lifecycle

Audit and manage consent events for Brazilian LGPD compliance.

2|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/Canhada-Labs/ceo-orchestration --skill consent-lifecycle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: consent-lifecycle
Source: https://github.com/Canhada-Labs/ceo-orchestration/tree/main/.claude/skills/core/consent-lifecycle
Command: npx skills add https://github.com/Canhada-Labs/ceo-orchestration --skill consent-lifecycle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides an auditable consent management system to comply with Brazilian LGPD and similar regulations, ensuring proper tracking of consent events.

Core Features & Use Cases

  • Consent Event Schema: Manage events such as granting, revoking, and expiring consent.
  • State-Machine Design: Utilizes state-machine concepts to maintain consent states.
  • Audit Logging: Generates tamper-evident audit logs for all consent events.
  • Integration Tests: Includes pre-defined integration tests to ensure functionality.

Quick Start

Load the consent-lifecycle skill to manage consent for the 'marketing' purpose of a user with 'user_id'.

Frequently Asked Questions about consent-lifecycle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage LGPD consent events for auditing and compliance?

You manage LGPD compliance by tracking granular consent events like granting, revoking, and expiring through an auditable state machine. This approach generates tamper-evident audit logs ensuring proper regulatory tracking.

What is a consent state machine and how does it handle per-purpose data compliance?

A consent state machine maintains specific states for user permissions, enabling per-purpose consent control for downstream system integration. It ensures immutable event streams for granular data compliance and operational review.

How do I implement immutable audit logging for consent revocation and re-up processes?

You implement immutable audit logging by processing consent events through a state machine that records revocation and re-up processes into a tamper-evident event stream. This ensures compliance and operational review readiness.

Can I use this consent management system for downstream integration when a user revokes permission?

Yes, the consent management system is designed for downstream system integration during revocation and re-up workflows. It manages per-purpose consent states to trigger necessary operational updates across connected platforms.

Does the consent lifecycle approach support integration testing for compliance workflows?

Yes, the consent lifecycle approach includes pre-defined integration tests to ensure the state machine and audit logging functionality operate correctly. This validates your compliance workflows before deployment.

When should I not use a state machine for consent management?

A state machine for consent management may not suit simple, stateless preference storage where granular per-purpose control and immutable audit logging are not required for compliance or operational review.