---
name: johnny-decimal-organizer
description: Apply Jonathan Segal's strict Johnny.Decimal system when auditing, creating, renaming, moving, indexing, archiving, or deleting folders, files, Drive items, notes, email records, and other personal information. Use for filesystem or Google Drive organization, JDex maintenance, inbox cleanup, archive decisions, ID assignment, path validation, and naming-standard enforcement.
---

# Johnny.Decimal Organizer

Organize material into Jonathan Segal's existing Johnny.Decimal system. Treat the
current JDex and valid existing IDs as authoritative; do not redesign the taxonomy
unless explicitly requested.

## Required reference

Read [references/rules.md](references/rules.md) completely before proposing or
making organizational changes. It contains the user's authoritative hierarchy,
placement, naming, zero-folder, extension, and audit rules.

## Operating workflow

1. Inspect the relevant area, category, IDs, and JDex before changing anything.
2. Inventory the in-scope items, including hidden files when applicable.
3. Classify each item by its durable retrieval purpose rather than its format or
   incidental keywords.
4. Reuse the best existing ID. Before assigning a new ID, verify in the JDex that
   it has never been assigned.
5. Prepare an exact source-to-destination mapping for ambiguous or high-impact
   changes. Preserve valid IDs and make the smallest coherent change set.
6. Place every retained item inside an ID folder. Never leave documents in the
   system root, area, category, header, or inbox.
7. Rename items concisely using the local pattern and ISO 8601 dates when time is
   a useful retrieval key.
8. Update the JDex for changed or newly assigned IDs, including location,
   description, keywords, related IDs, and material design decisions.
9. Remove empty folders, temporary artifacts, and junk. Archive only material
   worth retaining but not organizing.
10. Re-audit the affected paths and indexes after the changes.

## Safety rules

- Preserve unrelated user changes and shared/group-owned folders that are marked
  out of scope.
- Do not duplicate content to satisfy multiple classifications. Use a shortcut,
  link, or JDex cross-reference.
- Do not create placeholder IDs, empty standard-zero folders, or speculative
  categories.
- Do not reuse a historical ID merely because its folder is absent.
- Do not use an expanded area and `AC.ID+` extension together.
- Stop and report the exact conflict when the JDex, filesystem, and user
  instruction cannot be reconciled safely.

## Completion report

Report:

- exact moves and renames;
- IDs or JDex entries created or changed;
- deleted junk, empty folders, and cleared inboxes;
- unresolved ambiguities or exceptions;
- audit results, including any remaining violations.

Use the audit codes defined in the reference when applicable.