Doctrine
Legal & post-lock
The knockout legal and linguistic gate that runs before any purchase, and the governance that starts the moment a name is locked. The gate is human work; the product automates one screen of the US register, and only when a USPTO key is configured.
The gate, step by step
Six manual steps. The product automates one part of step 1 — a keyword screen of the US federal register — which appears on the appraisal as the legal gate. That screen needs USPTO_API_KEY: with no key the panel reads “not screened” and nothing was searched, and with a key it reports the marks the register returns. It is a keyword query, not the phonetic and same-commercial-impression judgement step 1 requires, and a no-hits answer is a filter, never a clearance. The rest stays with a person.
01USPTO Trademark Search at tmsearch.uspto.gov (TESS retired Nov#
1. USPTO Trademark Search at tmsearch.uspto.gov (TESS retired Nov-2023; old URLs redirect) — Basic + Advanced; Apr-2026 added a beta AI image-search (Clarivate) for logo/reverse-image, flagged supplemental. Search exact + PHONETIC sound-alikes (Kwik/Quick) + spelling variants, judged by same-commercial-impression in RELATED classes, NOT exact-match only. ⚠️ THE REGISTER IS SATURATED (2026 [High]): ~953,000 pending USPTO applications, ~4.4mo to first office action / ~10mo to registration; Class 9 (tech) alone >2M marks (was <23k in the 1980s); EUIPO 327,735 apps in 2025 (record). Even Anthropic's own ANTHROPIC word mark is under opposition — clearance difficulty is real; start early for anything ambitious (Placek: ~3yr lead for a big brand). ⚠️ 2026 ACCESS (verified 2026-08-27): tmsearch.uspto.gov is UI-ONLY (no public REST API); programmatic access needs a key issued to a registered operator: the trademark-search API at api.uspto.gov/api/v1/trademark/search answers 401 without one (verified 2026-10-27), and the TSDR Data API via data.uspto.gov covers per-case status (free registered key, 60 rpm status / 4 rpm docs) — the old ODP-Beta shut 2026-05-29 + the legacy developer hub was decommissioned 2026-06-05, so pre-mid-2026 integration URLs are STALE. Per-case status = tsdr.uspto.gov/statusview/sn<serial> (free, no auth). TMview (EUIPO, 70+ offices) + WIPO Global Brand DB = free UI, NO free bulk API. NO free AI-similarity API exists (Corsearch/TrademarkNow ExaMatch + Haloo.ai are enterprise-sales-gated, trial-only).
02TMview (EUIPO aggregate) + WIPO Global Brand Database#
2. TMview (EUIPO aggregate) + WIPO Global Brand Database — non-negotiable for an EU/HK-facing operator.
03Common#
3. Common-law sweep: Google '<name>' + category, App Store, GitHub, Product Hunt, social handles — unregistered in-use marks won't appear in any register and still sink you.
04Linguistic screen: native reads in every launch language#
4. Linguistic screen: native reads in every launch language — FRENCH + MANDARIN + CANTONESE mandatory for him.
05UDRP survival rules: you lose only if similar + no legitimate interest + bad faith ALL hold. Registered#
5. UDRP survival rules: you lose only if similar + no legitimate interest + bad faith ALL hold. Registered-BEFORE-their-mark ≈ immunity (RDNH; ACPA damages up to $100k for hijacking). Genuine distinct use = legitimate-interest defense. NEVER email a mark holder offering to sell (Exhibit A of bad faith). Register domain + mark in the COMPANY entity, not a founder (co-founder-breakup scar from r/startups).
06TWO#
6. TWO-PHASE, cheapest-first (2026 pro process): (a) KNOCKOUT search (~$150-500, 1-2 days, federal-register only — catches obvious blockers); ONLY if it passes → (b) FULL clearance (~$500-2,000+, adds state + common-law + domain + international). The USPTO does NOT clear for you — pre-filing clearance is entirely yours. AI-assisted KNOCKOUT tools worth knowing: Corsearch / TrademarkNow (similarity across ~190 registries), Haloo; none replace an attorney past knockout. A free pass = FILTER not conclusion — pay for a real clearance opinion only after the name survives 1-5 AND the venture passed its WTP gate (~60-70% of USPTO applications get an office action — descriptiveness or confusion).
Post-lock governance
Kill the pun in visuals#
('Keep HS Mate. Kill all chess.') The wordplay wins the NAME; the visual identity + copy must stand WITHOUT it — no leaning the brand on the pun.
Entity consistency lock#
(hdgefinance scar) Sub-brand/SKU names are ENTITIES: exact names, casing, and prices locked in ONE source + JSON-LD across all surfaces — inconsistency ('HDGE Pro' vs 'Core') measurably confused Google NLP + LLM scrapers = AI-visibility cost.
Ai entity disambiguation#
(2026-08-27) THE POST-LOCK AI-FINDABILITY PLAYBOOK — the fix for AI answers is operational, not the name. On lock, make the entity unambiguous to LLM knowledge graphs: (1) ONE canonical name string everywhere (site, socials, legal, invoices — casing included); (2) schema.org Organization/Brand + a `sameAs` array linking every official profile; (3) a Wikidata item + third-party corroboration (models resolve to a graph ENTITY, not a text string); (4) in-copy disambiguators in your own content ('Name, the growth-operator platform', not bare 'Name'). This is what actually moves AI-answer visibility per 2026 GEO doctrine — a distinctive name only gets you to the starting line. Links: rankability_ai_entity_test (pre-commit test + the ghost-citation ceiling), entity_consistency_lock.
Display name decoupling#
Keep store/display titles decoupled from code/repo names so renames stay ~free.
Personal vs commercial split#
Crowded namespaces are FINE for personal tools (n=1 user); the ownability gates only bind when a name goes commercial.