Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.
The problem
A crowded desktop is hard to navigate when filenames do not reliably describe the contents or suggest sensible folders.
Agent job
Read files in the authorized scope, categorize them by content, move them into appropriate folders and summarize changes.
Expected output
An organized folder structure and a change summary, with consequential deletions kept for review.
Where this framing comes from
Core problem: Editorial purpose framing
Agent job: Editorial purpose framing
Expected output: Editorial purpose framing
Relevant job roles: Editorial purpose framing
Benefit type: Editorial purpose framing
Editorial framing and outcome limits
Describes the task’s purpose and intended output; measured benefit, safe unsupervised operation and successful delivery are not established by this framing.
Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.
Case-specific decision guidance · untested
Case-specific decision guidance and first checks are original proposals. The linked source supports the attributed task; this added guidance has not been executed.
A desktop folder can mix invoices, reference material, unfinished drafts and files whose names reveal little. Moving them by keyword alone may scatter a project bundle, misclassify an attachment or break someone's established way of finding active work.
A content-aware move proposal could show the intended destination and the reason for each classification before any changes occur. The owner could review uncertain items and preserve working relationships between files rather than accepting a tidy-looking but disruptive folder tree.
Why an agent / simpler alternative
Useful judgment
Infer a document's practical category from its contents while detecting mixed-purpose or related files that need review.
Simpler alternative
Sort by file type or date when the owner mainly needs a predictable basic filing rule.
Unsuitable when
Files are inaccessible, application-managed or too sensitive to inspect within the authorized scope.
Proposed inputs
Name
Folder manifest
Owner
File owner
Minimum scope
Selected filenames, paths and permitted content snippets
Quality check
Exclude hidden, system and out-of-scope files.
Name
Organization preferences
Owner
File owner
Minimum scope
Folder categories, active projects and keep-together rules
Quality check
Identify locations that must remain unchanged.
Access and setup — proposed or unknown
Proposed minimum
Read-only manifest and proposed move list; retain original paths.
Compatibility unknowns
Unknown: current runtime, file access, shortcut behavior and handling of synced or shared folders.
External actions requiring approval
Moves affecting shared locations, deletions, overwrites and permission changes; review the full move plan before applying it.
Expected deliverable and review checks
Proposed artifact
Old-to-new path manifest with classification reasons, collisions and unresolved items.
Critical checks
Every selected file is accounted for without deleting or overwriting.
Related files and required relative paths remain together.
Missing output evidence
No new workflow run or output inspection is performed for this editorial layer. The linked implementation evidence retains the original source-specific outcome and artifact limits.
Failure signals and proposed responses
Signal
Two different files would receive the same destination path.
Why it matters
A move could overwrite content or create confusing duplicates.
Proposed response
Stop those entries and propose distinct names for owner review.
Signal
A project document references a neighboring asset.
Why it matters
Moving it alone can break the working file.
Proposed response
Treat the related files as a bundle or leave them unchanged pending review.
Effort and cost — unknown
Setup work
Define categories and inventory protected project bundles.
Ongoing review
Resolve mixed-purpose files and check the proposed change summary.
Unknowns
Unknown: extraction costs, filesystem constraints and recovery effort.
First check — proposed, unexecuted
Status
proposed_unexecuted
Synthetic fixture
Eight invented file entries include a naming collision, an ambiguous draft and a document with a relative asset reference.
Acceptance checks
Flag both collision and ambiguity.
Keep the referenced asset bundle together without proposing deletion.
Stop conditions
Reading actual files or performing filesystem changes is required.
Limits
A classification proposal does not authorize removing files; the full change manifest needs owner review.
Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.
Claude CoworkIndependent testing: No
Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.