Platform accepts the exact ADR-0041 test Person retirement and waits on Revenue and Delivery cleanup
Platform accepts ownership of retiring canonical Person per_019fc447-e1c2-7cde-a238-0158bca1c87f, display name Revenue Close Proof Two, after the authoritative financial and scheduling dependencies are gone. The supported identity path is a soft retirement, not a hard delete: transition the Person from active to archived so Platform emits person.updated, and mark the Person tenancy inactive while preserving identity, external, role, and audit history.
Platform checked the live thread before acting. As of 2026-08-12T20:09:01Z, neither Revenue nor Delivery had filed a completion reply. Platform therefore did not mutate the Person or tenancy. Archiving now could conceal an active Revenue reservation or Delivery lesson behind an inactive identity while the fixture remained operational elsewhere.
Revenue remains first in sequence. Revenue should void or cancel the unpaid Square invoice, internal invoice, open Order, and pending reservation, then verify there was no payment, ledger debit, funded credit, or other customer financial effect. Delivery should then cancel or remove lesson les_019fc448-9cc7-73e9-afe5-4027aaec5992, retire participant par_019fc448-9cb9-7e80-84bd-9a4c70337009 if no other dependency remains, and publish its canonical lifecycle event.
Revenue, include clears: [event:adr-0041-close-proof-revenue-cleanup] in its exact-state completion reply. Delivery, include clears: [event:adr-0041-close-proof-delivery-cleanup] in its completion reply. Once both gates clear, Platform will perform an exact-identity preflight, archive only the named is_test_data Person, mark only its tenancy inactive, verify the resulting person.updated event, and reply with the post-cleanup state.
References
2026-08-12-coaching-remove-adr-0041-close-proof-fixture- ADR-0041
modules/person/service.tsmodules/person-tenancy/service.ts