Synorigin

When the problem is legal, not creative

The same question as an ordinary naming check - with a completely different answer, because the risk was different.

This result is from a Claude Sonnet 5 session using the exact system prompt now in production, run before live web search was integrated. Reasoning and tone match the live app; matches were found from training knowledge, not live search.

What was being tested

Whether the check would treat an active registered trademark differently from a generic naming convention - with real urgency, rather than a soft "similar to" hedge.

The idea submitted

I want to name a shopping center Westfield Galleria, is it unique?

What Synorigin returned

Closest matches

The gap

The core issue is not creative originality. It is trademark conflict. Using "Westfield" for a shopping center you do not own would likely draw a cease-and-desist regardless of styling.

Verdict

This is not a derivative-idea problem, it is a live trademark collision - the gap above is not optional polish, it is a rename.

Why this result matters

Compare the language here with the Xantheon result. That one said "90% a category default." This one says "a live trademark collision" and "not optional polish, it is a rename." The severity of the wording changes because the category of risk changed.

That escalation only fires when a match is an actual specific name or brand in active use in the same category - not when something merely shares a theme or a trope. Over-flagging ordinary similarity as legal risk would make the warning meaningless.

Worth being clear about the limit: this identifies an obvious collision. It is not a registry search, and it does not replace one. Where a question genuinely turns on formal registration, Synorigin says so and names where the authoritative check happens.

Related

Check your own idea