The AVO Discipline, the OMG Protocol, the Authority Score, the Visibility Score, and the Practice Loop That Connects Them
How to read this document
This is the conceptual ground of AVO practice at Avonetiq. After reading Foundations, a team member understands what AVO is, why it exists, how the components relate, and what discipline they have joined when they practice it. This document is read once at onboarding and consulted occasionally afterward.
Foundations is the first of four documents in the AVO Internal Bible. The other three serve different purposes:
| Document | Use it for |
|---|---|
| Document 1: Foundations (this document) | Understanding what AVO is and why |
| Document 2: The OMG Action Playbook | Executing AVO work — daily reference |
| Document 3: The Datapoint Reference | Diagnosing AS findings — daily reference |
| Document 4: AVO in Practice — A Worked Engagement | Seeing how AVO operates over a full engagement |
This document does not contain calibration values (specific weights, thresholds, balance exponents). Calibration is engineering implementation detail and varies by deployment. This document teaches the discipline; calibration is documented separately in engineering references not part of this bible.
This document also does not specify time horizons for actions or stages of maturity. Operational time depends on team capacity, brand starting state, content production rate, category competitiveness, platform refresh cadence, and multilingual scope — variables this document teaches how to recognize. What this document does is teach the structural relationships: what comes before what, what depends on what, what must be true before something else is attempted. Practitioners apply that structure to their specific engagement context.
This document operates from the assumption that brands begin AVO engagement at AS ≈ 0, VS ≈ 0. Most brands Avonetiq onboards have not yet engineered for AI-mediated discovery in any deliberate way. Foundations therefore teaches the discipline from the beginning, surfacing prerequisites and dependencies that the public methodology paper acknowledges but does not exhaustively map.