Launch observability and incident hooks.

Use this operations view to watch deployment health, 404s, failed searches, client-side errors, page-load regressions, feedback signals, and escalation readiness during launch and the first 30 days after production promotion.

Launch Watch Summary

Watch window: 30 days
Signal groups: 7
Remote analytics: Disabled
Blocking severity: P0/P1

Signal Sources

Launch observability signals and escalation triggers
Signal	Source or route	Owner	Launch use	Escalation trigger
Deployment health	Azure pipeline result, `/version.txt`, production CDN rollback, and docs host header checks	release owner and docs platform reviewer	Confirm the deployed artifact, host, CDN, cache, and generated route manifests match the intended launch build.	Failed build or deploy, missing version record, unexpected redirect, stale artifact, HTTP 5xx, or cache state that hides the accepted build.
404s and broken journeys	404, `/404.html`, page-health broken journey events, link validation, and DOCS-100 route smoke	docs QA reviewer and docs platform reviewer	Distinguish expected missing-route behavior from broken navigation, stale links, or route rewrite failures.	A core route, product hub, legal/support page, sitemap route, or launch-critical entry path returns 404 or records repeated broken journeys.
Failed searches	Search no-result behavior and page-health failed-search table	docs platform reviewer and product SMEs	Detect missing keywords, unfindable launch pages, product facet issues, and reader language the current index does not serve.	Product names, quickstart terms, support/legal terms, known-limit terms, or launch-critical operations terms produce no useful result.
Client-side errors	Playwright console checks, browser smoke output, and manual launch-watch browser console notes	docs QA reviewer	Catch hydration errors, script exceptions, failed route transitions, broken copy buttons, and browser-only regressions that source validation cannot see.	Uncaught exception, hydration failure, repeated console error on a core route, or a browser interaction that prevents a reader from continuing.
Page-load regressions	DOCS-100 full-route smoke duration, representative accessibility/performance checks, and manual slow-route notes	docs QA reviewer and docs platform reviewer	Find pages that load too slowly, overflow badly, or hide primary content during launch watch.	A core route times out, exceeds the accepted smoke threshold, shows persistent layout overflow, or blocks primary content on mobile or desktop.
Feedback signals	Feedback, support, community issue templates, and support reviewer intake	support reviewer and docs triage lead	Route public docs gaps, product questions, sensitive evidence, and launch-impacting reports through approved paths.	A report contains credentials, customer data, security/legal/privacy concern, product promise confusion, or a P0/P1 docs defect.
Escalation readiness	Post-launch triage, rollback plan, DOCS-104 final acceptance report, and product owner lanes	release owner and operations reviewer	Ensure every launch signal has a responder, evidence package, severity, decision owner, and follow-up route.	Any P0/P1 lacks an owner, rollback path, redaction decision, customer-safe acknowledgement, or accepted-risk record.

Watch Cadence

Launch watch windows and required actions
Window	Cadence	Owner	Required action
Pre-launch rehearsal	One pass before production promotion	release owner	Confirm the launch watch roster, approved docs URL, expected build SHA, pipeline run ID, rollback mode, and evidence fields.
Launch day	Same-day watch after production deploy	release owner, support reviewer, and docs QA reviewer	Check deployment health, core routes, 404 behavior, search, page health, support/legal/feedback routes, and browser console output.
First 48 hours	Twice daily scan	docs triage lead	Review new feedback, failed searches, broken journeys, client-side errors, slow pages, and unresolved P0/P1 decisions.
First business week	Daily scan	support reviewer and docs platform reviewer	Merge duplicates, assign product or platform owners, record accepted risks, and confirm release-doc updates when docs behavior changed.
Days 8 through 30	Weekly scan at minimum	docs lead	Move non-blocking P2/P3 work into normal backlog and keep unresolved P0/P1 items on the release watch.

Incident Hooks

Triggers, responders, evidence, and decision paths
Hook	Trigger	First responder	Required evidence	Decision path
Build or deploy failure	Pipeline stage fails, deploy artifact is missing, /version.txt is stale, or expected docs host does not serve the build.	release owner	Pipeline run ID, commit SHA, failing stage, host, response headers, and last accepted artifact.	Use DOCS-101 to hold promotion, redeploy, restore S3 versions, invalidate cache, or roll back.
Core route outage	Home, search, status, support, legal, feedback, operations, product hubs, sitemap, or LLM manifests fail.	docs QA reviewer	URL, status, screenshot or browser output, route source, sitemap or LLM entry, and reproduction command.	Treat as P0/P1, fix or roll back, and record final status in DOCS-104.
Broken journey or 404 spike	New repeated broken journeys appear for public navigation, search results, support paths, product hubs, or launch docs.	docs platform reviewer	Missing route, referrer when available, link source, route manifest state, and link-validation result.	Fix link or route, add redirect/rewrite evidence, or accept as known unsupported entry path.
Failed search pattern	Launch-critical queries produce no results or send readers to the wrong product/status/limits surface.	docs platform reviewer and product SME	Query, selected facets, result count, expected target, affected audience, and search-index entry.	Add keywords, rewrite title/description, create missing route, or record a product-owner decision.
Client-side regression	Browser console reports uncaught errors, hydration issues, failed transitions, or broken interactive controls.	docs QA reviewer	Browser, viewport, route, console output, reproduction steps, and screenshot when useful.	Fix before launch acceptance for P0/P1; defer only when the owner records a P2/P3 accepted risk.
Feedback or support escalation	Public report names sensitive evidence, misleading docs, broken launch route, legal/privacy concern, or product promise mismatch.	support reviewer	Redacted report, route, product, severity, affected audience, acknowledgement status, and assigned owner.	Route through DOCS-092, DOCS-091, sensitive review, or product owner review before customer-visible commitments change.

Escalation Matrix

Launch severity, owner, and evidence rules
Severity	Condition	First responder	Escalate to	Required record
P0	Docs unavailable, public route exposes private systems or credentials, primary navigation unusable, or legal/privacy/support safety at risk.	release owner	docs lead, security/privacy/legal, support, and affected product owner	Incident summary, immediate action, rollback or hide decision, owner signoff, and customer-safe status.
P1	Core product hub, quickstart, reference, known limit, status, support, legal, search, or feedback path materially misleads or strands a reader.	docs QA reviewer or support reviewer	docs lead, docs platform reviewer, product SME, and release owner	Reproduction, owner, due date, fix or accepted-risk decision, and validation command.
P2	Secondary route issue, search keyword gap, minor slow page, stale review signal, or non-critical copy/layout issue.	docs triage lead	docs platform reviewer, product SME, or docs lead	Triage row with severity, evidence, owner, target date, and disposition.
P3	Optional polish, visual improvement, alternate wording, or backlog-quality suggestion.	docs product lead	owning docs backlog owner	Normal backlog item or accepted launch-foundation risk.

Evidence Package

Fields required before a launch signal can close
Field	Required value
Build identity	Commit SHA, branch or PR, pipeline run ID, deploy artifact identity, and /version.txt value when available.
Environment	Local, docs-dev, docs-tst, or production hostname, timestamp, and reviewer network context when non-production access gating applies.
Signal source	Pipeline, route smoke, page health, support report, issue template, browser console, manual check, or generated route manifest.
Reproduction	Command, URL, browser, viewport, search query, selected facets, referrer, or interaction steps needed to reproduce.
Severity and owner	P0/P1/P2/P3, first responder, decision owner, due date, and escalation lane.
Privacy posture	Confirmation that credentials, customer identifiers, payload bodies, private topology, account IDs, and raw support evidence are redacted or withheld.
Decision	Fixed, rolled back, hidden, relabeled, accepted with limits, deferred, or launch-blocking.
Validation	Rerun command, browser evidence, route check, or owner acceptance that proves the current disposition.

Production CDN, DNS, cache, and rollback plan
Available: DOCS-101
Cutover evidence, CDN, DNS, cache, invalidation, rollback, and go/no-go records.
Observability and audit guide
Available: DOCS-054
Product health, metrics, audit, logs, diagnostics, support bundle, and privacy-safe handoff boundaries.
Page health analytics
Available: DOCS-068
Browser-local failed searches, broken journeys, future feedback event shape, and stale review signals.
Public feedback intake
Available: DOCS-092
Customer-safe docs feedback intake, product-question routing, redaction boundaries, and support handoff.
Post-launch triage
Available: DOCS-091
First 30 days of launch triage cadence, severity, owner lanes, and required outputs.
Launch QA
Available: DOCS-090
QA gates, browser and device expectations, blocker rules, and accepted launch risks.