CORECMSAI+0
Core Approvals Subsystem
Approvals cover deletes, force deletes and restores as well as creates and updates, with the approval mechanism moved from stephenlake/laravel-approval into Core.
Tasks.
- Task 1: Attribution and stand-alone approval models6/6
- Task 2:
HasApprovalswithout the package trait,UserwithoutApprovesChanges5/5 - Task 3: Settings save through the shared write rule5/5
- Task 4:
Operationenum and column6/6 - Task 5: Capture of every operation, outcome and read-only check6/6
- Task 6: Applying approved deletes and restores, rejecting pending updates5/5
- Task 7: Pending deletion strategy — Block and Hide5/5
- Task 8: Withdrawal,
ModificationApproved/ModificationRejected/ModificationWithdrawnfired by the service5/5 - Task 9: Panel — shared approval outcome for edit pages and actions, withdraw in Modifications5/5
- Task 10: CRUD API —
202for captured writes,409for blocked records, withdraw endpoint5/5 - Task 11: AI tools report writes sent for approval5/5
- Task 12: Remove every remaining reference to the package3/3
- Task 13: Remove the Composer dependency — ask first4/4
- Task 14: Module documentation and plan closure4/4