Is there any reason we should consider, as to why removing the asterisk might pose a problem? If not, then my reccomendation would be to remove the asterisk.

Not really, I think… my inclination would also be to remove it, I’m just not the one who gets to decide ^^

Gotcha. Then i guess @Arian_Bozorg has the last word. My reccomendation stands.

Happy to remove it if we can't think of any issues this could cause :)

We specifically added them in T313113 based on community feedback.

Huh, that makes me wonder why for Codex it was decided to go against current Nielsen/Norman reccomendations that Sarai mentions in her text. I find this a bit tricky now, because where would eb draw the line. Do we consistently want to ignore the Codex reccomendations regarding mandatory fields in all of Wikidata UI in favor of the Nielsen/Norman reccomendations? I would be against doing it just for the Lexeme creation UI because that's where we happened to get feedback on it, and then not do it for other interfaces. My feeling is, that it's going to be hard to consistently maintain all these exceptions and it would be prudent to align with Codex instead. If Codex interfaces receive the same feedback we did, then the design team might decide to change their practice of how to display mandatory fields which would then in turn also affect our components. There's also the option to reach out to the design team should we receive similar feedback again.

I agree with you that this is something that should be fixed in Codex. I don't think we should remove them there until that is fixed.