Jonomor

Reference — Jonomor

Layer: Entity Stability · All References

Entity Registry

What an Entity Registry Is

An entity registry is the authoritative document that defines the canonical name, Schema.org type, stable @id, and description for every entity in a system — before any page, schema declaration, or cross-domain reference is published.

The entity registry is the governance layer for the Entity Stability stage of the AI Visibility implementation sequence. Without a registry, schema diverges, names vary, and descriptions drift — producing fragmented entity representations in AI training data. With a registry enforced before publication, every surface produces consistent signals that accumulate around a single entity representation rather than fragmenting across several weak ones.

Why Canonical Names and Canonical IDs Matter

AI language models learn entity associations from statistical co-occurrence patterns in training data. Every time an entity name appears in a context — alongside related terms, attributed to relationships, described with specific language — the model updates its internal representation of that name.

When a name is used inconsistently — 'Jonomor' in one location, 'jonomor.com' in another, 'Jono-Mor' in a third — the model distributes the co-occurrence signal across three representations. None accumulates enough signal to produce reliable retrieval. The registry prevents this by locking one canonical form.

Canonical @ids serve a parallel function in schema. Two schema declarations that refer to the same entity using different @id values — 'https://www.jonomor.com/#org' versus 'https://www.jonomor.com/#organization' — are two separate nodes in the knowledge graph. They cannot be merged without an explicit owl:sameAs declaration. The registry prevents this by assigning one stable @id per entity before any schema is written.

Current Jonomor Registry

Ali Morgan

Person

https://www.jonomor.com/ali-morgan#person

Jonomor

Organization

https://www.jonomor.com/#organization

XRNotify

SoftwareApplication

https://www.xrnotify.io/#app

MyPropOps

SoftwareApplication

https://www.mypropops.com/#app

The Neutral Bridge

CreativeWork

https://www.theneutralbridge.com/#work

Guard-Clause

DefinedTermSet

https://www.guard-clause.com/#method

Evenfield

SoftwareApplication

https://www.evenfield.io/#app

H.U.N.I.E.

SoftwareApplication

https://www.hunie.ai/#app

AI Presence

SoftwareApplication

https://www.ai-presence.app/#app

Governance Rules

  • 01Canonical names are locked. No variations — including abbreviations, platform suffixes, or shorthand — are permitted on any surface.
  • 02Canonical @ids are stable. They must not change unless the entity's primary domain changes, and any change requires updating all referencing schema across every domain.
  • 03Schema type is fixed per entity. Type changes require explicit governance review — not editorial judgement.
  • 04Canonical descriptions must match between schema and page copy. Divergence between machine-readable and human-readable definitions counts as fragmentation.
  • 05New entities may not be added without a complete registry entry — name, @id, type, and description — before any page references them.
  • 06Deprecated entities may not be reused or reassigned. If an entity is retired, its canonical name, canonical @id, and historical references must remain reserved to prevent collision or identity drift.

Related