Part of #888.
User problem
Names such as Ben Vallack Nav and Chord Groups (Ben Vallack style) assume users know the source material. The names provide attribution, but they do not tell a newcomer what the rule family does or how it differs from neighboring options.
Users should be able to choose a rule from its name and short description without recognizing a creator's name.
Decision to make
For each community-derived rule family:
- Decide whether the primary name should describe the behavior or workflow.
- Preserve attribution in a secondary line, detail view, or guide where it adds useful context.
- Avoid renaming established concepts when the community name itself is the clearest commonly understood term.
- Consider migration and saved-configuration implications before changing any stable identifier.
Initial examples:
- Ben Vallack Nav
- Chord Groups (Ben Vallack style)
Deliverable
A naming recommendation with proposed primary names, attribution treatment, and a clear statement about whether internal identifiers remain unchanged.
Human review needed
Approve the product names and attribution placement before implementation.
Acceptance criteria
- Each proposed primary name communicates the user's outcome or interaction model.
- Attribution remains discoverable without carrying the full explanatory burden.
- Internal identifiers and migration risk are explicitly addressed.
- Any approved UI/documentation changes are split into bounded follow-up work.
Non-goals
- Removing credit for community sources.
- Renaming internal identifiers by default.
- Broad catalog copy cleanup.
Part of #888.
User problem
Names such as Ben Vallack Nav and Chord Groups (Ben Vallack style) assume users know the source material. The names provide attribution, but they do not tell a newcomer what the rule family does or how it differs from neighboring options.
Users should be able to choose a rule from its name and short description without recognizing a creator's name.
Decision to make
For each community-derived rule family:
Initial examples:
Deliverable
A naming recommendation with proposed primary names, attribution treatment, and a clear statement about whether internal identifiers remain unchanged.
Human review needed
Approve the product names and attribution placement before implementation.
Acceptance criteria
Non-goals