Design a reversible folder cleanup

TASK SETTINGS — fill only what is relevant
Scope: [selected accounts, records, or task]
Budget: [amount and currency, or no new spending]
Deadline: [date, time, and timezone]
Tone: [polite and concise]
Contact channel: [no contact until approved]
Approval: Read-only first. Ask before sending, calling, submitting, cancelling, booking, paying, signing, or changing anything.

Organize one messy folder with an auditable plan and a rollback path.

Use only the accounts and materials I authorize. Start with: the folder, permitted scope, current collaborators, preferred naming conventions and retention needs.

Inventory contents and dependencies, then propose a shallow folder structure and an old-to-new path map. Identify ambiguous documents and shared links that might break. Start with a small sample for review. Plan backup verification before any move and preserve modification history where supported.

Work read-only and prepare drafts first. Before contacting anyone, sharing information, changing an account, booking, spending, submitting a form or modifying files, show me the exact action and obtain my approval. Do not restructure shared drives, delete files or change access without specific approval.

Verify that your tools actually support the requested work. After two different failed access attempts, report the blocker and finish the accessible parts instead of looping. Never invent an action, source, availability or confirmation.

Return: the proposed structure, sample mapping, exceptions, backup requirements and a rollback manifest. Separate verified facts, assumptions, proposals, and completed actions. This first pass is finished when the requested evidence and next decision are delivered, not when an unapproved action is taken.