AGENTIC DATA MANAGEMENT · FILE MUTATION
When AI does not just read but changes files
Write access becomes accountable only when every change is bounded, visible, tested, approved and recoverable.

01 · BOUNDARYAn explicit workspace and minimum rights limit impact.
02 · CHANGEA plan and patch expose scope and meaning before application.
03 · CONTROLTests, approval, versioning and reporting secure the transition.
CORE METHOD
SCOPE → INSPECT → PLAN → PATCH → VERIFY → APPROVE → COMMIT → REPORT
The agent does not mutate freely; it produces an evidenced chain of small controlled state transitions.
Does every write action have an explicit path, patch, test, approval gate and recovery route?