Free, open source blog writer for Claude Code. Researches current sources, writes answer-first posts for Google and AI answers, has an independent reviewer score each one out of 100 and ships only after five delivery gates. 32 skills, 30 /blog commands, 5 agents. Active development at AI-Marketing-Hub/claude-blog; public releases ship here.
Python agent-skillsaiai-citationsai-contentai-marketingai-marketing-hubblogblog-writingclaude-codeclaude-code-skillclaude-pluginclaude-skillcontent-creationcontent-optimizationcontent-strategyeeatgeomultilingualopen-sourceseo
fix(review): adapter citation integrity + schema validation + ledger + notes
Agrici Daniel63312db9c73e
diff --git a/examples/sample-vault/.raw/.manifest.json b/examples/sample-vault/.raw/.manifest.jsonindex c47f7ef..fddda73 100644--- a/examples/sample-vault/.raw/.manifest.json+++ b/examples/sample-vault/.raw/.manifest.json@@ -4,14 +4,14 @@"client": "sample-vault","client_name": "Sample Client","owner": "Daniel Agrici",- "created": "2026-07-06"+ "created": "2026-07-07"}],"sources": [{"path": ".raw/sources/sample-source.md","sha256": "9927f31d619695c9e6d81a2696f3ef83e1fbdffc733a40ba2bfbbb39bd89a8dc",- "retrieved": "2026-07-06",+ "retrieved": "2026-07-07","source_type": "fixture"}]diff --git a/examples/sample-vault/_templates/decision.md b/examples/sample-vault/_templates/decision.mdindex 8b56edd..1d87809 100644--- a/examples/sample-vault/_templates/decision.md+++ b/examples/sample-vault/_templates/decision.md@@ -1,8 +1,8 @@---type: "decision"title: "{{title}}"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "proposed"---diff --git a/examples/sample-vault/_templates/source-note.md b/examples/sample-vault/_templates/source-note.mdindex 78b161a..a1541be 100644--- a/examples/sample-vault/_templates/source-note.md+++ b/examples/sample-vault/_templates/source-note.md@@ -1,8 +1,8 @@---type: "source"title: "{{title}}"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "draft"---diff --git a/examples/sample-vault/_templates/standard-note.md b/examples/sample-vault/_templates/standard-note.mdindex 79a8cfe..a70126f 100644--- a/examples/sample-vault/_templates/standard-note.md+++ b/examples/sample-vault/_templates/standard-note.md@@ -1,8 +1,8 @@---type: "note"title: "{{title}}"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "draft"---@@ -18,4 +18,4 @@ Write the current sourced truth here.## Timeline-- 2026-07-06 - Note created.+- 2026-07-07 - Note created.diff --git a/examples/sample-vault/weekly-report.html b/examples/sample-vault/weekly-report.htmlindex 8f93da5..75e5b46 100644--- a/examples/sample-vault/weekly-report.html+++ b/examples/sample-vault/weekly-report.html@@ -1,7 +1,7 @@<!doctype html><meta charset='utf-8'><title>Weekly Report</title><body><p>type: "report"</p><p>title: "Weekly Report"</p>-<p>created: "2026-07-06"</p>-<p>updated: "2026-07-06"</p>+<p>created: "2026-07-07"</p>+<p>updated: "2026-07-07"</p><p>status: "draft"</p><h1>Weekly Report</h1><h2>Summary</h2>diff --git a/examples/sample-vault/wiki/accounts/_index.md b/examples/sample-vault/wiki/accounts/_index.mdindex 8a45953..0a9df7c 100644--- a/examples/sample-vault/wiki/accounts/_index.md+++ b/examples/sample-vault/wiki/accounts/_index.md@@ -1,8 +1,8 @@---type: "hub"title: "Accounts Hub"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/canvases/_index.md b/examples/sample-vault/wiki/canvases/_index.mdindex 71db02f..0e546bc 100644--- a/examples/sample-vault/wiki/canvases/_index.md+++ b/examples/sample-vault/wiki/canvases/_index.md@@ -1,8 +1,8 @@---type: "hub"title: "Canvases Hub"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/concepts/Best Practices Kernel.md b/examples/sample-vault/wiki/concepts/Best Practices Kernel.mdindex fc98c33..d7348fb 100644--- a/examples/sample-vault/wiki/concepts/Best Practices Kernel.md+++ b/examples/sample-vault/wiki/concepts/Best Practices Kernel.md@@ -1,8 +1,8 @@---type: "concept"title: "Best Practices Kernel"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/concepts/_index.md b/examples/sample-vault/wiki/concepts/_index.mdindex 0642c0a..3d68f6b 100644--- a/examples/sample-vault/wiki/concepts/_index.md+++ b/examples/sample-vault/wiki/concepts/_index.md@@ -1,8 +1,8 @@---type: "hub"title: "Concepts Hub"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/decisions/Approval Queue.md b/examples/sample-vault/wiki/decisions/Approval Queue.mdindex 9914a3c..9dfdd0b 100644--- a/examples/sample-vault/wiki/decisions/Approval Queue.md+++ b/examples/sample-vault/wiki/decisions/Approval Queue.md@@ -1,8 +1,8 @@---type: "decision"title: "Approval Queue"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/decisions/_index.md b/examples/sample-vault/wiki/decisions/_index.mdindex a53f8c6..e94ba19 100644--- a/examples/sample-vault/wiki/decisions/_index.md+++ b/examples/sample-vault/wiki/decisions/_index.md@@ -1,8 +1,8 @@---type: "hub"title: "Decisions Hub"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/deliverables/Action Roadmap.md b/examples/sample-vault/wiki/deliverables/Action Roadmap.mdindex 8aa79cf..e1d58ec 100644--- a/examples/sample-vault/wiki/deliverables/Action Roadmap.md+++ b/examples/sample-vault/wiki/deliverables/Action Roadmap.md@@ -1,8 +1,8 @@---type: "deliverable"title: "Action Roadmap"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "draft"---diff --git a/examples/sample-vault/wiki/deliverables/Health Scorecard.md b/examples/sample-vault/wiki/deliverables/Health Scorecard.mdindex 9a4ebca..dc758f8 100644--- a/examples/sample-vault/wiki/deliverables/Health Scorecard.md+++ b/examples/sample-vault/wiki/deliverables/Health Scorecard.md@@ -1,8 +1,8 @@---type: "deliverable"title: "Health Scorecard"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "draft"---@@ -12,7 +12,7 @@ status: "draft"| Source | Hash | Retrieved ||---|---|---:|-| `.raw/sources/sample-source.md` | `9927f31d6196` | 2026-07-06 |+| `.raw/sources/sample-source.md` | `9927f31d6196` | 2026-07-07 |## Current Readdiff --git a/examples/sample-vault/wiki/deliverables/_index.md b/examples/sample-vault/wiki/deliverables/_index.mdindex 325b31a..2b21a82 100644--- a/examples/sample-vault/wiki/deliverables/_index.md+++ b/examples/sample-vault/wiki/deliverables/_index.md@@ -1,8 +1,8 @@---type: "hub"title: "Deliverables Hub"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/entities/_index.md b/examples/sample-vault/wiki/entities/_index.mdindex ade845d..8694d5f 100644--- a/examples/sample-vault/wiki/entities/_index.md+++ b/examples/sample-vault/wiki/entities/_index.md@@ -1,8 +1,8 @@---type: "hub"title: "Entities Hub"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/experiments/_index.md b/examples/sample-vault/wiki/experiments/_index.mdindex 83c591a..cf5d32c 100644--- a/examples/sample-vault/wiki/experiments/_index.md+++ b/examples/sample-vault/wiki/experiments/_index.md@@ -1,8 +1,8 @@---type: "hub"title: "Experiments Hub"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/flows/Reporting Workflow.md b/examples/sample-vault/wiki/flows/Reporting Workflow.mdindex 0626c5b..7d4a505 100644--- a/examples/sample-vault/wiki/flows/Reporting Workflow.md+++ b/examples/sample-vault/wiki/flows/Reporting Workflow.md@@ -1,8 +1,8 @@---type: "flow"title: "Reporting Workflow"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/flows/Research Refresh Workflow.md b/examples/sample-vault/wiki/flows/Research Refresh Workflow.mdindex 846c07b..aba48c4 100644--- a/examples/sample-vault/wiki/flows/Research Refresh Workflow.md+++ b/examples/sample-vault/wiki/flows/Research Refresh Workflow.md@@ -1,8 +1,8 @@---type: "flow"title: "Research Refresh Workflow"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/flows/Source Intake Workflow.md b/examples/sample-vault/wiki/flows/Source Intake Workflow.mdindex 19420ca..08579fd 100644--- a/examples/sample-vault/wiki/flows/Source Intake Workflow.md+++ b/examples/sample-vault/wiki/flows/Source Intake Workflow.md@@ -1,8 +1,8 @@---type: "flow"title: "Source Intake Workflow"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/flows/Synthesis Workflow.md b/examples/sample-vault/wiki/flows/Synthesis Workflow.mdindex dc69a4a..528ef0f 100644--- a/examples/sample-vault/wiki/flows/Synthesis Workflow.md+++ b/examples/sample-vault/wiki/flows/Synthesis Workflow.md@@ -1,8 +1,8 @@---type: "flow"title: "Synthesis Workflow"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/flows/_index.md b/examples/sample-vault/wiki/flows/_index.mdindex 4edb8d8..8cf89be 100644--- a/examples/sample-vault/wiki/flows/_index.md+++ b/examples/sample-vault/wiki/flows/_index.md@@ -1,8 +1,8 @@---type: "hub"title: "Flows Hub"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/gaps/_index.md b/examples/sample-vault/wiki/gaps/_index.mdindex 8e5d9d3..78fd408 100644--- a/examples/sample-vault/wiki/gaps/_index.md+++ b/examples/sample-vault/wiki/gaps/_index.md@@ -1,8 +1,8 @@---type: "hub"title: "Gaps Hub"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/hot.md b/examples/sample-vault/wiki/hot.mdindex 26e62bb..8b6b803 100644--- a/examples/sample-vault/wiki/hot.md+++ b/examples/sample-vault/wiki/hot.md@@ -1,8 +1,8 @@---type: "hot"title: "Hot"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/index.md b/examples/sample-vault/wiki/index.mdindex 8a24984..a9f0707 100644--- a/examples/sample-vault/wiki/index.md+++ b/examples/sample-vault/wiki/index.md@@ -1,8 +1,8 @@---type: "index"title: "Index"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/log.md b/examples/sample-vault/wiki/log.mdindex ac1c43b..e5727e3 100644--- a/examples/sample-vault/wiki/log.md+++ b/examples/sample-vault/wiki/log.md@@ -1,8 +1,8 @@---type: "log"title: "Log"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---@@ -10,6 +10,6 @@ status: "active"Related: [[Hot]] | [[Index]] | [[Dashboard]]-- 2026-07-06 - Claude Blog Brain scaffolded.-- 2026-07-06 - Ingested source [[sample-source]] from `.raw/sources/sample-source.md`.-- 2026-07-06 - Synthesized source-cited starter deliverables.+- 2026-07-07 - Claude Blog Brain scaffolded.+- 2026-07-07 - Ingested source [[sample-source]] from `.raw/sources/sample-source.md`.+- 2026-07-07 - Synthesized source-cited starter deliverables.diff --git a/examples/sample-vault/wiki/meta/Start Here.md b/examples/sample-vault/wiki/meta/Start Here.mdindex 8332784..255d3b6 100644--- a/examples/sample-vault/wiki/meta/Start Here.md+++ b/examples/sample-vault/wiki/meta/Start Here.md@@ -1,8 +1,8 @@---type: "meta"title: "Start Here"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/meta/dashboard.md b/examples/sample-vault/wiki/meta/dashboard.mdindex 2b33a05..9dde085 100644--- a/examples/sample-vault/wiki/meta/dashboard.md+++ b/examples/sample-vault/wiki/meta/dashboard.md@@ -1,8 +1,8 @@---type: "dashboard"title: "Dashboard"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/overview.md b/examples/sample-vault/wiki/overview.mdindex 5168aec..bd71752 100644--- a/examples/sample-vault/wiki/overview.md+++ b/examples/sample-vault/wiki/overview.md@@ -1,8 +1,8 @@---type: "overview"title: "Overview"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/platforms/_index.md b/examples/sample-vault/wiki/platforms/_index.mdindex f433aa2..6c76143 100644--- a/examples/sample-vault/wiki/platforms/_index.md+++ b/examples/sample-vault/wiki/platforms/_index.md@@ -1,8 +1,8 @@---type: "hub"title: "Platforms Hub"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/questions/_index.md b/examples/sample-vault/wiki/questions/_index.mdindex 010304c..34cdcc1 100644--- a/examples/sample-vault/wiki/questions/_index.md+++ b/examples/sample-vault/wiki/questions/_index.md@@ -1,8 +1,8 @@---type: "hub"title: "Questions Hub"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/reports/Weekly Report.md b/examples/sample-vault/wiki/reports/Weekly Report.mdindex a776ddf..0fe1fea 100644--- a/examples/sample-vault/wiki/reports/Weekly Report.md+++ b/examples/sample-vault/wiki/reports/Weekly Report.md@@ -1,8 +1,8 @@---type: "report"title: "Weekly Report"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "draft"---diff --git a/examples/sample-vault/wiki/reports/_index.md b/examples/sample-vault/wiki/reports/_index.mdindex e7abb7c..d985849 100644--- a/examples/sample-vault/wiki/reports/_index.md+++ b/examples/sample-vault/wiki/reports/_index.md@@ -1,8 +1,8 @@---type: "hub"title: "Reports Hub"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/sources/Source Manifest Guide.md b/examples/sample-vault/wiki/sources/Source Manifest Guide.mdindex dfe6fbf..1587650 100644--- a/examples/sample-vault/wiki/sources/Source Manifest Guide.md+++ b/examples/sample-vault/wiki/sources/Source Manifest Guide.md@@ -1,8 +1,8 @@---type: "source"title: "Source Manifest Guide"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/sources/_index.md b/examples/sample-vault/wiki/sources/_index.mdindex d609d90..2aa5b82 100644--- a/examples/sample-vault/wiki/sources/_index.md+++ b/examples/sample-vault/wiki/sources/_index.md@@ -1,8 +1,8 @@---type: "hub"title: "Sources Hub"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"---diff --git a/examples/sample-vault/wiki/sources/sample-source.md b/examples/sample-vault/wiki/sources/sample-source.mdindex 23cfb99..e0c3e69 100644--- a/examples/sample-vault/wiki/sources/sample-source.md+++ b/examples/sample-vault/wiki/sources/sample-source.md@@ -1,8 +1,8 @@---type: "source"title: "sample-source"-created: "2026-07-06"-updated: "2026-07-06"+created: "2026-07-07"+updated: "2026-07-07"status: "active"sources: [".raw/sources/sample-source.md"]---@@ -13,7 +13,7 @@ sources: [".raw/sources/sample-source.md"]- Path: `.raw/sources/sample-source.md`- Hash: `9927f31d619695c9e6d81a2696f3ef83e1fbdffc733a40ba2bfbbb39bd89a8dc`-- Retrieved: 2026-07-06+- Retrieved: 2026-07-07- Type: fixture## Compiled Truthdiff --git a/references/source-ledger.json b/references/source-ledger.jsonindex 6b86fd7..dffec94 100644--- a/references/source-ledger.json+++ b/references/source-ledger.json@@ -854,7 +854,7 @@"source_type": "standards","retrieved": "2026-07-06","last_verified": "2026-07-06",- "published": "2026-04-25",+ "published": "2024-09-03","refresh_due": "2026-08-01","confidence": "high","section": "geo",@@ -865,7 +865,7 @@"A /llms.txt file to guide LLMs to primary content."],"source_pool": "Claude SEO Brain references/source-ledger.json",- "date": "2026-04-25"+ "date": "2024-09-03"},{"id": "sitemaps-org",@@ -1034,7 +1034,7 @@"source_type": "primary","retrieved": "2026-07-06","last_verified": "2026-07-06",- "published": "2026-04-25",+ "published": "2026-02-04","refresh_due": "2026-08-01","confidence": "high","section": "geo",@@ -1045,7 +1045,7 @@"Position-one CTR ~58% lower when an AI Overview is present (Dec 2025 data)."],"source_pool": "Claude SEO Brain references/source-ledger.json",- "date": "2026-04-25"+ "date": "2026-02-04"},{"id": "seoclarity-chatgpt",@@ -1054,7 +1054,7 @@"source_type": "primary","retrieved": "2026-07-06","last_verified": "2026-07-06",- "published": "2026-04-25",+ "published": "2025-11-20","refresh_due": "2026-08-01","confidence": "high","section": "geo",@@ -1065,7 +1065,7 @@"25% of top 1,000 ChatGPT-cited URLs have zero Google organic visibility."],"source_pool": "Claude SEO Brain references/source-ledger.json",- "date": "2026-04-25"+ "date": "2025-11-20"},{"id": "pew-ai",@@ -1094,7 +1094,7 @@"source_type": "primary","retrieved": "2026-07-06","last_verified": "2026-07-06",- "published": "2026-04-25",+ "published": "2025-12-15","refresh_due": "2026-08-01","confidence": "high","section": "geo",@@ -1105,7 +1105,7 @@"Presence and composition of AI Overviews across query types."],"source_pool": "Claude SEO Brain references/source-ledger.json",- "date": "2026-04-25"+ "date": "2025-12-15"},{"id": "statcounter",diff --git a/scripts/ingest_blog_input.py b/scripts/ingest_blog_input.pyindex df2bd52..2d0b5ff 100644--- a/scripts/ingest_blog_input.py+++ b/scripts/ingest_blog_input.py@@ -18,6 +18,13 @@ from pathlib import Pathfrom typing import Anyfrom urllib.parse import urlparse+try:+ from jsonschema import Draft7Validator as JsonSchemaDraft7Validator+ from jsonschema import FormatChecker as JsonSchemaFormatChecker+except ImportError: # pragma: no cover - exercised when optional dependency is absent.+ JsonSchemaDraft7Validator = None # type: ignore[assignment]+ JsonSchemaFormatChecker = None # type: ignore[assignment]+REPO = Path(__file__).resolve().parents[1]SCHEMA_PATH = REPO / "schemas" / "blog-post-input.schema.json"@@ -125,8 +132,133 @@ def read_json(path: str | Path) -> dict[str, Any]:return clean_structure(data)-def validate_input(data: dict[str, Any]) -> None:+def load_input_schema() -> dict[str, Any]:+ schema = json.loads(SCHEMA_PATH.read_text(encoding="utf-8"))+ if not isinstance(schema, dict):+ raise ValidationError(["blog post input schema root must be an object"])+ return schema+++def validate_against_schema(data: dict[str, Any]) -> list[str]:+ schema = load_input_schema()+ if JsonSchemaDraft7Validator is not None:+ format_checker = JsonSchemaFormatChecker() if JsonSchemaFormatChecker is not None else None+ validator = JsonSchemaDraft7Validator(schema, format_checker=format_checker)+ return dedupe_errors(+ [format_schema_error(error) for error in sorted(validator.iter_errors(data), key=schema_error_sort_key)]+ )+ return manual_schema_errors(data, schema)+++def schema_error_sort_key(error: Any) -> tuple[str, str]:+ path = ".".join(str(part) for part in error.absolute_path)+ return (path, str(error.message))+++def format_schema_error(error: Any) -> str:+ path = ".".join(str(part) for part in error.absolute_path)+ if error.validator == "required" and isinstance(error.instance, dict):+ missing = sorted(set(error.validator_value) - set(error.instance))+ if len(missing) == 1:+ key = f"{path}.{missing[0]}" if path else missing[0]+ return f"missing required key: {key}"+ if error.validator == "anyOf" and not path:+ return "one of body_markdown or body_html is required"+ prefix = f"{path}: " if path else ""+ return prefix + str(error.message)+++def manual_schema_errors(data: dict[str, Any], schema: dict[str, Any]) -> list[str]:errors: list[str] = []+ properties = schema.get("properties", {})+ for key in schema.get("required", []):+ if key not in data:+ errors.append(f"missing required key: {key}")+ unexpected = sorted(set(data) - set(properties))+ if unexpected:+ errors.append("unexpected keys: " + ", ".join(unexpected))+ if "body_markdown" not in data and "body_html" not in data:+ errors.append("one of body_markdown or body_html is required")++ check_string_fields(data, ("title", "url", "body_markdown", "body_html", "target_keyword", "locale", "platform", "published_at", "modified_at"), errors)+ if "frontmatter" in data:+ if not isinstance(data["frontmatter"], dict):+ errors.append("frontmatter must be an object")+ else:+ check_string_fields(data["frontmatter"], ("description", "author", "date", "dateModified", "category", "coverImage"), errors, "frontmatter")+ if "tags" in data["frontmatter"] and not is_string_list(data["frontmatter"]["tags"]):+ errors.append("frontmatter.tags must be an array of strings")+ if "secondary_keywords" in data and not is_string_list(data["secondary_keywords"]):+ errors.append("secondary_keywords must be an array of strings")+ if "author" in data:+ manual_author_schema_errors(data["author"], errors)+ if "sources" in data:+ manual_sources_schema_errors(data["sources"], errors)+ if "audit_findings" in data:+ manual_audit_finding_schema_errors(data["audit_findings"], errors)+ return dedupe_errors(errors)+++def check_string_fields(data: dict[str, Any], fields: tuple[str, ...], errors: list[str], prefix: str = "") -> None:+ for key in fields:+ if key in data and not isinstance(data[key], str):+ path = f"{prefix}.{key}" if prefix else key+ errors.append(f"{path} must be a string")+++def manual_author_schema_errors(author: Any, errors: list[str]) -> None:+ if not isinstance(author, dict):+ errors.append("author must be an object")+ return+ check_string_fields(author, ("name", "url", "bio"), errors, "author")+ if "sameAs" in author and not is_string_list(author["sameAs"]):+ errors.append("author.sameAs must be an array of strings")+++def manual_sources_schema_errors(sources: Any, errors: list[str]) -> None:+ if not isinstance(sources, list):+ errors.append("sources must be an array")+ return+ for index, source in enumerate(sources, start=1):+ if not isinstance(source, dict):+ errors.append(f"sources #{index} must be an object")+ continue+ for key in ("url", "title", "retrieved"):+ if key not in source:+ errors.append(f"sources #{index} missing {key}")+ check_string_fields(source, ("url", "title", "publisher", "published", "retrieved", "confidence"), errors, f"sources #{index}")+ if "supports_claims" in source and not is_string_list(source["supports_claims"]):+ errors.append(f"sources #{index} supports_claims must be an array of strings")+++def manual_audit_finding_schema_errors(findings: Any, errors: list[str]) -> None:+ if not isinstance(findings, list):+ errors.append("audit_findings must be an array")+ return+ for index, finding in enumerate(findings, start=1):+ if not isinstance(finding, dict):+ errors.append(f"audit_findings #{index} must be an object")+ continue+ for key in ("id", "category", "severity", "summary"):+ if key not in finding:+ errors.append(f"audit_findings #{index} missing {key}")+ check_string_fields(finding, ("id", "category", "severity", "summary", "recommendation", "source"), errors, f"audit_findings #{index}")+ if finding.get("severity") not in {"critical", "high", "medium", "low", None}:+ errors.append(f"audit_findings #{index} severity is invalid")+++def dedupe_errors(errors: list[str]) -> list[str]:+ seen: set[str] = set()+ deduped: list[str] = []+ for error in errors:+ if error not in seen:+ deduped.append(error)+ seen.add(error)+ return deduped+++def validate_input(data: dict[str, Any]) -> None:+ errors: list[str] = validate_against_schema(data)for key in REQUIRED_KEYS:if key not in data:errors.append(f"missing required key: {key}")@@ -161,7 +293,7 @@ def validate_input(data: dict[str, Any]) -> None:if "audit_findings" in data:validate_audit_findings(data["audit_findings"], errors)if errors:- raise ValidationError(errors)+ raise ValidationError(dedupe_errors(errors))def validate_author(author: Any, errors: list[str]) -> None:@@ -343,7 +475,7 @@ def normalize_blog_input(data: dict[str, Any], *, source_name: str, raw_bytes: bauthor = data.get("author", {}) or {}sources = data.get("sources", []) or []audit_findings = normalize_audit_findings(data.get("audit_findings", []) or [])- schema = json.loads(SCHEMA_PATH.read_text(encoding="utf-8"))+ schema = load_input_schema()input_bytes = raw_bytes if raw_bytes is not None else json.dumps(data, sort_keys=True).encode("utf-8")raw_lower = raw_body.lower()title = data["title"].strip()diff --git a/scripts/synthesize_blog_plan.py b/scripts/synthesize_blog_plan.pyindex 46ac31b..49fae35 100644--- a/scripts/synthesize_blog_plan.py+++ b/scripts/synthesize_blog_plan.py@@ -40,13 +40,6 @@ AUDIT_CATEGORY_MAP = {}AUDIT_PENALTY = {"critical": 28, "high": 18, "medium": 10, "low": 4}PRIORITY_ORDER = {"critical": 0, "high": 1, "medium": 2, "low": 3}-DEFAULT_CATEGORY_SOURCE = {- "content": ["g-helpful-content"],- "seo": ["g-helpful-content"],- "eeat": ["g-helpful-content", "g-qrg-full"],- "technical": ["g-mobile-first"],- "ai_citation": ["g-ai-features", "ziptie-aio-source-selection"],-}class SourceError(ValueError):@@ -121,7 +114,198 @@ def load_ingested(path: str | Path) -> dict[str, Any]:raise ValidationError(["ingested record missing keys: " + ", ".join(missing)])if data.get("schema") != "claude-blog-brain.ingested-blog-post.v1":raise ValidationError(["ingested record schema is not supported"])- return clean_structure(data)+ cleaned = clean_structure(data)+ validate_ingested_record(cleaned)+ return cleaned+++def validate_ingested_record(record: dict[str, Any]) -> None:+ errors: list[str] = []+ if record.get("schema") != "claude-blog-brain.ingested-blog-post.v1":+ errors.append("ingested record schema is not supported")+ require_string(record, "adapter", errors, required=True)+ input_data = require_object(record, "input", errors)+ provenance = require_object(record, "provenance", errors)+ require_object(record, "frontmatter", errors)+ require_object(record, "author", errors)+ dates = require_object(record, "dates", errors)+ content = require_object(record, "content", errors)+ signals = require_object(record, "signals", errors)+ require_list(record, "sources", errors)+ audit_findings = require_list(record, "audit_findings", errors)++ if input_data is not None:+ for key in ("title", "url", "target_keyword", "locale"):+ require_string(input_data, key, errors, required=True, prefix="input")+ require_string(input_data, "platform", errors, prefix="input")+ require_string_list(input_data, "secondary_keywords", errors, prefix="input")+ if provenance is not None:+ for key in ("input_name", "input_sha256", "body_sha256", "schema_path", "schema_id", "body_format", "source_url"):+ require_string(provenance, key, errors, required=True, prefix="provenance")+ require_int(provenance, "source_count", errors, required=True, prefix="provenance")+ require_int(provenance, "audit_finding_count", errors, required=True, prefix="provenance")+ if provenance.get("body_format") not in {"markdown", "html", None}:+ errors.append("provenance.body_format must be markdown or html")+ if dates is not None:+ require_string(dates, "published_at", errors, required=True, prefix="dates")+ require_string(dates, "modified_at", errors, required=True, prefix="dates")+ if content is not None:+ for key in ("body_text", "intro"):+ require_string(content, key, errors, required=True, prefix="content")+ require_int(content, "word_count", errors, required=True, prefix="content")+ headings = require_list(content, "headings", errors, prefix="content")+ sections = require_list(content, "sections", errors, prefix="content")+ require_string_list(content, "links", errors, prefix="content")+ validate_headings(headings, errors)+ validate_sections(sections, errors)+ if signals is not None:+ for key in (+ "has_meta_description",+ "has_author",+ "has_author_bio",+ "has_dates",+ "has_modified_date",+ "has_direct_intro_answer",+ "has_article_schema",+ "has_faq_schema",+ "has_canonical_tag",+ "has_noindex",+ "has_first_hand_evidence",+ ):+ require_bool(signals, key, errors, required=True, prefix="signals")+ require_int(signals, "meta_description_length", errors, required=True, prefix="signals")+ validate_audit_findings(audit_findings, errors)+ if errors:+ raise ValidationError(dedupe_errors(errors))+++def require_object(data: dict[str, Any], key: str, errors: list[str]) -> dict[str, Any] | None:+ if key not in data:+ errors.append(f"ingested record missing key: {key}")+ return None+ if not isinstance(data[key], dict):+ errors.append(f"{key} must be an object")+ return None+ return data[key]+++def require_list(data: dict[str, Any], key: str, errors: list[str], prefix: str = "") -> list[Any] | None:+ path = f"{prefix}.{key}" if prefix else key+ if key not in data:+ errors.append(f"ingested record missing key: {path}")+ return None+ if not isinstance(data[key], list):+ errors.append(f"{path} must be a list")+ return None+ return data[key]+++def require_string(+ data: dict[str, Any],+ key: str,+ errors: list[str],+ *,+ required: bool = False,+ prefix: str = "",+) -> None:+ path = f"{prefix}.{key}" if prefix else key+ if key not in data:+ if required:+ errors.append(f"ingested record missing key: {path}")+ return+ if not isinstance(data[key], str):+ errors.append(f"{path} must be a string")+++def require_string_list(data: dict[str, Any], key: str, errors: list[str], prefix: str = "") -> None:+ path = f"{prefix}.{key}" if prefix else key+ if key not in data:+ errors.append(f"ingested record missing key: {path}")+ return+ if not isinstance(data[key], list) or not all(isinstance(item, str) for item in data[key]):+ errors.append(f"{path} must be a list of strings")+++def require_int(+ data: dict[str, Any],+ key: str,+ errors: list[str],+ *,+ required: bool = False,+ prefix: str = "",+) -> None:+ path = f"{prefix}.{key}" if prefix else key+ if key not in data:+ if required:+ errors.append(f"ingested record missing key: {path}")+ return+ if not isinstance(data[key], int) or isinstance(data[key], bool):+ errors.append(f"{path} must be an integer")+++def require_bool(+ data: dict[str, Any],+ key: str,+ errors: list[str],+ *,+ required: bool = False,+ prefix: str = "",+) -> None:+ path = f"{prefix}.{key}" if prefix else key+ if key not in data:+ if required:+ errors.append(f"ingested record missing key: {path}")+ return+ if not isinstance(data[key], bool):+ errors.append(f"{path} must be a boolean")+++def validate_headings(headings: list[Any] | None, errors: list[str]) -> None:+ if headings is None:+ return+ for index, heading in enumerate(headings, start=1):+ if not isinstance(heading, dict):+ errors.append(f"content.headings #{index} must be an object")+ continue+ require_int(heading, "level", errors, required=True, prefix=f"content.headings #{index}")+ require_string(heading, "text", errors, required=True, prefix=f"content.headings #{index}")+++def validate_sections(sections: list[Any] | None, errors: list[str]) -> None:+ if sections is None:+ return+ for index, section in enumerate(sections, start=1):+ if not isinstance(section, dict):+ errors.append(f"content.sections #{index} must be an object")+ continue+ require_string(section, "heading", errors, required=True, prefix=f"content.sections #{index}")+ require_string(section, "opening", errors, required=True, prefix=f"content.sections #{index}")+ require_int(section, "word_count", errors, required=True, prefix=f"content.sections #{index}")+++def validate_audit_findings(findings: list[Any] | None, errors: list[str]) -> None:+ if findings is None:+ return+ for index, finding in enumerate(findings, start=1):+ if not isinstance(finding, dict):+ errors.append(f"audit_findings #{index} must be an object")+ continue+ for key in ("id", "category", "severity", "summary"):+ require_string(finding, key, errors, required=True, prefix=f"audit_findings #{index}")+ for key in ("recommendation", "source"):+ require_string(finding, key, errors, prefix=f"audit_findings #{index}")+ if finding.get("severity") not in {"critical", "high", "medium", "low", None}:+ errors.append(f"audit_findings #{index} severity is invalid")+++def dedupe_errors(errors: list[str]) -> list[str]:+ seen: set[str] = set()+ deduped: list[str] = []+ for error in errors:+ if error not in seen:+ deduped.append(error)+ seen.add(error)+ return dedupeddef load_source_index(path: str | Path = DEFAULT_LEDGER) -> dict[str, dict[str, Any]]:@@ -133,6 +317,8 @@ def load_source_index(path: str | Path = DEFAULT_LEDGER) -> dict[str, dict[str,def synthesize(record: dict[str, Any], *, ledger_path: str | Path = DEFAULT_LEDGER) -> dict[str, Any]:+ record = clean_structure(record)+ validate_ingested_record(record)source_index = load_source_index(ledger_path)quality = build_quality_read(record, source_index)geo = build_geo_readiness(record)@@ -428,8 +614,10 @@ def apply_audit_findings(for finding in record.get("audit_findings", []):category = AUDIT_CATEGORY_MAP.get(finding.get("category", ""), "content")severity = finding.get("severity", "low")- source_ids = audit_source_ids(finding, category, source_index)+ source_ids = audit_source_ids(finding, source_index)recommendation = finding.get("recommendation") or "Resolve the supplied audit finding before publication."+ if not source_ids:+ recommendation = mark_operator_supplied(recommendation)builders[category].add(finding=f"Input audit finding {finding.get('id')}: {finding.get('summary')}",recommendation=recommendation,@@ -442,13 +630,19 @@ def apply_audit_findings(def audit_source_ids(finding: dict[str, Any],- category: str,source_index: dict[str, dict[str, Any]],) -> list[str]:source = finding.get("source", "")if isinstance(source, str) and source in source_index:return [source]- return DEFAULT_CATEGORY_SOURCE.get(category, ["g-helpful-content"])+ return []+++def mark_operator_supplied(recommendation: str) -> str:+ marker = "operator-supplied (unverified)"+ if recommendation.lower().startswith(marker):+ return recommendation+ return f"{marker}: {recommendation}"def compute_geo_metrics(record: dict[str, Any]) -> dict[str, Any]:diff --git a/tests/test_blog_adapters.py b/tests/test_blog_adapters.pyindex 5b818f2..1c431ef 100644--- a/tests/test_blog_adapters.py+++ b/tests/test_blog_adapters.py@@ -13,7 +13,7 @@ sys.path.insert(0, str(ROOT / "scripts"))from ingest_blog_input import ValidationError, load_blog_input # noqa: E402from render_blog_report import render_markdown # noqa: E402-from synthesize_blog_plan import synthesize # noqa: E402+from synthesize_blog_plan import load_ingested, synthesize # noqa: E402FIXTURE = ROOT / "tests" / "fixtures" / "sample-blog-post.json"@@ -74,3 +74,41 @@ def test_blog_adapter_invalid_input_error(tmp_path: Path) -> None:assert "missing required key: title" in messageassert "one of body_markdown or body_html is required" in messageassert "url must be an absolute URI" in message+++def test_blog_adapter_rejects_wrong_typed_dates(tmp_path: Path) -> None:+ payload = json.loads(FIXTURE.read_text(encoding="utf-8"))+ payload["published_at"] = 20260610+ bad_input = tmp_path / "bad-date-blog-post.json"+ bad_input.write_text(json.dumps(payload), encoding="utf-8")++ with pytest.raises(ValidationError) as excinfo:+ load_blog_input(bad_input)++ assert "published_at must be a string" in str(excinfo.value)+++def test_blog_synthesis_rejects_missing_nested_fields(tmp_path: Path) -> None:+ record = load_blog_input(FIXTURE)+ del record["input"]["title"]+ bad_record = tmp_path / "bad-ingested.json"+ bad_record.write_text(json.dumps(record), encoding="utf-8")++ with pytest.raises(ValidationError) as excinfo:+ load_ingested(bad_record)++ assert "ingested record missing key: input.title" in str(excinfo.value)+++def test_unknown_audit_source_is_operator_supplied_uncited(tmp_path: Path) -> None:+ payload = json.loads(FIXTURE.read_text(encoding="utf-8"))+ payload["audit_findings"][0]["source"] = "operator-note"+ bad_source_input = tmp_path / "operator-source-blog-post.json"+ bad_source_input.write_text(json.dumps(payload), encoding="utf-8")++ plan = synthesize(load_blog_input(bad_source_input))+ recommendation = next(item for item in plan["prioritized_recommendations"] if item["id"] == "audit-geo-source-context")++ assert recommendation["source_ids"] == []+ assert recommendation["recommendation"].startswith("operator-supplied (unverified):")+ assert "operator-note" not in {source["id"] for source in plan["source_citations"]}diff --git a/wiki/briefs-outlines/Evidence Block Requirements.md b/wiki/briefs-outlines/Evidence Block Requirements.mdindex 5985837..afbd9cb 100644--- a/wiki/briefs-outlines/Evidence Block Requirements.md+++ b/wiki/briefs-outlines/Evidence Block Requirements.md@@ -37,7 +37,7 @@ source_urls:## SummaryEvidence Block Requirements is the spoke for define which claims need sources, dates, calculations, expert review, or caveats.Use it when [[SERP-Informed Briefs and Outlines]] needs a repeatable decision record before a brief, draft, score, or report moves forward.-The durable output is a evidence block checklist.+The durable output is an evidence block checklist.The success condition is that current and risky claims carry dated trustworthy sources before drafting.Keep the note advisory in V1 and route implementation to a human owner.diff --git a/wiki/clusters/Entity Extraction Workflow.md b/wiki/clusters/Entity Extraction Workflow.mdindex 2f08926..6f6125f 100644--- a/wiki/clusters/Entity Extraction Workflow.md+++ b/wiki/clusters/Entity Extraction Workflow.md@@ -38,7 +38,7 @@ source_urls:## SummaryEntity Extraction Workflow is the spoke for extract entities, salience, source names, and topic relationships before clustering.Use it when [[Semantic Topic Clusters]] needs a repeatable decision record before a brief, draft, score, or report moves forward.-The durable output is a entity extraction worksheet.+The durable output is an entity extraction worksheet.The success condition is that cluster decisions reflect entities and reader language rather than only keyword strings.Keep the note advisory in V1 and route implementation to a human owner.diff --git a/wiki/clusters/Internal Link Matrix.md b/wiki/clusters/Internal Link Matrix.mdindex d3f4d37..f31c8c6 100644--- a/wiki/clusters/Internal Link Matrix.md+++ b/wiki/clusters/Internal Link Matrix.md@@ -38,7 +38,7 @@ source_urls:## SummaryInternal Link Matrix is the spoke for assign hub to spoke, spoke to hub, and sibling links with descriptive anchors.Use it when [[Semantic Topic Clusters]] needs a repeatable decision record before a brief, draft, score, or report moves forward.-The durable output is a internal link matrix.+The durable output is an internal link matrix.The success condition is that links help readers move from broad context to precise support and back.Keep the note advisory in V1 and route implementation to a human owner.diff --git a/wiki/data-integrations/Credential Boundary Rules.md b/wiki/data-integrations/Credential Boundary Rules.mdindex 43b80eb..d81187e 100644--- a/wiki/data-integrations/Credential Boundary Rules.md+++ b/wiki/data-integrations/Credential Boundary Rules.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Credential Boundary Rules decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Credential Boundary Rules advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Credential Boundary Rules into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Credential Boundary Rules guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Credential Boundary Rules outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Credential Boundary Rules decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Credential Boundary Rules gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Credential Boundary Rules evidence is incomplete or outside this brain.## Related- [[Google Data Integrations]]diff --git a/wiki/data-integrations/Data Confidence Labels.md b/wiki/data-integrations/Data Confidence Labels.mdindex fadf988..39f98e9 100644--- a/wiki/data-integrations/Data Confidence Labels.md+++ b/wiki/data-integrations/Data Confidence Labels.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Data Confidence Labels decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Data Confidence Labels advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Data Confidence Labels into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Data Confidence Labels guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Data Confidence Labels outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Data Confidence Labels decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Data Confidence Labels gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Data Confidence Labels evidence is incomplete or outside this brain.## Related- [[Google Data Integrations]]diff --git a/wiki/data-integrations/First Party Versus Market Data.md b/wiki/data-integrations/First Party Versus Market Data.mdindex ff9743d..18cfe82 100644--- a/wiki/data-integrations/First Party Versus Market Data.md+++ b/wiki/data-integrations/First Party Versus Market Data.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: First Party Versus Market Data decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep First Party Versus Market Data advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn First Party Versus Market Data into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust First Party Versus Market Data guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in First Party Versus Market Data outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A First Party Versus Market Data decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for First Party Versus Market Data gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when First Party Versus Market Data evidence is incomplete or outside this brain.## Related- [[Google Data Integrations]]diff --git a/wiki/data-integrations/GA4 Blog Engagement Metrics.md b/wiki/data-integrations/GA4 Blog Engagement Metrics.mdindex 71c4fe0..3ef674e 100644--- a/wiki/data-integrations/GA4 Blog Engagement Metrics.md+++ b/wiki/data-integrations/GA4 Blog Engagement Metrics.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: GA4 Blog Engagement Metrics decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep GA4 Blog Engagement Metrics advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn GA4 Blog Engagement Metrics into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust GA4 Blog Engagement Metrics guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in GA4 Blog Engagement Metrics outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A GA4 Blog Engagement Metrics decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for GA4 Blog Engagement Metrics gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when GA4 Blog Engagement Metrics evidence is incomplete or outside this brain.## Related- [[Google Data Integrations]]diff --git a/wiki/data-integrations/GSC Search Analytics Query Plan.md b/wiki/data-integrations/GSC Search Analytics Query Plan.mdindex 4aa0e27..e5144b1 100644--- a/wiki/data-integrations/GSC Search Analytics Query Plan.md+++ b/wiki/data-integrations/GSC Search Analytics Query Plan.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: GSC Search Analytics Query Plan decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep GSC Search Analytics Query Plan advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn GSC Search Analytics Query Plan into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust GSC Search Analytics Query Plan guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in GSC Search Analytics Query Plan outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A GSC Search Analytics Query Plan decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for GSC Search Analytics Query Plan gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when GSC Search Analytics Query Plan evidence is incomplete or outside this brain.## Related- [[Google Data Integrations]]diff --git a/wiki/data-integrations/Generative AI Performance Reporting.md b/wiki/data-integrations/Generative AI Performance Reporting.mdindex dcc4076..c5fd169 100644--- a/wiki/data-integrations/Generative AI Performance Reporting.md+++ b/wiki/data-integrations/Generative AI Performance Reporting.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Generative AI Performance Reporting decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Generative AI Performance Reporting advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Generative AI Performance Reporting into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Generative AI Performance Reporting guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Generative AI Performance Reporting outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Generative AI Performance Reporting decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Generative AI Performance Reporting gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Generative AI Performance Reporting evidence is incomplete or outside this brain.## Related- [[Google Data Integrations]]diff --git a/wiki/data-integrations/Metric Export Schema.md b/wiki/data-integrations/Metric Export Schema.mdindex 6647472..f828787 100644--- a/wiki/data-integrations/Metric Export Schema.md+++ b/wiki/data-integrations/Metric Export Schema.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Metric Export Schema decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Metric Export Schema advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Metric Export Schema into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Metric Export Schema guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Metric Export Schema outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Metric Export Schema decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Metric Export Schema gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Metric Export Schema evidence is incomplete or outside this brain.## Related- [[Google Data Integrations]]diff --git a/wiki/data-integrations/Missing Data Disclosure.md b/wiki/data-integrations/Missing Data Disclosure.mdindex 4d10c85..b3b589c 100644--- a/wiki/data-integrations/Missing Data Disclosure.md+++ b/wiki/data-integrations/Missing Data Disclosure.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Missing Data Disclosure decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Missing Data Disclosure advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Missing Data Disclosure into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Missing Data Disclosure guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Missing Data Disclosure outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Missing Data Disclosure decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Missing Data Disclosure gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Missing Data Disclosure evidence is incomplete or outside this brain.## Related- [[Google Data Integrations]]diff --git a/wiki/data-integrations/Page URL Canonical Data Checks.md b/wiki/data-integrations/Page URL Canonical Data Checks.mdindex 855fe0f..3f369a8 100644--- a/wiki/data-integrations/Page URL Canonical Data Checks.md+++ b/wiki/data-integrations/Page URL Canonical Data Checks.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Page URL Canonical Data Checks decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Page URL Canonical Data Checks advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Page URL Canonical Data Checks into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Page URL Canonical Data Checks guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Page URL Canonical Data Checks outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Page URL Canonical Data Checks decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Page URL Canonical Data Checks gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Page URL Canonical Data Checks evidence is incomplete or outside this brain.## Related- [[Google Data Integrations]]diff --git a/wiki/data-integrations/Query Dimension Hygiene.md b/wiki/data-integrations/Query Dimension Hygiene.mdindex 0af2984..dcce929 100644--- a/wiki/data-integrations/Query Dimension Hygiene.md+++ b/wiki/data-integrations/Query Dimension Hygiene.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Query Dimension Hygiene decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Query Dimension Hygiene advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Query Dimension Hygiene into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Query Dimension Hygiene guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Query Dimension Hygiene outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Query Dimension Hygiene decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Query Dimension Hygiene gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Query Dimension Hygiene evidence is incomplete or outside this brain.## Related- [[Google Data Integrations]]diff --git a/wiki/data-integrations/Read Only Data Access Pattern.md b/wiki/data-integrations/Read Only Data Access Pattern.mdindex c0858ba..2c5e793 100644--- a/wiki/data-integrations/Read Only Data Access Pattern.md+++ b/wiki/data-integrations/Read Only Data Access Pattern.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Read Only Data Access Pattern decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Read Only Data Access Pattern advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Read Only Data Access Pattern into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Read Only Data Access Pattern guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Read Only Data Access Pattern outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Read Only Data Access Pattern decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Read Only Data Access Pattern gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Read Only Data Access Pattern evidence is incomplete or outside this brain.## Related- [[Google Data Integrations]]diff --git a/wiki/data-integrations/URL Inspection Evidence Plan.md b/wiki/data-integrations/URL Inspection Evidence Plan.mdindex 1f1bf5f..ab1a55f 100644--- a/wiki/data-integrations/URL Inspection Evidence Plan.md+++ b/wiki/data-integrations/URL Inspection Evidence Plan.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: URL Inspection Evidence Plan decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep URL Inspection Evidence Plan advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn URL Inspection Evidence Plan into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust URL Inspection Evidence Plan guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in URL Inspection Evidence Plan outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A URL Inspection Evidence Plan decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for URL Inspection Evidence Plan gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when URL Inspection Evidence Plan evidence is incomplete or outside this brain.## Related- [[Google Data Integrations]]diff --git a/wiki/distribution/AI Referral Reporting.md b/wiki/distribution/AI Referral Reporting.mdindex 38b4708..f20fd9f 100644--- a/wiki/distribution/AI Referral Reporting.md+++ b/wiki/distribution/AI Referral Reporting.md@@ -39,7 +39,7 @@ source_urls:## SummaryAI Referral Reporting is the spoke for separate AI referral traffic, AI feature impressions, and AI citation observations.Use it when [[Distribution and Repurposing]] needs a repeatable decision record before a brief, draft, score, or report moves forward.-The durable output is a AI referral report.+The durable output is an AI referral report.The success condition is that AI performance reporting uses available first-party data and visible caveats.Keep the note advisory in V1 and route implementation to a human owner.diff --git a/wiki/media/Alt Text Standards.md b/wiki/media/Alt Text Standards.mdindex 6b171af..873fb65 100644--- a/wiki/media/Alt Text Standards.md+++ b/wiki/media/Alt Text Standards.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Alt Text Standards decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Alt Text Standards advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Alt Text Standards into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Alt Text Standards guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Alt Text Standards outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Alt Text Standards decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Alt Text Standards gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Alt Text Standards evidence is incomplete or outside this brain.## Related- [[Images Audio and Charts]]diff --git a/wiki/media/Audio Summary Rules.md b/wiki/media/Audio Summary Rules.mdindex 7744186..2d05658 100644--- a/wiki/media/Audio Summary Rules.md+++ b/wiki/media/Audio Summary Rules.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Audio Summary Rules decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Audio Summary Rules advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Audio Summary Rules into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Audio Summary Rules guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Audio Summary Rules outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Audio Summary Rules decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Audio Summary Rules gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Audio Summary Rules evidence is incomplete or outside this brain.## Related- [[Images Audio and Charts]]diff --git a/wiki/media/Chart Source Requirements.md b/wiki/media/Chart Source Requirements.mdindex 93cb93f..0e12647 100644--- a/wiki/media/Chart Source Requirements.md+++ b/wiki/media/Chart Source Requirements.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Chart Source Requirements decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Chart Source Requirements advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Chart Source Requirements into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Chart Source Requirements guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Chart Source Requirements outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Chart Source Requirements decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Chart Source Requirements gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Chart Source Requirements evidence is incomplete or outside this brain.## Related- [[Images Audio and Charts]]diff --git a/wiki/media/Data Visualization Review.md b/wiki/media/Data Visualization Review.mdindex 14515cd..8b6f841 100644--- a/wiki/media/Data Visualization Review.md+++ b/wiki/media/Data Visualization Review.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Data Visualization Review decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Data Visualization Review advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Data Visualization Review into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Data Visualization Review guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Data Visualization Review outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Data Visualization Review decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Data Visualization Review gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Data Visualization Review evidence is incomplete or outside this brain.## Related- [[Images Audio and Charts]]diff --git a/wiki/media/Generated Media Disclosure Notes.md b/wiki/media/Generated Media Disclosure Notes.mdindex f6b2c55..f68a9e8 100644--- a/wiki/media/Generated Media Disclosure Notes.md+++ b/wiki/media/Generated Media Disclosure Notes.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Generated Media Disclosure Notes decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Generated Media Disclosure Notes advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Generated Media Disclosure Notes into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Generated Media Disclosure Notes guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Generated Media Disclosure Notes outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Generated Media Disclosure Notes decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Generated Media Disclosure Notes gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Generated Media Disclosure Notes evidence is incomplete or outside this brain.## Related- [[Images Audio and Charts]]diff --git a/wiki/media/Image Selection Rules.md b/wiki/media/Image Selection Rules.mdindex 5abecfd..e1bd7d8 100644--- a/wiki/media/Image Selection Rules.md+++ b/wiki/media/Image Selection Rules.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Image Selection Rules decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Image Selection Rules advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Image Selection Rules into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Image Selection Rules guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Image Selection Rules outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Image Selection Rules decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Image Selection Rules gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Image Selection Rules evidence is incomplete or outside this brain.## Related- [[Images Audio and Charts]]diff --git a/wiki/media/Image Sitemap Notes.md b/wiki/media/Image Sitemap Notes.mdindex 8de9990..f13355e 100644--- a/wiki/media/Image Sitemap Notes.md+++ b/wiki/media/Image Sitemap Notes.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Image Sitemap Notes decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Image Sitemap Notes advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Image Sitemap Notes into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Image Sitemap Notes guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Image Sitemap Notes outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Image Sitemap Notes decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Image Sitemap Notes gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Image Sitemap Notes evidence is incomplete or outside this brain.## Related- [[Images Audio and Charts]]diff --git a/wiki/media/Media Accessibility Checklist.md b/wiki/media/Media Accessibility Checklist.mdindex 3acabbc..1c7a343 100644--- a/wiki/media/Media Accessibility Checklist.md+++ b/wiki/media/Media Accessibility Checklist.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Media Accessibility Checklist decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Media Accessibility Checklist advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Media Accessibility Checklist into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Media Accessibility Checklist guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Media Accessibility Checklist outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Media Accessibility Checklist decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Media Accessibility Checklist gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Media Accessibility Checklist evidence is incomplete or outside this brain.## Related- [[Images Audio and Charts]]diff --git a/wiki/media/Media QA For Blog Posts.md b/wiki/media/Media QA For Blog Posts.mdindex 433497e..107ff92 100644--- a/wiki/media/Media QA For Blog Posts.md+++ b/wiki/media/Media QA For Blog Posts.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Media QA For Blog Posts decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Media QA For Blog Posts advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Media QA For Blog Posts into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Media QA For Blog Posts guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Media QA For Blog Posts outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Media QA For Blog Posts decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Media QA For Blog Posts gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Media QA For Blog Posts evidence is incomplete or outside this brain.## Related- [[Images Audio and Charts]]diff --git a/wiki/media/Media Repurposing Matrix.md b/wiki/media/Media Repurposing Matrix.mdindex ed42478..598cad4 100644--- a/wiki/media/Media Repurposing Matrix.md+++ b/wiki/media/Media Repurposing Matrix.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Media Repurposing Matrix decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Media Repurposing Matrix advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Media Repurposing Matrix into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Media Repurposing Matrix guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Media Repurposing Matrix outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Media Repurposing Matrix decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Media Repurposing Matrix gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Media Repurposing Matrix evidence is incomplete or outside this brain.## Related- [[Images Audio and Charts]]diff --git a/wiki/media/VideoObject Checklist.md b/wiki/media/VideoObject Checklist.mdindex 579335d..13191e7 100644--- a/wiki/media/VideoObject Checklist.md+++ b/wiki/media/VideoObject Checklist.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: VideoObject Checklist decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep VideoObject Checklist advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn VideoObject Checklist into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust VideoObject Checklist guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in VideoObject Checklist outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A VideoObject Checklist decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for VideoObject Checklist gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when VideoObject Checklist evidence is incomplete or outside this brain.## Related- [[Images Audio and Charts]]diff --git a/wiki/media/Visual Claim Review.md b/wiki/media/Visual Claim Review.mdindex 486d51a..edfb40c 100644--- a/wiki/media/Visual Claim Review.md+++ b/wiki/media/Visual Claim Review.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Visual Claim Review decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Visual Claim Review advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Visual Claim Review into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Visual Claim Review guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Visual Claim Review outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Visual Claim Review decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Visual Claim Review gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Visual Claim Review evidence is incomplete or outside this brain.## Related- [[Images Audio and Charts]]diff --git a/wiki/monitoring/2024 Google Update Timeline.md b/wiki/monitoring/2024 Google Update Timeline.mdindex 82b4135..97568da 100644--- a/wiki/monitoring/2024 Google Update Timeline.md+++ b/wiki/monitoring/2024 Google Update Timeline.md@@ -145,24 +145,24 @@ Third-party volatility can explain what to inspect, but it does not promote an e- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: 2024 Google Update Timeline decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep 2024 Google Update Timeline advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn 2024 Google Update Timeline into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust 2024 Google Update Timeline guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in 2024 Google Update Timeline outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A 2024 Google Update Timeline decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for 2024 Google Update Timeline gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when 2024 Google Update Timeline evidence is incomplete or outside this brain.## Related- [[Google Algorithm Update Ledger]]diff --git a/wiki/monitoring/2025 Google Update Timeline.md b/wiki/monitoring/2025 Google Update Timeline.mdindex 940c608..997d2d7 100644--- a/wiki/monitoring/2025 Google Update Timeline.md+++ b/wiki/monitoring/2025 Google Update Timeline.md@@ -144,24 +144,24 @@ Third-party volatility can explain what to inspect, but it does not promote an e- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: 2025 Google Update Timeline decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep 2025 Google Update Timeline advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn 2025 Google Update Timeline into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust 2025 Google Update Timeline guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in 2025 Google Update Timeline outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A 2025 Google Update Timeline decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for 2025 Google Update Timeline gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when 2025 Google Update Timeline evidence is incomplete or outside this brain.## Related- [[Google Algorithm Update Ledger]]diff --git a/wiki/monitoring/2026 Google Update Timeline.md b/wiki/monitoring/2026 Google Update Timeline.mdindex cc407d3..f96c8b2 100644--- a/wiki/monitoring/2026 Google Update Timeline.md+++ b/wiki/monitoring/2026 Google Update Timeline.md@@ -166,24 +166,24 @@ Third-party volatility can explain what to inspect, but it does not promote an e- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: 2026 Google Update Timeline decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep 2026 Google Update Timeline advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn 2026 Google Update Timeline into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust 2026 Google Update Timeline guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in 2026 Google Update Timeline outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A 2026 Google Update Timeline decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for 2026 Google Update Timeline gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when 2026 Google Update Timeline evidence is incomplete or outside this brain.## Related- [[Google Algorithm Update Ledger]]diff --git a/wiki/monitoring/AI Search Update Watch.md b/wiki/monitoring/AI Search Update Watch.mdindex 0bbc43f..71587ea 100644--- a/wiki/monitoring/AI Search Update Watch.md+++ b/wiki/monitoring/AI Search Update Watch.md@@ -99,24 +99,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: AI Search Update Watch decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep AI Search Update Watch advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn AI Search Update Watch into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust AI Search Update Watch guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in AI Search Update Watch outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A AI Search Update Watch decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for AI Search Update Watch gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when AI Search Update Watch evidence is incomplete or outside this brain.## Related- [[Google Algorithm Update Ledger]]diff --git a/wiki/monitoring/Confirmed Update Entry Template.md b/wiki/monitoring/Confirmed Update Entry Template.mdindex 9e63929..1de2510 100644--- a/wiki/monitoring/Confirmed Update Entry Template.md+++ b/wiki/monitoring/Confirmed Update Entry Template.md@@ -99,24 +99,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Confirmed Update Entry Template decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Confirmed Update Entry Template advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Confirmed Update Entry Template into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Confirmed Update Entry Template guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Confirmed Update Entry Template outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Confirmed Update Entry Template decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Confirmed Update Entry Template gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Confirmed Update Entry Template evidence is incomplete or outside this brain.## Related- [[Google Algorithm Update Ledger]]diff --git a/wiki/monitoring/Core Update Response Playbook.md b/wiki/monitoring/Core Update Response Playbook.mdindex 9e3b9b3..1aa08c2 100644--- a/wiki/monitoring/Core Update Response Playbook.md+++ b/wiki/monitoring/Core Update Response Playbook.md@@ -99,24 +99,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Core Update Response Playbook decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Core Update Response Playbook advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Core Update Response Playbook into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Core Update Response Playbook guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Core Update Response Playbook outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Core Update Response Playbook decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Core Update Response Playbook gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Core Update Response Playbook evidence is incomplete or outside this brain.## Related- [[Google Algorithm Update Ledger]]diff --git a/wiki/monitoring/Monitoring Confidence Labels.md b/wiki/monitoring/Monitoring Confidence Labels.mdindex 812a14a..d3bbba7 100644--- a/wiki/monitoring/Monitoring Confidence Labels.md+++ b/wiki/monitoring/Monitoring Confidence Labels.md@@ -99,24 +99,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Monitoring Confidence Labels decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Monitoring Confidence Labels advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Monitoring Confidence Labels into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Monitoring Confidence Labels guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Monitoring Confidence Labels outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Monitoring Confidence Labels decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Monitoring Confidence Labels gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Monitoring Confidence Labels evidence is incomplete or outside this brain.## Related- [[Google Algorithm Update Ledger]]diff --git a/wiki/monitoring/Monthly Source Refresh.md b/wiki/monitoring/Monthly Source Refresh.mdindex 26d1dfb..db40ef0 100644--- a/wiki/monitoring/Monthly Source Refresh.md+++ b/wiki/monitoring/Monthly Source Refresh.md@@ -99,24 +99,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Monthly Source Refresh decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Monthly Source Refresh advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Monthly Source Refresh into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Monthly Source Refresh guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Monthly Source Refresh outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Monthly Source Refresh decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Monthly Source Refresh gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Monthly Source Refresh evidence is incomplete or outside this brain.## Related- [[Google Algorithm Update Ledger]]diff --git a/wiki/monitoring/QRG Revision Watch.md b/wiki/monitoring/QRG Revision Watch.mdindex 4d6c7df..041ae71 100644--- a/wiki/monitoring/QRG Revision Watch.md+++ b/wiki/monitoring/QRG Revision Watch.md@@ -99,24 +99,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: QRG Revision Watch decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep QRG Revision Watch advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn QRG Revision Watch into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust QRG Revision Watch guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in QRG Revision Watch outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A QRG Revision Watch decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for QRG Revision Watch gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when QRG Revision Watch evidence is incomplete or outside this brain.## Related- [[Google Algorithm Update Ledger]]diff --git a/wiki/monitoring/Schema Deprecation Watch.md b/wiki/monitoring/Schema Deprecation Watch.mdindex 5b91741..bf53fa4 100644--- a/wiki/monitoring/Schema Deprecation Watch.md+++ b/wiki/monitoring/Schema Deprecation Watch.md@@ -99,24 +99,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Schema Deprecation Watch decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Schema Deprecation Watch advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Schema Deprecation Watch into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Schema Deprecation Watch guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Schema Deprecation Watch outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Schema Deprecation Watch decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Schema Deprecation Watch gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Schema Deprecation Watch evidence is incomplete or outside this brain.## Related- [[Google Algorithm Update Ledger]]diff --git a/wiki/monitoring/Spam Update Response Playbook.md b/wiki/monitoring/Spam Update Response Playbook.mdindex 892810a..63a3b3b 100644--- a/wiki/monitoring/Spam Update Response Playbook.md+++ b/wiki/monitoring/Spam Update Response Playbook.md@@ -99,24 +99,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Spam Update Response Playbook decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Spam Update Response Playbook advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Spam Update Response Playbook into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Spam Update Response Playbook guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Spam Update Response Playbook outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Spam Update Response Playbook decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Spam Update Response Playbook gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Spam Update Response Playbook evidence is incomplete or outside this brain.## Related- [[Google Algorithm Update Ledger]]diff --git a/wiki/monitoring/Unverified Volatility Quarantine.md b/wiki/monitoring/Unverified Volatility Quarantine.mdindex e1c6a8a..e5903b7 100644--- a/wiki/monitoring/Unverified Volatility Quarantine.md+++ b/wiki/monitoring/Unverified Volatility Quarantine.md@@ -99,24 +99,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Unverified Volatility Quarantine decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Unverified Volatility Quarantine advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Unverified Volatility Quarantine into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Unverified Volatility Quarantine guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Unverified Volatility Quarantine outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Unverified Volatility Quarantine decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Unverified Volatility Quarantine gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Unverified Volatility Quarantine evidence is incomplete or outside this brain.## Related- [[Google Algorithm Update Ledger]]diff --git a/wiki/monitoring/Update Impact Review.md b/wiki/monitoring/Update Impact Review.mdindex 7074af1..54e8676 100644--- a/wiki/monitoring/Update Impact Review.md+++ b/wiki/monitoring/Update Impact Review.md@@ -99,24 +99,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Update Impact Review decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Update Impact Review advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Update Impact Review into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Update Impact Review guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Update Impact Review outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Update Impact Review decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Update Impact Review gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Update Impact Review evidence is incomplete or outside this brain.## Related- [[Google Algorithm Update Ledger]]diff --git a/wiki/multilingual/Cross Locale Internal Linking.md b/wiki/multilingual/Cross Locale Internal Linking.mdindex 0bc3907..449627d 100644--- a/wiki/multilingual/Cross Locale Internal Linking.md+++ b/wiki/multilingual/Cross Locale Internal Linking.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Cross Locale Internal Linking decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Cross Locale Internal Linking advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Cross Locale Internal Linking into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Cross Locale Internal Linking guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Cross Locale Internal Linking outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Cross Locale Internal Linking decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Cross Locale Internal Linking gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Cross Locale Internal Linking evidence is incomplete or outside this brain.## Related- [[Multilingual Publishing]]diff --git a/wiki/multilingual/Hreflang Checklist.md b/wiki/multilingual/Hreflang Checklist.mdindex 465a11e..f3f2603 100644--- a/wiki/multilingual/Hreflang Checklist.md+++ b/wiki/multilingual/Hreflang Checklist.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Hreflang Checklist decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Hreflang Checklist advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Hreflang Checklist into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Hreflang Checklist guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Hreflang Checklist outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Hreflang Checklist decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Hreflang Checklist gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Hreflang Checklist evidence is incomplete or outside this brain.## Related- [[Multilingual Publishing]]diff --git a/wiki/multilingual/Locale Intent Research.md b/wiki/multilingual/Locale Intent Research.mdindex afca278..14145e3 100644--- a/wiki/multilingual/Locale Intent Research.md+++ b/wiki/multilingual/Locale Intent Research.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Locale Intent Research decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Locale Intent Research advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Locale Intent Research into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Locale Intent Research guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Locale Intent Research outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Locale Intent Research decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Locale Intent Research gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Locale Intent Research evidence is incomplete or outside this brain.## Related- [[Multilingual Publishing]]diff --git a/wiki/multilingual/Locale Launch QA.md b/wiki/multilingual/Locale Launch QA.mdindex 8bfd01e..ed733e5 100644--- a/wiki/multilingual/Locale Launch QA.md+++ b/wiki/multilingual/Locale Launch QA.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Locale Launch QA decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Locale Launch QA advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Locale Launch QA into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Locale Launch QA guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Locale Launch QA outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Locale Launch QA decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Locale Launch QA gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Locale Launch QA evidence is incomplete or outside this brain.## Related- [[Multilingual Publishing]]diff --git a/wiki/multilingual/Locale Review Workflow.md b/wiki/multilingual/Locale Review Workflow.mdindex dc26f57..9ed9319 100644--- a/wiki/multilingual/Locale Review Workflow.md+++ b/wiki/multilingual/Locale Review Workflow.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Locale Review Workflow decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Locale Review Workflow advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Locale Review Workflow into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Locale Review Workflow guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Locale Review Workflow outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Locale Review Workflow decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Locale Review Workflow gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Locale Review Workflow evidence is incomplete or outside this brain.## Related- [[Multilingual Publishing]]diff --git a/wiki/multilingual/Localized Source Requirements.md b/wiki/multilingual/Localized Source Requirements.mdindex 629ad6a..9044835 100644--- a/wiki/multilingual/Localized Source Requirements.md+++ b/wiki/multilingual/Localized Source Requirements.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Localized Source Requirements decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Localized Source Requirements advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Localized Source Requirements into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Localized Source Requirements guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Localized Source Requirements outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Localized Source Requirements decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Localized Source Requirements gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Localized Source Requirements evidence is incomplete or outside this brain.## Related- [[Multilingual Publishing]]diff --git a/wiki/multilingual/Machine Translation Risk Notes.md b/wiki/multilingual/Machine Translation Risk Notes.mdindex 9e0cdbc..0cee776 100644--- a/wiki/multilingual/Machine Translation Risk Notes.md+++ b/wiki/multilingual/Machine Translation Risk Notes.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Machine Translation Risk Notes decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Machine Translation Risk Notes advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Machine Translation Risk Notes into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Machine Translation Risk Notes guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Machine Translation Risk Notes outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Machine Translation Risk Notes decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Machine Translation Risk Notes gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Machine Translation Risk Notes evidence is incomplete or outside this brain.## Related- [[Multilingual Publishing]]diff --git a/wiki/multilingual/Multilingual Refresh Cadence.md b/wiki/multilingual/Multilingual Refresh Cadence.mdindex 1358086..e08562e 100644--- a/wiki/multilingual/Multilingual Refresh Cadence.md+++ b/wiki/multilingual/Multilingual Refresh Cadence.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Multilingual Refresh Cadence decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Multilingual Refresh Cadence advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Multilingual Refresh Cadence into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Multilingual Refresh Cadence guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Multilingual Refresh Cadence outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Multilingual Refresh Cadence decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Multilingual Refresh Cadence gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Multilingual Refresh Cadence evidence is incomplete or outside this brain.## Related- [[Multilingual Publishing]]diff --git a/wiki/multilingual/Multilingual Schema Rules.md b/wiki/multilingual/Multilingual Schema Rules.mdindex 51911dc..bd2e794 100644--- a/wiki/multilingual/Multilingual Schema Rules.md+++ b/wiki/multilingual/Multilingual Schema Rules.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Multilingual Schema Rules decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Multilingual Schema Rules advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Multilingual Schema Rules into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Multilingual Schema Rules guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Multilingual Schema Rules outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Multilingual Schema Rules decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Multilingual Schema Rules gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Multilingual Schema Rules evidence is incomplete or outside this brain.## Related- [[Multilingual Publishing]]diff --git a/wiki/multilingual/Regional Legal And YMYL Escalation.md b/wiki/multilingual/Regional Legal And YMYL Escalation.mdindex 1778eea..f00d6d2 100644--- a/wiki/multilingual/Regional Legal And YMYL Escalation.md+++ b/wiki/multilingual/Regional Legal And YMYL Escalation.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Regional Legal And YMYL Escalation decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Regional Legal And YMYL Escalation advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Regional Legal And YMYL Escalation into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Regional Legal And YMYL Escalation guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Regional Legal And YMYL Escalation outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Regional Legal And YMYL Escalation decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Regional Legal And YMYL Escalation gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Regional Legal And YMYL Escalation evidence is incomplete or outside this brain.## Related- [[Multilingual Publishing]]diff --git a/wiki/multilingual/Translation Versus Localization.md b/wiki/multilingual/Translation Versus Localization.mdindex 581e8c8..87b33db 100644--- a/wiki/multilingual/Translation Versus Localization.md+++ b/wiki/multilingual/Translation Versus Localization.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Translation Versus Localization decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Translation Versus Localization advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Translation Versus Localization into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Translation Versus Localization guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Translation Versus Localization outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Translation Versus Localization decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Translation Versus Localization gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Translation Versus Localization evidence is incomplete or outside this brain.## Related- [[Multilingual Publishing]]diff --git a/wiki/multilingual/x-default Handling.md b/wiki/multilingual/x-default Handling.mdindex b769b57..5028eaa 100644--- a/wiki/multilingual/x-default Handling.md+++ b/wiki/multilingual/x-default Handling.md@@ -100,24 +100,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: x-default Handling decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep x-default Handling advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn x-default Handling into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust x-default Handling guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in x-default Handling outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A x-default Handling decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for x-default Handling gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when x-default Handling evidence is incomplete or outside this brain.## Related- [[Multilingual Publishing]]diff --git a/wiki/personas/Audience Persona Template.md b/wiki/personas/Audience Persona Template.mdindex 9ad7705..ba41463 100644--- a/wiki/personas/Audience Persona Template.md+++ b/wiki/personas/Audience Persona Template.md@@ -98,24 +98,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Audience Persona Template decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Audience Persona Template advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Audience Persona Template into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Audience Persona Template guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Audience Persona Template outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Audience Persona Template decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Audience Persona Template gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Audience Persona Template evidence is incomplete or outside this brain.## Related- [[Voice and Style]]diff --git a/wiki/personas/Banned Claims And Phrases.md b/wiki/personas/Banned Claims And Phrases.mdindex 151ca51..4150280 100644--- a/wiki/personas/Banned Claims And Phrases.md+++ b/wiki/personas/Banned Claims And Phrases.md@@ -98,24 +98,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Banned Claims And Phrases decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Banned Claims And Phrases advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Banned Claims And Phrases into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Banned Claims And Phrases guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Banned Claims And Phrases outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Banned Claims And Phrases decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Banned Claims And Phrases gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Banned Claims And Phrases evidence is incomplete or outside this brain.## Related- [[Voice and Style]]diff --git a/wiki/personas/Brand Voice Inventory.md b/wiki/personas/Brand Voice Inventory.mdindex 1526712..b24110d 100644--- a/wiki/personas/Brand Voice Inventory.md+++ b/wiki/personas/Brand Voice Inventory.md@@ -98,24 +98,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Brand Voice Inventory decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Brand Voice Inventory advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Brand Voice Inventory into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Brand Voice Inventory guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Brand Voice Inventory outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Brand Voice Inventory decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Brand Voice Inventory gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Brand Voice Inventory evidence is incomplete or outside this brain.## Related- [[Voice and Style]]diff --git a/wiki/personas/Distribution Voice Adaptation.md b/wiki/personas/Distribution Voice Adaptation.mdindex f7ad35b..f5a580f 100644--- a/wiki/personas/Distribution Voice Adaptation.md+++ b/wiki/personas/Distribution Voice Adaptation.md@@ -98,24 +98,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Distribution Voice Adaptation decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Distribution Voice Adaptation advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Distribution Voice Adaptation into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Distribution Voice Adaptation guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Distribution Voice Adaptation outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Distribution Voice Adaptation decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Distribution Voice Adaptation gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Distribution Voice Adaptation evidence is incomplete or outside this brain.## Related- [[Voice and Style]]diff --git a/wiki/personas/Example Selection Rules.md b/wiki/personas/Example Selection Rules.mdindex 464eb9e..f7ed4e4 100644--- a/wiki/personas/Example Selection Rules.md+++ b/wiki/personas/Example Selection Rules.md@@ -98,24 +98,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Example Selection Rules decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Example Selection Rules advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Example Selection Rules into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Example Selection Rules guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Example Selection Rules outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Example Selection Rules decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Example Selection Rules gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Example Selection Rules evidence is incomplete or outside this brain.## Related- [[Voice and Style]]diff --git a/wiki/personas/Locale Voice Adaptation.md b/wiki/personas/Locale Voice Adaptation.mdindex 46a28c4..6b91287 100644--- a/wiki/personas/Locale Voice Adaptation.md+++ b/wiki/personas/Locale Voice Adaptation.md@@ -98,24 +98,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Locale Voice Adaptation decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Locale Voice Adaptation advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Locale Voice Adaptation into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Locale Voice Adaptation guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Locale Voice Adaptation outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Locale Voice Adaptation decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Locale Voice Adaptation gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Locale Voice Adaptation evidence is incomplete or outside this brain.## Related- [[Voice and Style]]diff --git a/wiki/personas/Persona Evidence Packet.md b/wiki/personas/Persona Evidence Packet.mdindex 6b5e95c..c2d47a9 100644--- a/wiki/personas/Persona Evidence Packet.md+++ b/wiki/personas/Persona Evidence Packet.md@@ -98,24 +98,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Persona Evidence Packet decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Persona Evidence Packet advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Persona Evidence Packet into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Persona Evidence Packet guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Persona Evidence Packet outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Persona Evidence Packet decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Persona Evidence Packet gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Persona Evidence Packet evidence is incomplete or outside this brain.## Related- [[Voice and Style]]diff --git a/wiki/personas/Readability Review.md b/wiki/personas/Readability Review.mdindex a0065c7..07a886a 100644--- a/wiki/personas/Readability Review.md+++ b/wiki/personas/Readability Review.md@@ -98,24 +98,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Readability Review decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Readability Review advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Readability Review into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Readability Review guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Readability Review outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Readability Review decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Readability Review gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Readability Review evidence is incomplete or outside this brain.## Related- [[Voice and Style]]diff --git a/wiki/personas/Terminology Control List.md b/wiki/personas/Terminology Control List.mdindex cf358b5..e14b67e 100644--- a/wiki/personas/Terminology Control List.md+++ b/wiki/personas/Terminology Control List.md@@ -98,24 +98,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Terminology Control List decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Terminology Control List advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Terminology Control List into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Terminology Control List guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Terminology Control List outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Terminology Control List decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Terminology Control List gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Terminology Control List evidence is incomplete or outside this brain.## Related- [[Voice and Style]]diff --git a/wiki/personas/Tone By Funnel Stage.md b/wiki/personas/Tone By Funnel Stage.mdindex fd1b31c..6aa4d37 100644--- a/wiki/personas/Tone By Funnel Stage.md+++ b/wiki/personas/Tone By Funnel Stage.md@@ -98,24 +98,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Tone By Funnel Stage decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Tone By Funnel Stage advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Tone By Funnel Stage into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Tone By Funnel Stage guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Tone By Funnel Stage outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Tone By Funnel Stage decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Tone By Funnel Stage gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Tone By Funnel Stage evidence is incomplete or outside this brain.## Related- [[Voice and Style]]diff --git a/wiki/personas/Voice Drift Audit.md b/wiki/personas/Voice Drift Audit.mdindex d2f3286..ec0bec9 100644--- a/wiki/personas/Voice Drift Audit.md+++ b/wiki/personas/Voice Drift Audit.md@@ -98,24 +98,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Voice Drift Audit decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Voice Drift Audit advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Voice Drift Audit into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Voice Drift Audit guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Voice Drift Audit outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Voice Drift Audit decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Voice Drift Audit gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Voice Drift Audit evidence is incomplete or outside this brain.## Related- [[Voice and Style]]diff --git a/wiki/personas/YMYL Tone Guardrails.md b/wiki/personas/YMYL Tone Guardrails.mdindex 743fa0c..11582a1 100644--- a/wiki/personas/YMYL Tone Guardrails.md+++ b/wiki/personas/YMYL Tone Guardrails.md@@ -98,24 +98,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: YMYL Tone Guardrails decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep YMYL Tone Guardrails advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn YMYL Tone Guardrails into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust YMYL Tone Guardrails guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in YMYL Tone Guardrails outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A YMYL Tone Guardrails decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for YMYL Tone Guardrails gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when YMYL Tone Guardrails evidence is incomplete or outside this brain.## Related- [[Voice and Style]]diff --git a/wiki/quality/AI Citation Readiness Subscore.md b/wiki/quality/AI Citation Readiness Subscore.mdindex a174763..871e84e 100644--- a/wiki/quality/AI Citation Readiness Subscore.md+++ b/wiki/quality/AI Citation Readiness Subscore.md@@ -38,7 +38,7 @@ source_urls:## SummaryAI Citation Readiness Subscore is the spoke for score answer-first passages, entity clarity, citations, preview controls, and no special AI file myths.Use it when [[Blog Quality Score]] needs a repeatable decision record before a brief, draft, score, or report moves forward.-The durable output is a AI citation readiness subscore.+The durable output is an AI citation readiness subscore.The success condition is that citation readiness is measured without promising inclusion.Keep the note advisory in V1 and route implementation to a human owner.diff --git a/wiki/sources/Canon Notes Map.md b/wiki/sources/Canon Notes Map.mdindex a083270..139f54b 100644--- a/wiki/sources/Canon Notes Map.md+++ b/wiki/sources/Canon Notes Map.md@@ -98,24 +98,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Canon Notes Map decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Canon Notes Map advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Canon Notes Map into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Canon Notes Map guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Canon Notes Map outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Canon Notes Map decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Canon Notes Map gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Canon Notes Map evidence is incomplete or outside this brain.## Related- [[Research Pack Index]]diff --git a/wiki/sources/Claim To Source Mapping.md b/wiki/sources/Claim To Source Mapping.mdindex 262b664..65274f6 100644--- a/wiki/sources/Claim To Source Mapping.md+++ b/wiki/sources/Claim To Source Mapping.md@@ -98,24 +98,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Claim To Source Mapping decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Claim To Source Mapping advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Claim To Source Mapping into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Claim To Source Mapping guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Claim To Source Mapping outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Claim To Source Mapping decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Claim To Source Mapping gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Claim To Source Mapping evidence is incomplete or outside this brain.## Related- [[Research Pack Index]]diff --git a/wiki/sources/Current Requirements Digest.md b/wiki/sources/Current Requirements Digest.mdindex c211292..7dce04b 100644--- a/wiki/sources/Current Requirements Digest.md+++ b/wiki/sources/Current Requirements Digest.md@@ -98,24 +98,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Current Requirements Digest decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Current Requirements Digest advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Current Requirements Digest into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Current Requirements Digest guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Current Requirements Digest outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Current Requirements Digest decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Current Requirements Digest gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Current Requirements Digest evidence is incomplete or outside this brain.## Related- [[Research Pack Index]]diff --git a/wiki/sources/Evidence Gap Register.md b/wiki/sources/Evidence Gap Register.mdindex 77280df..50251ce 100644--- a/wiki/sources/Evidence Gap Register.md+++ b/wiki/sources/Evidence Gap Register.md@@ -98,24 +98,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Evidence Gap Register decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Evidence Gap Register advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Evidence Gap Register into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Evidence Gap Register guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Evidence Gap Register outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Evidence Gap Register decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Evidence Gap Register gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Evidence Gap Register evidence is incomplete or outside this brain.## Related- [[Research Pack Index]]diff --git a/wiki/sources/Google Source Priority Ladder.md b/wiki/sources/Google Source Priority Ladder.mdindex 0343618..782d814 100644--- a/wiki/sources/Google Source Priority Ladder.md+++ b/wiki/sources/Google Source Priority Ladder.md@@ -98,24 +98,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Google Source Priority Ladder decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Google Source Priority Ladder advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Google Source Priority Ladder into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Google Source Priority Ladder guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Google Source Priority Ladder outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Google Source Priority Ladder decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Google Source Priority Ladder gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Google Source Priority Ladder evidence is incomplete or outside this brain.## Related- [[Research Pack Index]]diff --git a/wiki/sources/Practitioner Source Caveats.md b/wiki/sources/Practitioner Source Caveats.mdindex be18b9e..46d64f0 100644--- a/wiki/sources/Practitioner Source Caveats.md+++ b/wiki/sources/Practitioner Source Caveats.md@@ -98,24 +98,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Practitioner Source Caveats decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Practitioner Source Caveats advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Practitioner Source Caveats into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Practitioner Source Caveats guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Practitioner Source Caveats outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Practitioner Source Caveats decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Practitioner Source Caveats gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Practitioner Source Caveats evidence is incomplete or outside this brain.## Related- [[Research Pack Index]]diff --git a/wiki/sources/Primary Study Source Rules.md b/wiki/sources/Primary Study Source Rules.mdindex bbf7754..9505a38 100644--- a/wiki/sources/Primary Study Source Rules.md+++ b/wiki/sources/Primary Study Source Rules.md@@ -98,24 +98,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Primary Study Source Rules decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Primary Study Source Rules advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Primary Study Source Rules into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Primary Study Source Rules guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Primary Study Source Rules outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Primary Study Source Rules decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Primary Study Source Rules gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Primary Study Source Rules evidence is incomplete or outside this brain.## Related- [[Research Pack Index]]diff --git a/wiki/sources/Research Release Gate Notes.md b/wiki/sources/Research Release Gate Notes.mdindex b202d10..2c9d874 100644--- a/wiki/sources/Research Release Gate Notes.md+++ b/wiki/sources/Research Release Gate Notes.md@@ -98,24 +98,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Research Release Gate Notes decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Research Release Gate Notes advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Research Release Gate Notes into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Research Release Gate Notes guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Research Release Gate Notes outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Research Release Gate Notes decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Research Release Gate Notes gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Research Release Gate Notes evidence is incomplete or outside this brain.## Related- [[Research Pack Index]]diff --git a/wiki/sources/Source Confidence Labels.md b/wiki/sources/Source Confidence Labels.mdindex 3642d30..306c9b1 100644--- a/wiki/sources/Source Confidence Labels.md+++ b/wiki/sources/Source Confidence Labels.md@@ -98,24 +98,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Source Confidence Labels decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Source Confidence Labels advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Source Confidence Labels into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Source Confidence Labels guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Source Confidence Labels outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Source Confidence Labels decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Source Confidence Labels gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Source Confidence Labels evidence is incomplete or outside this brain.## Related- [[Research Pack Index]]diff --git a/wiki/sources/Source Ledger Reading Guide.md b/wiki/sources/Source Ledger Reading Guide.mdindex 73b9c4f..7dcac0e 100644--- a/wiki/sources/Source Ledger Reading Guide.md+++ b/wiki/sources/Source Ledger Reading Guide.md@@ -98,24 +98,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Source Ledger Reading Guide decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Source Ledger Reading Guide advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Source Ledger Reading Guide into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Source Ledger Reading Guide guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Source Ledger Reading Guide outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Source Ledger Reading Guide decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Source Ledger Reading Guide gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Source Ledger Reading Guide evidence is incomplete or outside this brain.## Related- [[Research Pack Index]]diff --git a/wiki/sources/Source Refresh Cadence.md b/wiki/sources/Source Refresh Cadence.mdindex 0be3614..6aa6b13 100644--- a/wiki/sources/Source Refresh Cadence.md+++ b/wiki/sources/Source Refresh Cadence.md@@ -98,24 +98,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Source Refresh Cadence decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Source Refresh Cadence advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Source Refresh Cadence into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Source Refresh Cadence guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Source Refresh Cadence outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Source Refresh Cadence decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Source Refresh Cadence gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Source Refresh Cadence evidence is incomplete or outside this brain.## Related- [[Research Pack Index]]diff --git a/wiki/sources/Source URL Canonicalization.md b/wiki/sources/Source URL Canonicalization.mdindex 163da5f..bc9e8e6 100644--- a/wiki/sources/Source URL Canonicalization.md+++ b/wiki/sources/Source URL Canonicalization.md@@ -98,24 +98,24 @@ The output should be short enough to apply during a brief or audit, but complete- The note stays inside the assigned folder and does not mutate references, data, scripts, or external platforms.## Risk Controls-- Stale source risk: a Search Central, QRG, schema, or AI feature change can invalidate current wording.-- Overclaim risk: market studies can describe averages, not guaranteed results for a specific site.-- Scope risk: a workflow note can drift into implementation if credential, CMS, or API mutation steps are added.-- Evidence risk: single-source or practitioner-only claims need advisory confidence until stronger evidence is captured.-- Locale risk: translated content can lose legal, cultural, or source meaning without qualified review.-- Media risk: visuals can imply facts that the text and sources do not support.-- Metric risk: GSC, GA4, URL Inspection, and AI feature reports answer different questions and should not be merged casually.-- Monitoring risk: unconfirmed volatility should stay quarantined until a Google-owned URL confirms it.+- Evidence currency risk: Source URL Canonicalization decisions can go stale when a source, date, or requirement changes.+- Claim scope risk: keep Source URL Canonicalization advice tied to the source coverage named in this note.+- Operational boundary risk: do not turn Source URL Canonicalization into CMS, analytics, Search Console, API, or publishing mutation steps.+- Proof gap risk: when the note lacks direct evidence, record the gap instead of upgrading confidence.+- Audience fit risk: adjust Source URL Canonicalization guidance for topic sensitivity, locale, and review ownership before use.+- Media and data risk: verify charts, visuals, metrics, and examples before they carry this note's claims.+- Metric interpretation risk: separate first-party exports, market studies, and API signals in Source URL Canonicalization outputs.+- Monitoring risk: quarantine unconfirmed volatility until a dated source in the ledger supports it.## Output Shape-- A one-paragraph decision summary for the editor or auditor.-- A dated source list using URLs that are present in the source ledger.-- A confidence label that distinguishes verified evidence from advisory interpretation.-- A rollback or refresh condition for time-sensitive guidance.-- A list of blocked claims that need more evidence before publication.-- A handoff note for writers, editors, reviewers, or data owners.-- A graph link to the parent hub and at least several sibling spokes.-- A clear statement when no action is recommended because the evidence is incomplete.+- A Source URL Canonicalization decision summary for the editor or auditor.+- The source IDs or URLs that directly support the active recommendation.+- A confidence label that matches the evidence strength for this note.+- A rollback or refresh condition tied to the source or workflow affected.+- A blocked-claims list for Source URL Canonicalization gaps that need more evidence.+- A handoff note naming the writer, editor, reviewer, or data owner next action.+- Links back to the parent hub and sibling notes that keep the graph navigable.+- A no-action statement when Source URL Canonicalization evidence is incomplete or outside this brain.## Related- [[Research Pack Index]]