Skip to content

docs: record why tangles of directories get no move search - #43

Merged
alecf merged 1 commit into
mainfrom
docs/dir-move-bound
Nov 14, 2026
Merged

alecf merged 1 commit into
mainfrom
docs/dir-move-bound

Conversation

@alecf

@alecf alecf commented Nov 14, 2026

Copy link
Copy Markdown
Owner

What changes for the reader

Nothing in the report changes. The plan doc said a move search for tangles of directories was next. This records why it was dropped.

The measurement

For each tangle of directories, I removed every edge from another module into one file, for each file in turn. No single move can remove more than that. A move must leave at most two thirds of the tangle, or break it.

  • On the four public repositories the default granularity finds 11 tangles of directories.
  • 9 of 11 fail even this bound.
  • The 2 that pass have no file cycle under them. The report calls those a product of grouping and proposes no fix, on purpose.

So the search would print nothing new on these repositories. At file granularity the same repositories get 109 moves, and the hint pointing there stays.

🤖 Generated with Claude Code

https://claude.ai/code/session_01S7cyneSpBhH5XCwE3t8w1Y

An upper bound on any single move fails on 9 of 11 directory tangles in
the four public repositories. The 2 that pass have no file cycle under
them, so the report already proposes nothing there.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S7cyneSpBhH5XCwE3t8w1Y
@alecf
alecf force-pushed the docs/dir-move-bound branch from 617fd7d to b5ec2d1 Compare November 14, 2026 01:23
@alecf
alecf merged commit 3dd87d2 into main Nov 14, 2026
10 checks passed
@alecf
alecf deleted the docs/dir-move-bound branch November 14, 2026 01:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant