metaentitiesdedupaliasesmergeUpdated 2026-07-01

Entity Identity Protocol

Search before create. Stable identity lives in canonical slugs plus aliases, not in whatever name appeared in the latest source.

Entity identity prevents the wiki from splitting one person/tool/project across multiple pages. Duplicate pages are worse than missing pages because they make future answers confidently incomplete. Source: AGENTS.md Entity Identity Protocol

Before Creating an Entity Page

  1. Search exact name with qmd search "{name}".
  2. Search likely variants: handles, emails, company suffixes, product aliases, old names.
  3. Search frontmatter aliases with rg "aliases:|{name}" wiki.
  4. Check the target directory for nearby slugs.
  5. Decide whether the entity deserves a standalone page, a ledger row, or a section using Wiki Brain Operating Model.
  6. If a match exists, update the survivor and add the new alias.
  7. If no match exists, create a page through Filing Decision Tree.

Canonical Slugs

Use kebab-case.md. Prefer stable identity over presentation:

  • person: first-last.md, disambiguated when needed
  • company/project/tool: current canonical public name
  • collisions: add context, for example david-liu-crustdata.md

Wikilinks should use the canonical page title or slug without directory prefix.

Aliases

Aliases belong in frontmatter. Include:

  • nicknames
  • handles
  • email addresses
  • old product names
  • company abbreviations
  • capitalization variants that appear in sources

Aliases are required for person pages and strongly recommended for projects/tools with prior names.

Merge Protocol

When two pages are the same entity:

  1. Pick the more complete page as the survivor.
  2. Merge compiled truth into one coherent synthesis.
  3. Merge timeline entries in chronological order.
  4. Merge aliases and related links.
  5. Update all wikilinks from duplicate to survivor.
  6. Add redirects for retired slugs when lookup value remains.
  7. Delete or fold the duplicate only after links and redirects are updated.
  8. Rebuild index, redirect index, and qmd.
  9. Refresh packs, capsules, registry output, or review ledgers when the entity was part of a generated surface; use Generated Surface Contract.
  10. Log the merge.

Use a commit message like merge: duplicate-slug into survivor-slug when committing.

Shape Decision

Not every recurring name deserves a full article. Use the smallest durable shape that future agents can find:

Signal Shape
Kevin works with, builds on, or repeatedly references the entity Standalone page
Entity appears across multiple sources but has little narrative context Ledger row with aliases
Entity only matters as evidence for another topic Section or timeline entry on the stronger page
Old page was folded into a stronger page Redirect plus alias on the survivor

Notability Gate

Create a dedicated entity page when one of these is true:

  • Kevin directly works with or cares about the entity.
  • The entity appears across two or more sources.
  • The entity is central to a project, tool, decision, or philosophy page.
  • Future agents are likely to search for it.

Otherwise, link the mention if a page exists, or leave it as plain text until it recurs.

Timeline

Related Pages

Filing Decision TreeWiki Brain Operating ModelWiki Page FormatWiki Redirect IndexGenerated Surface ContractQuality GatesBacklink Index Protocol

13 pages link here

Backlink Index ProtocolMetaBacklink Iron LawSOULEnrichment TiersMetaEntity IdentityFiling Decision TreeFiling Decision TreeFiling Decision TreeHow to Update the WikiMetaMerge ProtocolFiling Decision TreeNotability GateFiling Decision TreePage Consolidation AuditMetaPeople FilingFiling Decision TreeQuality GatesMetaResolver Split DecisionDecisionsWiki Page FormatMeta