Change-Control Policy

New lanes, automation, live submissions, webhooks, CRM changes, and downstream mutations require explicit approval and evidence planning.

Allowed change classes

Maintenance documentation updates.
Governance audit reruns.
Broken link cleanup.
Evidence-gated wording clarification.
Registry, sitemap, discovery, llms, and manifest consistency fixes.
Approved schema or template patches that do not create new lanes.

Blocked change classes

DNS changes.
Google Workspace or email record changes.
Live form submissions.
Webhook execution.
CRM, CMS, Google Sheets, Apps Script, email, SMS, social, paid media, alert, or inventory mutations.
New operating lanes without explicit approval.
Downstream completion claims without destination evidence.

Required validation before publishing

Local JSON parse checks for changed JSON and JSON-LD.
Read-back of changed files.
Inclusion checks for sitemap, llms, discovery, and site manifest when relevant.
here.now publish output captured.
Live fetch and exact phrase verification after publish.

Required evidence before downstream claims

Direct destination-system evidence matching the exact claim.
Timestamped source or log reference.
Human review when private, stale, conflicting, sensitive, or downstream-completion claims are involved.

Rollback expectations

Use /release-snapshot-v1-0-2.json and /backup-manifest.json to identify the stable baseline.
Re-publish the last known good static bundle when needed.
Verify live URLs before claiming restoration.

Human approval triggers

New lanes.
Automation.
Live tests.
Form submissions.
Webhooks.
CRM, CMS, sheet, script, alert, email, SMS, social, paid media, or inventory changes.
Any claim that depends on private platform state.

Last updated: 2026-06-12T10:19:06Z

# Change-Control Policy New lanes, automation, live submissions, webhooks, CRM changes, and downstream mutations require explicit approval and evidence planning. ## Allowed change classes - Maintenance documentation updates. - Governance audit reruns. - Broken link cleanup. - Evidence-gated wording clarification. - Registry, sitemap, discovery, llms, and manifest consistency fixes. - Approved schema or template patches that do not create new lanes. ## Blocked change classes - DNS changes. - Google Workspace or email record changes. - Live form submissions. - Webhook execution. - CRM, CMS, Google Sheets, Apps Script, email, SMS, social, paid media, alert, or inventory mutations. - New operating lanes without explicit approval. - Downstream completion claims without destination evidence. ## Required validation before publishing - Local JSON parse checks for changed JSON and JSON-LD. - Read-back of changed files. - Inclusion checks for sitemap, llms, discovery, and site manifest when relevant. - here.now publish output captured. - Live fetch and exact phrase verification after publish. ## Required evidence before downstream claims - Direct destination-system evidence matching the exact claim. - Timestamped source or log reference. - Human review when private, stale, conflicting, sensitive, or downstream-completion claims are involved. ## Rollback expectations - Use `/release-snapshot-v1-0-2.json` and `/backup-manifest.json` to identify the stable baseline. - Re-publish the last known good static bundle when needed. - Verify live URLs before claiming restoration. ## Human approval triggers - New lanes. - Automation. - Live tests. - Form submissions. - Webhooks. - CRM, CMS, sheet, script, alert, email, SMS, social, paid media, or inventory changes. - Any claim that depends on private platform state. Last updated: 2026-06-12T10:19:06Z