# `pdpa-platform` preset (business, stub)

> Stub only. Not implemented in this template version.

## What this preset would model

Personal Data Protection Act (Thai PDPA) compliance product: data subject self-service portal, consent management, DSAR (data subject access request) tracking, right-to-erasure workflows, breach notification, data classification, processor agreements.

## Suggested entities (when implemented)

`DataSubject`, `Consent`, `ConsentVersion`, `DsarTicket`, `DsarTask`, `BreachIncident`, `DataInventory`, `DataFlow`, `ProcessorAgreement`, `ConsentArtifact`.

## Why it is a stub even though PDPA flags are on

`compliance.pdpa = true` in `project.config.json` enables baseline **compliance hooks** (audit trail, anonymization scripts, retention policies). Those primitives live in `enterprise-modules/audit/` and Phase 8 docs.

The `pdpa-platform` preset would only be added if PDPA compliance is the _product itself_ (a tool sold to other companies) rather than a horizontal requirement applied to every product.

## When to promote

- A spawned project is the PDPA compliance product.
- Legal team validates the workflow model.
- DPO sign-off on the data classification taxonomy.
