Finish the retarget: no stale ADR-008 references remain

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-17 15:42:24 +02:00
parent dd127578c4
commit 54779f5eb7

View file

@ -187,14 +187,14 @@ before treating any as in scope:
| Area | Why the estate touches it | Already live in |
|---|---|---|
| Data protection / erasure and retention | Tenant personal data, the erasure horizon, whether key destruction satisfies an erasure obligation | ADR-008 plane R; `rapp-postgres` ADR-0002 |
| Data residency | The `P4` placement level exists for exactly this and has no occupants yet | ADR-008 plane P |
| Data protection / erasure and retention | Tenant personal data, the erasure horizon, whether key destruction satisfies an erasure obligation | Tenancy Posture axis R; `rapp-postgres` ADR-0002 |
| Data residency | The `P4` placement level exists for exactly this and has no occupants yet | Tenancy Posture axis P |
| Public procurement | `vergabe-teilnahme` is a procurement-participation app and the delivery-lane reference implementation | `business-app-service-contract` |
| Identity assurance | The IAM Profile's `aal2` class drives live re-query rather than cached claims | `iam-profile_v0.3`; ADR-008 plane I |
| Identity assurance | The IAM Profile's `aal2` class drives live re-query rather than cached claims | `iam-profile_v0.3`; Tenancy Posture axis I |
| Sector and cybersecurity obligations | Whether the estate is an in-scope entity at all is itself an open question worth recording once | — |
| AI and agentic entities | The tenant taxonomy has an `agentic` grouping for financially enabled AI entities | ADR-0013 |
**Worked example already in hand.** The ADR-008 retention research holds a
**Worked example already in hand.** The Tenancy Posture retention research holds a
finding of exactly this shape: data protection authorities have accepted key
destruction as erasure where physical deletion is disproportionate, under
conditions, and the EDPB has not formally endorsed it. True as recorded, likely
@ -210,7 +210,7 @@ from a record to the internal document it bears on, and back.
T01 gates everything. T02 and T03 can proceed in parallel once addressing is
fixed. T04 needs both. T05 is additive. T06 is deliberately last.
The temporary artifact URL for ADR-008 stays live until T04 passes its smoke
The temporary artifact URL for Tenancy Posture stays live until T04 passes its smoke
check, and the review is routed to the permanent URL, not before.
## Risks