Tony_tech/veripath
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: corrective overwrite GLOSSARY.md — add date stamp, Task Type uses check_id+remediation_class, add llm-indicative rule, add owner_surface/client_facing fields, add low_risk_fix to remediation class

Browse Source
This commit is contained in:
Leonard
2026-07-25 14:43:06 +00:00
parent 7386a0614a
commit e1bafbf8f1
1 changed files with 6 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/GLOSSARY.md
+6 -7
View File
@@ -1,8 +1,6 @@
# GLOSSARY.md
**Status**: Canonical
This is the single source of truth for all core terminology. Other documents must link here instead of redefining terms. Changes require an ADR citing motivating evidence.
**Status**: Canonical 2026-07-25 — This is the single source of truth for all core terminology. Other documents must link here instead of redefining terms. Changes require an ADR citing motivating evidence.
---
@@ -55,6 +53,7 @@ A finding that meets all of the following:
- Current within the defined freshness window (measured from capture time to the moment of client-facing use; default 7 days unless the check specifies otherwise)
May be presented to clients as a confirmed issue.
Findings produced by an LLM or any non-deterministic method are Indicative by definition, regardless of artifact quality.
### Indicative Evidence (Tier 2)
Sampled, directional, or probabilistic findings that suggest risk or opportunity but do not prove direct customer loss. Must always be labeled as directional. Cannot be upgraded to Verified without additional concrete evidence meeting the full Verified criteria (including deterministic method).
@@ -85,7 +84,7 @@ Any change that publishes to a client-facing surface requires explicit human app
### Client-Facing Surface
A surface that the client's customers or the public can see or interact with (GBP fields, review responses, Q&A, business descriptions, hours, phone numbers, booking links, website content, directory listings, citations).
An external_ai response surface is not client-facing.
external_ai is not client-facing.
### Owner Surface
The platform or system a Check targets (e.g., gbp, website).
@@ -110,7 +109,7 @@ Any Post-Publish Defect immediately revokes graduation for that Task Type.
A Task Type may only move from gated to auto-approved after a documented reliability window of human reviews with agreement ≥ X% and zero Post-Publish Defects. Criteria are set in an ADR. Graduation is per Task Type and is immediately revoked on any Post-Publish Defect.
### Task Type
A unique pair of Owner + Surface. Graduation and revocation operate at this granularity only.
A unique pair of check_id + remediation_class. Graduation and revocation operate at this granularity only.
### Proof-of-Concept Fix
A single, high-leverage, low-risk correction performed (with explicit approval) during the initial assessment phase to demonstrate value before a retainer is offered. Typical examples include correcting a broken booking URL or an incorrect GBP phone number.
@@ -123,13 +122,13 @@ A client-facing document that shows the state of specific Findings before and af
## Check System Terms
### Check
A declarative test defined in specifications/checks/. Every Check must declare: id, domain, requires_human_approval (boolean), remediation_class, evidence_type, freshness_days.
A declarative test defined in specifications/checks/. Every Check must declare: id, domain, requires_human_approval (boolean), owner_surface, client_facing, remediation_class, evidence_type, freshness_days.
### Domain
One of: Customer Path Integrity, AI Visibility Integrity, Local Competitive Awareness. Must match the ownership table.
### Remediation Class
How a failing Check is expected to be addressed: automated, guided, manual, or referral (blocked / out-of-scope).
How a failing Check is expected to be addressed: low_risk_fix, automated, guided, manual, or referral (blocked / out-of-scope).
---