Remove Verdict Override
Delete the finding on one (axis, subject_type, subject_id).
Address it exactly as you created it โ the same triple.
Removal is scoped to the axis you name. A plot carrying both a compliance override and an exclusion attestation keeps the other one; deleting a compliance override does not touch the Article 10 attestation on the same plot.
โถRequest body
{
"axis": "plot_compliance" | "legality" | "exclusion", // required
"subject_type": "plot" | "entity" | "record", // default "plot"
"subject_id": "uuid", // required
"reason": "max 2000 chars" // required
}
โถWhat changes
The subject reverts to its computed verdict. That is the point of the call, and it has consequences worth expecting:
- Removing a
plot_complianceoverride from a plot Epoch assessednon_compliantputs theplots_non_compliantblocker back and the record stops being submittable. - Removing an
exclusionattestation returns the plot to the filing, and it will be assessed on its own merits. - Removing a
legalityclearance restores the computed legality verdict and the clearance block leaves the audit-trail document.
A config.finding_removed event records the deletion with your
reason as payload.note, so the removal is as auditable as the
write.
โถIdempotent
Deleting a finding that is not there answers 200, not 404, which
keeps retries safe. Two things tell you nothing was removed:
data.idreads the literal"deleted"rather than the finding's composite key.- No
config.finding_removedevent is appended. The log records what happened, and nothing happened.
So do not read a 200 here as proof a finding is gone โ it may
never have existed, or it may sit on a different axis than the one
you named.
โถRemoving versus expiring
Deleting a finding erases it. Setting valid_to in the past
retires it: the finding stops applying, but stays readable and
stays printed in the audit trail as expired.
Prefer expiry when the attestation was true and has run out โ the document should still show what was attested and when. Delete only when the finding should never have existed.
โถErrors
| Status | Code | When |
|---|---|---|
| 400 | BAD_REQUEST | Unknown axis, malformed subject_id, missing reason |
| 401 | UNAUTHORIZED | Missing or invalid API key |
| 403 | FORBIDDEN | Key lacks eudr:write |
| 404 | NOT_FOUND | Record is not visible to the caller |
| 409 | CONFLICT | The version is filed to TRACES and frozen |
Required scope:
eudr:write