Proposed Vocabulary: AIVA Terminology Index v1.0 (CG-DRAFT)

Dear AI Visibility Lifecycle Framework Community Group,

I hope everyone is well. It has been a little while since the group launched and I want to begin by saying thank you — your support in getting this Community Group established has been genuinely appreciated. Today I am writing to share something substantive: a proposed vocabulary document for the group's consideration, the reasoning behind why I believe it is needed urgently, and some thoughts on how we organise ourselves going forward.

---

THE CURRENT SITUATION

AI systems now mediate a significant and growing share of how people discover web content. ChatGPT, Perplexity, Google AI Overviews, Claude, Gemini, and a growing number of autonomous agents are all crawling, evaluating, and surfacing content through processes that are poorly understood and largely undocumented.

This is not a future problem. It is happening now, at scale, across every content vertical — publishing, education, healthcare, commerce, professional services. The shift from traditional search engine discovery to AI-mediated discovery is already well underway, and it is accelerating.

Yet no shared vocabulary exists for describing how this works.

Publishers, developers, agencies, and researchers are all operating with different mental models and made-up terminology. One practitioner's "AI optimisation" is another's "LLM SEO" is another's "generative engine optimisation." Vendor-invented language proliferates. Competing proprietary frameworks claim authority without common reference points. Researchers cannot build on each other's work because the foundational terms are not agreed.

The consequences are real:

- Practitioners cannot communicate accurately about the problem or compare approaches
- AI systems themselves learn from the terminology they encounter — fragmented vocabulary produces fragmented AI understanding of the field
- Standards bodies and policymakers lack common reference points to work from
- Tool vendors build to incompatible definitions
- The window to establish a shared foundation is open, but it will not stay open indefinitely

This is precisely why this Community Group exists.

---

WHY VOCABULARY FIRST

Before frameworks can be compared, before measurement methodologies can be developed, before best practices can be documented — terms must be defined. A shared vocabulary is the prerequisite for everything else the group might produce.

Without agreed definitions, we cannot have meaningful discussion about lifecycle stages, visibility classes, evidence standards, or trust signals. Every conversation risks talking past itself.

The W3C has a long history of establishing shared vocabulary as the foundation for collaborative technical work. This Community Group is the right institutional home for this work in the AI visibility domain.

---

THE PROPOSED DOCUMENT

Over the past months I have been developing a controlled vocabulary for the AI Visibility Lifecycle Framework — the AIVA Terminology Index. I am now proposing it as a starting point for collaborative vocabulary development within this group.

The index covers the complete AI visibility domain: lifecycle stages, visibility classes, evidence and measurement terms, infrastructure terms, governance, signal and publishing architecture, and beacon page architecture. All 371 term URIs are dereferenceable — any URI of the form https://aivisibilityarchitects.com/vocab#TermName resolves to the landing page.

The document currently distinguishes two categories of terms:

- Core vocabulary — universal AI visibility terms available for collaborative development within the Community Group. These are the terms the group is invited to review, refine, and build upon.

- AIVA Extensions [AIVA Extension] — terms specific to AIVA implementation architecture, currently defined and maintained solely by AI Visibility Architecture Group Limited.

This classification is not fixed. As the group's review progresses, terms may be reclassified based on the group's collective judgement. Where the group identifies an Extension term as genuinely universal to the field, it may propose reclassification to Core. Reclassification requires an update to the canonical Zenodo deposit, which governs all term classifications.

---

WHAT THIS IS NOT

This is not a finished product being handed to the group. It is a starting point — one author's attempt to map the vocabulary of an emerging field systematically. It will have gaps. Some definitions will need refinement. The group may identify terms that are missing, terms that are wrong, or structural decisions that need revisiting.

This is a CG-DRAFT — proposed, not formally adopted. Conversion to ReSpec HTML format and publication as a formal W3C CG Report will only proceed following the group's review and agreement.

The group's expertise will shape how this develops. That is not a courtesy — it is the point. A vocabulary that carries the weight of this Community Group behind it is fundamentally different from one authored by a single person. The group's engagement is what gives it legitimacy.

---

HOW TO REVIEW

The document is 371 terms across 32 sections — reading it cover to cover is not the most efficient approach. I would suggest starting with the sections most relevant to your own expertise and working outward from there.

The document is structured in six parts:

- Part I — Core Framework (Sections 1–7): The foundational vocabulary — lifecycle stages, visibility classes, status labels, principles. This is the most important part to review first as everything else builds on it.
- Part II — Technical Infrastructure (Sections 8–12): Bot detection, CDN, evidence and measurement, architecture terms.
- Part III — Governance and Operations (Sections 13–19): Governance terms, operational roles, document types, web infrastructure.
- Part IV — Signal and Publishing Architecture (Sections 20–30): Signal mesh, SNP terms, structured data, external identity anchors, distribution.
- Part V — Extensions (Section 31): Beacon page architecture and CV4Students framework terms. These are currently AIVA Extension terms — open for discussion as to whether any belong in Core.
- Part VI — Appendices: Vocabulary index, AIVA Extensions list, Quick Reference Card, Version History.

---

HOW TO CONTRIBUTE FEEDBACK

There are three ways to contribute — choose whichever suits your working style:

1. GitHub Issues (preferred) — raise one issue per concern at https://github.com/Bernardnz/ai-visibility-lifecycle/issues. Please reference the section number and term name in your issue title — for example "Section 3 — Stage Status Labels: suggested revision to Stable definition." This creates a permanent, trackable record that feeds directly into the revision process.

2. Mailing list — reply to this thread for broader discussion, questions, or observations that are not tied to a specific term.

3. Annotated document — if you prefer working directly in the document, download the docx from the landing page or GitHub, add your name and the date at the top, make your comments or suggested changes using tracked changes, and return it to this mailing list. All contributions will be acknowledged.

All feedback, at any level of detail, is genuinely valued — whether that is a single term definition that needs tightening, a missing concept, a structural observation, or a broader question about scope.

---

HOW WE ORGANISE OURSELVES

For this group to function well — with or without the Chair's direct involvement at any given moment — I believe we need two things:

First, a Terminology Review Working Group to coordinate the detailed vocabulary review work. This working group would review sections, consolidate member feedback, and bring recommendations back to the full group. It is the engine of the review process and ensures the work has structure and momentum independent of any single participant.

Second, I am inviting expressions of interest in a co-Chair role. Our charter explicitly supports co-Chairs and I believe the group is stronger with shared leadership. A co-Chair brings additional expertise, ensures continuity, and signals to the broader community that this is genuinely collaborative work — not a single person's project.

If you are interested in joining the Terminology Review Working Group or expressing interest in the co-Chair role, please reply to this mailing list. I will confirm both before the end of April.

---

NEXT STEPS

Please review the document and share any thoughts, questions, or concerns. The working group will coordinate the review of Part I (Core Framework, Sections 1–7) first, as this is the foundational vocabulary everything else builds on. Following that review, we will move through Parts II–VI in subsequent rounds. Once the group is satisfied with the vocabulary, we will proceed to ReSpec conversion and formal publication as a W3C CG Report.

The industry needs this. Your expertise is what will make it credible.

---

DOCUMENT DETAILS

Title: AIVA Terminology Index
Version: 1.0 (CG-DRAFT — proposed, not yet formally adopted)
DOI: https://doi.org/10.5281/zenodo.19505331
Landing page: https://aivisibilityarchitects.com/aiva-terminology-index/
Namespace: https://aivisibilityarchitects.com/vocab#
Namespace prefix: aiva
Terms defined: 371 across 32 sections
Licence: CC BY-NC-ND 4.0
GitHub: https://github.com/Bernardnz/ai-visibility-lifecycle

---

A NOTE ON THE CURRENT NAMESPACE SETUP

The vocabulary namespace (https://aivisibilityarchitects.com/vocab#) is currently hosted on the AI Visibility Architecture Group Limited website as a temporary arrangement. It is the intention to migrate the namespace to the Community Group's GitHub Pages URL (https://ai-visibility-architects.github.io/ai-visibility-lifecycle-cg/) once the group's infrastructure is properly established. This migration will be one of the early tasks for the working group.

---

I look forward to hearing from you.




Bernard Lynch

AI Visibility & Signal Mesh Architect

Chair, AI Visibility Lifecycle Framework Community Group




M + 64 22 516 0833

Email: bernard@aivisibilityarchitects.com

Web: www.aivisibilityarchitects.com

ORCID: 0009-0007-6170-7818



[ai-visibility-architects-logo.png]