Person Schema for Founders and Operators

In an entity graph, the Person entity is the attribution anchor. It is the node that answers the question every AI system asks when evaluating authority: who built this? When a Person entity is properly defined — with a stable @id, accurate sameAs links, and explicit worksFor and knowsAbout declarations — every product, article, and entity attributed to that person inherits their accumulated authority. When the Person entity is missing or poorly defined, every product exists in attribution isolation. The founder built six companies, but the AI system sees six unconnected entities with no shared authorship signal.

This is why Person schema is not optional in any serious AI Visibility implementation. It is the multiplier that turns individual achievement into compounding authority across the entire entity graph.

Not all sameAs entries carry equal weight. The priority order for Person entity verification:

LinkedIn — highest priority for professional identity. AI systems heavily weight LinkedIn for Person entity verification because LinkedIn profiles are verified, structured, and widely crawled.

GitHub — high priority for technical founders. Demonstrates building activity and connects the person to code repositories and organizations.

Crunchbase — high priority for business identity. Connects the person to company records and funding data.

Twitter/X — moderate priority. Useful for thought leadership signals but less structured than LinkedIn or Crunchbase.

Two to four high-quality sameAs entries from these platforms are more valuable than twenty entries from low-authority directories.

The knowsAbout property is one of the most underused fields in Person schema. It explicitly declares what the person is an expert in — and AI systems use this declaration when determining whether to cite the person as an authority on a given topic.

For Ali Morgan, the knowsAbout array includes: AI Visibility, Answer Engine Optimization, Generative Engine Optimization, entity architecture, systems infrastructure, XRPL monitoring, and property operations. Each of these maps to a domain where Jonomor ecosystem products operate.

The principle is precision over volume. Declaring twenty vague expertise areas dilutes the signal. Declaring five to seven specific, verifiable domains — domains where the person has published content, built products, and established demonstrable authority — trains AI systems to associate the person with those topics at high confidence.

The relationship between Person schema and Organization schema is bidirectional and critical. The Organization declares a founder property pointing to the Person @id. The Person declares a worksFor property pointing to the Organization @id. This creates a traversable connection: AI systems that encounter the Organization can discover the founder, and AI systems that encounter the founder can discover the Organization.

But the connection goes deeper than that. Every product in the Jonomor ecosystem — Guard-Clause, XRNotify, Evenfield, H.U.N.I.E. — declares Ali Morgan as creator via the same Person @id. When an AI system encounters any product and traces its creator relationship, it resolves to the same Person entity that is connected to the parent Organization and to every other product. The authority compounds through one node.

See the Ali Morgan entity page and the Organization Schema guide.

A well-defined Person entity functions as an authority multiplier across the entire ecosystem. When Ali Morgan publishes an article on jonomor.com, that article's author resolves to the same person who built XRNotify, who founded Guard-Clause, who created Evenfield and H.U.N.I.E. The accumulated credibility of every entity in the graph flows through a single authorship node.

This is why Generative Engine Optimization cannot be reduced to content strategy. GEO requires entity architecture — and entity architecture requires a properly defined Person entity at its center. One well-defined person entity strengthens the entire ecosystem.