data.erase_own_field

A person's own record says something about erasure it can't: erase: on a field with anything but Erasure.retained or with no personal:, a reference that deletes a record that must stay, or a field named as the column erasure keeps.

Area 15, Personal data; not declinable; the next step is usually the human's.

Why Jadpo refuses it

On a field of the person's own record, erase: says one thing: this field stays when they are erased, because the law makes you keep it. Every other marked field is cleared whatever you write, and the whole record is deleted when nothing stays. So Erasure.deleted and Erasure.anonymised there say nothing erasure doesn't already do. A field that isn't marked personal: stays anyway, and Erasure.retained on it would keep the person's record for no reason.

An entity that keeps a record this way can't have a reference that deletes the record when another entity's records go, since that would take what must stay. It also notes when each person was erased in a column called jadpo_erased_at, so no field may be stored under that name.

What it looks like

main.jadpo:

config {    policy_retention: Duration {        default: 1826d    }}type PolicyNumber = Text {    max_length: 20}entity Customer {    id: Uuid    email: Email? {        personal: PersonalData.contact    }    policy_number: PolicyNumber {        personal: PersonalData.identifying        erase: Erasure.deleted    }    policy_ended_at: Instant?    person: true    retention: {        after: config.policy_retention        since: policy_ended_at    }}

   |18 |         erase: Erasure.deleted   |         ^^^^^ `Erasure.deleted`

(human) at the end of the next: line tells your coding agent to stop and ask you which fix you want, because the choice is yours to make: it decides whether a person's data outlives their request to be forgotten.

How to fix it

The question is whether the law makes you keep the field.

If it does, say so:

policy_number: PolicyNumber {    personal: PersonalData.identifying    erase: Erasure.retained}

Erasing a customer now clears their email and keeps their policy number, hidden, until their retention ends.

If it doesn't, remove erase::

policy_number: PolicyNumber {    personal: PersonalData.identifying}

Erasing a customer now deletes their whole record.

Related

• The person's own record
• Erasure
• Retention