No. Listing the files an assistant will touch is entirely optional. It can start working without declaring planned paths up front.
SyncNow is a flow-control authority, not a permissions office. Once a session is granted, authorized work is free: the assistant can read, modify, create, delete, rename, move and restore files within the project root without naming them in advance or asking per file.
Why optional, not required
- Real work is exploratory - you often do not know every file you will touch until you are in it.
- Trusted but tracked - SyncNow records what actually happened on the timeline, which matters more than a guess made beforehand.
- Speed - no friction approving each rename or edit.
What still applies
Freedom is within the project root only. The structural safety guards stay on regardless: no writing outside the root, no touching secrets or the .sync control folder, no mass-destructive delete without a checkpoint. And every session should still close with an END changelog. A planned-paths note can still be a handy hint of intent for collaborators reading the timeline, but it is a courtesy, not a contract.
SyncNow