docs: add AI Visibility Unified Framework v1, Artifact A/B templates, GLOSSARY additions

docs/GLOSSARY.md

@@ -204,4 +204,81 @@ Shared surfaces declare a primary owner. Secondary domains may observe but do no
 
 ---
 
+---
+
+## From Unified Framework v1 Convergence (2026-08-06)
+
+These entries formalize terminology decided across Decisions 1–8 of DOP-AI-Visibility-Unified-Framework-v1.md.
+
+## Artifact A — Diagnostic Record
+
+Layer 1/2 deliverable. Contains diagnosis only. No solution language in authored narrative fields (executive summary, observation narrative, competitor observation summaries). Raw evidence (prompt text, engine output, source titles, quoted business names) is exempt from the banned-word gate. Does not duplicate data-inventory-v1.md or threat-register-v1.md — feeds findings into those files' existing schemas instead. Never reaches a client raw — internal evidentiary backing only. Governed by field-scoped banned-language QA gate + human review.
+
+## Artifact B — Strategy and Remediation Brief
+
+Layer 3+ deliverable. Translates threat-register-v1.md findings (via the Opportunity Matrix) into revenue scenarios, package recommendation, and measurement windows. Does not duplicate requirements-v1.md or workflows-v1.md — feeds action items into those by entry ID instead. Prescriptive by design — the only place solution/recommendation language belongs.
+
+## Severity
+
+A diagnostic classification of how serious a problem is. Lives in Artifact A. Values: Critical, Major, Minor.
+
+## Priority
+
+A prescriptive classification of how urgently an action should be taken. Lives in Artifact B. Values: Fix Now, Fix Soon, Monitor. Do not conflate with Severity — a Critical diagnosis and a Fix Now priority are different fields answering different questions.
+
+## Tier 1 — Verified
+
+A fact verified by the appropriate authority. Verification authority differs by fact class:
+- Business-entity facts (name, phone, address, hours, services, categories): requires owner confirmation or owner-access verification.
+- Audit-run facts (prompt executed, engine captured, timestamp, raw output stored): requires stored filesystem/git/database evidence. Verifies the audit *event* occurred, not that a business fact inside it is true.
+- Public claims inside AI outputs: default Tier 2 until owner confirmation upgrades it (see Tier 2).
+
+Same terminology as "Verified" in Module A — one scale, no separate axis.
+
+## Tier 2 — Indicative
+
+A fact or observation derived from public sources, inference, or unverified signals. Public observation defaults to Tier 2 until upgraded by stronger verification. Same terminology as "Indicative" in Module A.
+
+## Core Visibility Index
+
+Quantitative component of the Visibility Score, 0–70 points, lives in Artifact A. Composed of directly countable audit observations only: Mention rate (35), Mention strength/position (20), Description accuracy (15). Never blended with qualitative indicators into a single false-precision number without disclosure.
+
+## Directional Context Indicators
+
+Tier 2 qualitative signals reported separately from the Core Visibility Index: Source/citation quality, Competitor observation share, Engine variance. Disclosed as indicative, not measured market share.
+
+## Owner-Verified Correction Plan
+
+A Layer 1b (owner-access verification) artifact, not Layer 4 — corrected after cross-check against path-to-poc-sequencing.md and requirements-template.md. Layer 4's actual deliverable is requirements-v1.md (outcome statements, linked Threat ID, pricing-band ceiling). The Correction Plan fills a documentation gap in Layer 1b's exit criteria: canonical business name and public name, canonical NAP/service-area definition, primary + secondary geography, canonical phone/website, owner-verified service list, high-ticket priority services, capacity constraints, access matrix, access method and expiry, approval boundaries, no-change zones, change intake channel, V1 platform scope, definition of "setup complete." Definition of done: all fields Tier 1, access tested not just requested, approval boundaries acknowledged in writing.
+
+## Execution Card
+
+A constrained agent task definition with fixed trigger conditions, allowed inputs, forbidden actions, deterministic output format, human approval gate, and required completion evidence. No free-form reasoning permitted unless a skill has been explicitly promoted (see Promotion Gate). Working precedent: the GBP cold-audit pattern (Leonard fires only fixed rules R1–R3).
+
+## Promotion Gate
+
+The measurable threshold a skill must clear before moving from execution-card-constrained to higher autonomy: ≥5 scored runs in the task reliability ledger, ≥80% at Benchmark quality (9–10, zero scope violations), ≥4 consecutive weeks with zero fabrication/self-report incidents, and ≥3 clients engaged (i.e., past pure PoC). Evaluated per-skill, never as a blanket switch.
+
+## Restraint Principle
+
+A design principle: stable signals should not be changed unnecessarily. Freshness is not the same as activity. Over-editing has a cost — applies especially to Phase B / ongoing monitoring work.
+
+## Exposure Craft
+
+In-scope V1 work: platform category selection, attributes, service listing fields, structured short descriptions constrained by platform fields, Q&A seeded from owner-verified facts, schema properties from owner-verified data, canonical NAP enforcement, listing-field language matching customer search terms. Explicitly distinct from Content Marketing (out of scope per README V1 Scope Exclusions): open-ended copywriting, blog content, content strategy, brand narrative, social media production, paid ad copy, website redesign copy.
+
+## Path to PoC vs. Client Lifecycle Stages
+
+Path to PoC (Layers 1–7) is the authoritative internal engagement sequence, verified against `path-to-poc-sequencing.md` (pulled from main 2026-08-06). Client Lifecycle Stages (0–10) is client-facing narrative language layered on top. Bridge map (verified, no longer a working hypothesis):
+
+| Stage | Layer(s) |
+|---|---|
+| 0–1 | Pre-Layer 1 |
+| 2 | Layer 1a + 2 |
+| 3 | Layer 3 (non-skippable) |
+| 4 | Layer 1b + Layer 4 (owner-access verification *and* requirements — both land here) |
+| 5 | Layer 5 + 6 + 7 (POC Delivery belongs here, not Stage 6) |
+| 6 | Re-run of Layer 1–2 tooling (second diagnostic pass, not delivery) |
+| 7–10 | Post-PoC operations |
+
 **End of Glossary**