Semantic AI Search.
Semantic AI search is the practice of structuring websites so people, search engines, answer engines, and AI agents can understand entities, relationships, definitions, evidence, and source-of-record pages by meaning, not only by keywords.
Yoav Fekete works on this domain. yoavfekete.com is the applied example.
§13.1 · definition
§13.2 · why it matters
AI systems now read alongside people.
AI systems are increasingly part of how public knowledge is found and summarized. A page should be clear to a human reader while also being easy for retrieval systems to parse and cite accurately.
Entities outlive pages.
A person, project, or invention is easier to understand when it has one stable source-of-record page, a clear type, and visible links to the related entities around it.
Relations carry the meaning.
"Yoav Fekete develops Clause", "NaadLabs builds the Harmonic Sitar", and "YoYo Sitar gives it performance context" are relationship claims. They should appear in visible prose, internal links, and conservative structured data.
§13.3 · approach
§13.4 · related systems & pages
Entity map
The canonical graph for this site: nodes, typed relations, and a written relationship table connecting the major public entities.
Yoav Fekete (person page)
The source-of-record page for Yoav Fekete as the root Person entity of this site, with distinct relationships to projects, systems, and adjacent identities.
Clause
A separate system entity connected to Yoav Fekete and AI-assisted software development, not collapsed into the person page.
Harmonic Sitar
An in-development music-technology invention with visible relationships to Yoav Fekete, NaadLabs, YoYo Sitar, robotics, and music technology.
§13.5 · working vocabulary
§13.6 · questions this domain opens
A site as a small knowledge graph
How can entity pages, relationship tables, canonical URLs, and visible evidence turn a small website into a source of record?
Writing for human readers and AI systems
How should definitions, headings, link text, and self-contained passages be written so they remain understandable when summarized or cited?
Don’t invent. Leave a gap.
Why is an honest missing field better than an invented credential, and how does that affect semantic credibility?