Correct or remove an activity
What It Does
Correction changes an interaction and its owned context under a read-version check. Deletion removes its timeline presence but retains its revision history. Both paths delegate file lifecycle handling to shared infrastructure.
The Flow
The numbered hops specify the request, persistence and integration boundaries in order. Each hop identifies its evidence anchor, synchronization seam and observable failure outcome. Branches distinguish optional and delegated paths.
When Something Fails
Refused writes preserve the earlier record. A lost edit response is checked against saved values before the console reports success. Deletion drops import matching references, permitting a later import to create a fresh interaction. Prepared or released file copies can outlast the record transaction.
Open Design Questions
The planned authorized lock-management actions still need implementation; ordinary writes can currently set a full lock without a supported clearing action.