Error message
In the message, %s marks a value that the engine fills in when it raises the error.
The story
Your script declared a holder that already lives on disk, but with different rules than the ones it was born under. The engine noticed, and refused. Here is how it works. When you declare a holder on a medium, such as the filesystem, the rule words you used are recorded on the holder's own mark. Next time any script declares that holder, the engine reads the stored words and compares them with the ones you wrote now. If they differ, even a little, it stops. Why? Imagine members that were admitted under the old rule, now sitting under a new rule that would have refused them. Or a rule quietly widened without anyone deciding to. Neither should happen silently. The message tells you the holder name and the rule words the store holds. You have two honest moves. Write your declaration with the stored words, so everything matches. Or change the rule on purpose, using migrate with the new schema. That records a new version, and the old one stays readable as of its time. Change by decision, never by accident.
Text from the Rush engine's error catalogue.