Add reverse walk test: check who points INTO the folder from outside - #4
Open
jorgeccastro wants to merge 2 commits into
Open
Add reverse walk test: check who points INTO the folder from outside#4jorgeccastro wants to merge 2 commits into
jorgeccastro wants to merge 2 commits into
Conversation
jorgeccastro
added a commit
to jorgeccastro/icm-field-guide
that referenced
this pull request
Jul 21, 2026
New project example under the acquisition and relationship flywheel pattern: an anonymized shipped client kit (festival outreach for a photographer), following the existing card format and evidence labeling. New conditional operational extension: walk both directions before moving or renaming anything with outside consumers. The reverse walk checks who points INTO the old path from outside the moved tree; a version of it is proposed upstream for Architect's walk test (RinDig/icm-architect#4). Offered and accepted in the Clief Notes thread on the Field Guide release. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
jorgeccastro
force-pushed
the
reverse-walk-test
branch
from
August 15, 2026 09:29
4b55e54 to
d794f33
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ran Restructure against a real 500+ file workspace and wrote it up in the community thread. The walk test caught two genuine rot spots, but one class of breakage stayed invisible: two other systems of mine point at absolute paths inside that folder, and the migration would have broken them silently. Walking from the root outward can pass while external consumers break.
This adds the reverse walk in the two places it now belongs.
Restructure mode (this was the original PR, rebased): the inventory step, the propose gate, and one bullet in the walk test.
System map (new, since the form landed):
effects/answers "I am changing X, what inside the tree moves." It does not answer "what outside the tree points in." Nothing inside the subject references those consumers, so no card names them until you go looking. One paragraph in slice 4, one failure mode.Rebased onto b20fb45. Six lines total, no new sections.
I run this as a script over a fixed set of scopes before any migration. That is what convinced me it belongs in the method and not just in my own checklist: on the last restructure it returned two consumers the forward walk had no way to see.