Skip to content

docs: complete the MWP to ICM rename (16 stale references, 2 title typos) - #12

Open
Avicennasis wants to merge 1 commit into
RinDig:mainfrom
Avicennasis:docs/complete-icm-rename
Open

docs: complete the MWP to ICM rename (16 stale references, 2 title typos)#12
Avicennasis wants to merge 1 commit into
RinDig:mainfrom
Avicennasis:docs/complete-icm-rename

Conversation

@Avicennasis

Copy link
Copy Markdown

The project was renamed from Model Workspace Protocol to Interpretable Context Methodology, but 14 references to the old name survived, including in the two files carrying the most authority:

_core/CONVENTIONS.md:1   # MWP Conventions
_core/CONVENTIONS.md:3   The rules for building and maintaining MWP workspaces.
                         This is the canonical source.

Pattern 5 (Canonical Sources) supplies the smell test for exactly this case:

search the repo for a specific phrase. If it appears in more than one file and both instances are meant to be authoritative, one needs to become a pointer.

Run that test on the project's own name and it fails.

Also fixed

  • CLAUDE.md:1 read # Interpreted-Context-Methdology. Two typos: "Interpreted" for "Interpretable", and "Methdology" missing an o. 02ba5d8 fixed the README title but not this one.
  • CLAUDE.md:8 folder map root was model-workspace-protocol/.
  • README.md:254 cited the paper under its old title with a literal (link-to-paper) placeholder as the URL, while README.md:5 already carries the real arXiv link. Updated to the published title and URL: Interpretable Context Methodology: Folder Structure as Agentic Architecture, https://arxiv.org/abs/2603.16021

Verification

0 remaining matches for MWP / model-workspace-protocol / Model Workspace Protocol, 0 remaining link-to-paper, and no em dashes introduced (Quality Guardrails).

Note

references/conventions-reference.md line 3 is also touched by the /_core/ path PR. If both land, keep the relative path from that one and the ICM wording from this one.

The project was renamed from Model Workspace Protocol to Interpretable
Context Methodology, but 14 references to the old name survived, including
in the two files that carry the most authority:

  _core/CONVENTIONS.md:1   "# MWP Conventions"
  _core/CONVENTIONS.md:3   "The rules for building and maintaining MWP
                            workspaces. This is the canonical source."

Pattern 5 (Canonical Sources) gives the smell test for exactly this: "search
the repo for a specific phrase. If it appears in more than one file and both
instances are meant to be authoritative, one needs to become a pointer."
Run that test on the project's own name and it fails.

Also in this change:

- CLAUDE.md:1 heading read "# Interpreted-Context-Methdology" (two typos:
  "Interpreted" for "Interpretable", and "Methdology" missing an o).
  02ba5d8 fixed the README title but not this one.
- CLAUDE.md:8 folder map root was "model-workspace-protocol/".
- README.md:254 cited the paper under its old title with a literal
  "(link-to-paper)" placeholder as the URL, while README.md:5 already
  carries the real arXiv link. Updated to the published title and URL:
  "Interpretable Context Methodology: Folder Structure as Agentic
  Architecture", https://arxiv.org/abs/2603.16021

Verified: 0 remaining matches for MWP / model-workspace-protocol / Model
Workspace Protocol, 0 remaining "link-to-paper", and no em dashes
introduced (Quality Guardrails).

Note for the maintainer: references/conventions-reference.md line 3 is also
touched by the /_core/ path fix in the companion PR. If both land, keep the
relative path from that PR and the ICM wording from this one.
@Avicennasis

Copy link
Copy Markdown
Author

Correction on merge conflicts. My PR description mentioned a single one-line conflict. Having actually merged all five locally, there are three. Recording the exact resolutions so none of this costs you time.

Recommended order: #10 -> #11 -> #12 -> #13 -> #14. Each is independently mergeable; only the later ones need a touch.

Merging File Conflict Keep
#12 after #11 CLAUDE.md #11 adds the voice-driven-animation folder-map row, #12 renames MWP to ICM on the adjacent line both: the new row and (builds new ICM workspaces)
#12 after #10 conventions-reference.md:3 #10 fixes the path, #12 fixes the wording, same line both: The canonical ICM conventions live at ../../../_core/CONVENTIONS.md
#13 after #10/#12 conventions-reference.md #13 inserts the Pattern 8 entry next to lines #10 changed both: the new Pattern 8 bullet, with ../../../_core/ on the Bundled skills line below it

All three are "keep both sides" -- no judgment needed, nothing is dropped.

Verified end state with all five applied and conflicts resolved as above: bin/validate.py from #14 reports 15/15 rules passed, exit 0.

If you would rather not deal with any of this, say the word and I will collapse all five into a single PR, or rebase them into a stack so they apply in order with no conflicts at all.

@Avicennasis Avicennasis changed the title docs: complete the MWP to ICM rename (14 stale references, 2 title typos) docs: complete the MWP to ICM rename (16 stale references, 2 title typos) Aug 19, 2026
@Avicennasis

Copy link
Copy Markdown
Author

Correcting a count in the description: 16 stale references, not 14. The 14 figure counts bare MWP only; there are two long-form instances as well. Both are already fixed in the diff and described under "Also fixed", but they were not included in the headline number.

$ grep -roP '\bMWP\b' --include='*.md' . | wc -l                   # 14
$ grep -roP 'model-workspace-protocol' --include='*.md' . | wc -l  #  1  (CLAUDE.md:8)
$ grep -roP 'Model Workspace Protocol' --include='*.md' . | wc -l  #  1  (README.md:254)
                                                                   # 16 total

Title updated. The change itself is unaffected.

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