Editorial & Methodology Policy

Deterministic Phonotactic & Morphological Blending

Every core calculator on Name Combiner—including the Name Combiner, Couple Name Combiner, Baby Name Combiner, Word Combiner, Nickname Finder, and Username Generator—uses deterministic client-side TypeScript algorithms:

• Input Normalization: Entered strings are normalized in your browser using Latin orthography rules (`app/name-input.ts`), converting common accented Latin characters (such as é, ö, ł, ø) into base letters while rejecting unsupported non-Latin scripts rather than producing broken partial strings.
• Syllable & Boundary Segmentation: Names are segmented across vowel-consonant boundaries (onset, vowel nucleus, and coda) and shared letter pivots rather than arbitrary random character cuts.
• Readability & Phonotactic Scoring: Candidates are scored on a 0–100 scale based on vowel presence, length balance relative to the source inputs, and penalties for triple-letter collisions (e.g., lll) or 4+ consecutive consonant clusters (`app/generator-analysis.ts`).
• Explicit Fragment Provenance: Results display the exact prefix and suffix fragments and character-contribution percentages drawn from each input.

No Unreviewed Bulk AI Content

All editorial guides in our Naming Blog and all tool documentation modules are written, structured, and fact-checked by Lee Harsh. We do not publish unedited AI-generated articles or present automated text as human expertise.

Worked examples across our tools and guides (such as David + Sarah → Davah / Savid or Meadow + Lantern → Meadtern) are tested directly against our live algorithms and checked for spoken naturalness before publication.

Quarterly Documentation Audits

When our tools or guides reference external rules—such as character length limits, allowed symbols, or period placement restrictions on X/Twitter, TikTok, Instagram, YouTube, Discord, Twitch, and GitHub—we link directly to each platform's official help documentation (`app/username-platform-rules.ts`) and audit those rules quarterly.

When a tool checks syntax formatting rather than live account registries or government trademark databases, we state that boundary explicitly on the page so visitors never mistake a syntax check for legal clearance.

Every code change to namecombiner.co.uk must pass automated unit tests (`tests/*.cjs`) and our production route validator (`scripts/check-routes.cjs`) before deployment. Each guide and tool module displays a visible publication or “Last Reviewed” date, which is updated only when substantive content or algorithmic improvements are made.

If you spot a factual inaccuracy, a platform rule change, or an awkward blend output, please report it via our Contact page or email leeharsh@namecombiner.co.uk. Verified issues are investigated and corrected promptly.

Name Combiner is funded by display advertising served through Ezoic and Google advertising partners (see our Affiliate & Monetization Disclosure and Privacy Policy). Advertisers have zero influence over how our naming algorithms score candidates or how our editorial guides are written.