How They Work Together
Integration & Operating Model
1. Purpose of This Document
This document explains the relationship between AIVA (AI Visibility Architecture) and AI Stewardship™ — two distinct but integrated components of a complete AI visibility governance system.
Understanding this relationship is essential for:
- Organisations evaluating the service
- Teams implementing the methodology
- Practitioners training in the discipline
- Anyone reading AIVA or Stewardship documentation
2. The Fundamental Distinction
AIVA observes. AI Stewardship™ governs.
AIVA (AI Visibility Architecture)
What it is: A methodology and reporting system
What it does: Produces observable evidence about AI visibility conditions
Primary output: AIVA Visibility Reports and Visibility Index
Core function: State articulation — showing where visibility exists and doesn’t
AI Stewardship™
What it is: A governance service and authority model
What it does: Interprets evidence, determines eligibility, provides direction
Primary output: AI Stewardship™ Overview Reports and AES determinations
Core function: Governance — preserving architectural eligibility over time
3. The Integration Model
AIVA and AI Stewardship™ operate as a three-layer system, with each layer building on the one below.
Layer 1 — Infrastructure (Foundation)
Your existing infrastructure — CloudFlare, Akamai, AWS, or similar platforms — produces live reports showing how AI systems interact with your digital presence. This is raw data: bot traffic, crawl patterns, cache behaviour, delivery metrics.
Layer 2 — AIVA (Observability)
AIVA maps infrastructure reports to the 11-stage AI Visibility Lifecycle. It transforms raw data into structured visibility reports showing the status of each stage — Stable, Constrained, Residual, Inactive, or Unresolved. AIVA observes and reports. It does not interpret or recommend.
Layer 3 — AI Stewardship™ (Governance)
AI Stewardship™ sits above AIVA. It interprets the evidence AIVA produces, determines your AI Architectural Eligibility Status (AES), and provides governance direction. Stewardship preserves eligibility over time. It governs; it does not implement.
The flow is always upward: Infrastructure → AIVA → AI Stewardship™ → Organisation
4. How Data Flows
- Infrastructure produces live reports (CloudFlare, Akamai, etc.)
- AIVA maps reports to lifecycle stages using the 11-stage framework
- AIVA produces Visibility Reports showing stage status
- AI Stewardship™ interprets AIVA outputs in architectural context
- Stewardship determines AES (Eligible-Stable, At Risk, Ineligible)
- Stewardship provides governance direction to the organisation
5. Terminology Mapping
AIVA and AI Stewardship™ use related but distinct terminology:
| Concept | AIVA Term | Stewardship Term |
|---|---|---|
| Overall status | Visibility Profile / Visibility Index | AI Architectural Eligibility Status (AES) |
| Per-stage status | Stage Status Labels (Stable, Constrained, Residual, Inactive, Unresolved) | Used as inputs to AES determination |
| Primary output | AIVA Visibility Report | AI Stewardship™ Overview Report |
| Framework | 11-Stage AI Visibility Lifecycle | Same — shared framework |
| Human role | AI Visibility Architect | AI Stewardship™ Authority |
6. What Each System Does NOT Do
AIVA Does NOT:
- Determine eligibility (that’s Stewardship)
- Provide governance direction (that’s Stewardship)
- Make recommendations (observation only)
- Judge success or failure (state articulation only)
AI Stewardship™ Does NOT:
- Produce raw visibility evidence (that’s AIVA)
- Map infrastructure reports (that’s AIVA)
- Implement systems (that’s Practitioners)
- Guarantee outcomes (governance only)
7. The Complete Operating Chain
Together, AIVA and AI Stewardship™ form a complete operating chain with clear responsibilities at each level.
Layer 1 — AIVA System
- Produces governed AI visibility reports
- Enforces disciplined language and framing
- Separates observation from inference
- Produces auditable, comparable outputs
Layer 2 — AI Stewardship™ Authority (Human Professional)
- Reads and audits AIVA reports
- Compares results over time
- Identifies patterns and anomalies
- Interprets without fabricating causality
- Determines AES and provides governance direction
- Signs off with professional responsibility
Layer 3 — End User / Organisation (Decision Maker)
- Receives signed, interpreted reports
- Understands what changed and why
- Decides what to act on
- Takes organisational responsibility
8. Canonical Statement
AIVA is the observability methodology that produces evidence.
AI Stewardship™ is the governance layer that interprets evidence and preserves eligibility.
Neither substitutes for the other. Together they form a complete governance system.
ACCESS AND SCOPE NOTICE
Detailed methodologies for AI visibility measurement, architectural frameworks, and diagnostic practices are maintained separately. This paper describes the structural gap — not the operational response.
Public documentation describes what is happening, not how to address it.
Framework Developer: Bernard Lynch, Founder of CV4Students.com, AI Visibility & Signal Mesh Architect, Developer of the 11-Stage AI Visibility Lifecycle | AI Visibility Architecture Group Limited | Auckland, New Zealand
Canonical Source: Zenodo — DOI: 10.5281/zenodo.18460710
IETF Internet-Draft: draft-lynch-ai-visibility-lifecycle-00
W3C Community Group: AI Visibility Lifecycle Framework Community Group
License: Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International (CC BY-NC-ND 4.0)
AI Visibility Architecture Group Limited | Auckland, New Zealand