Global route verification dispositions.

This launch-readiness review decides how global routes, navigation, search, status, glossary, changelog, roadmap, and page-health surfaces expose Verification Required before final launch acceptance.

Decision Snapshot

Global surfaces: 16
P0/P1 blockers: 0
Hidden entry labels: 1
Accepted boundaries: 15

Global Surface Dispositions

DOCS-107 global route Verification Required decisions
Surface	Current exposure	Disposition	Rationale	Next owner
Home	General Verification Required label is hidden from the home maturity overview.	Accept	DOCS-106 already keeps the primary public entry point from leading with reviewer uncertainty.	docs lead
Primary and utility navigation	Navigation links do not show maturity badges.	Accept	The header and footer stay task-oriented while route pages carry their own maturity context.	docs platform reviewer
Product chooser	Page label remains Verification Required; product cards show product maturity.	Accept with limits	The chooser crosses all four products, so it keeps a conservative boundary until hub posture closes.	DOCS-108
Tutorials index	Page label remains Verification Required.	Accept with limits	The index defines tutorial quality gates while product quickstarts carry their own evidence.	docs QA reviewer and product SMEs
Guides index	Page label remains Verification Required.	Accept with limits	Guides aggregate example, feedback, page-health, and product workflows with mixed maturity.	DOCS-113
Reference index	Page label remains Verification Required.	Accept with limits	The schema is usable, but product reference items still own exact evidence and claim posture.	DOCS-109 through DOCS-112
Concepts index	Page label remains Verification Required.	Accept with limits	Cross-product concepts can imply integration, durability, support, or maturity commitments.	DOCS-113
Operations index	Page label remains Verification Required.	Accept with limits	Operations pages span runbooks, launch watch, privacy, support handoff, and incident language.	DOCS-113
Compatibility index	Page label and verification-required row state remain visible.	Accept with limits	The route documents row taxonomy; product matrices and tooling still own exact promotion rules.	DOCS-114 and product lanes
Search	Page label remains Verification Required; maturity facet includes the label.	Accept with limits	Reviewers need to find bounded claims, and no-result signals stay browser-local.	docs platform reviewer
Status	Page label remains Verification Required; records carry specific maturity labels.	Accept with limits	The dashboard mixes product availability, public beta dates, known limits, and evidence paths.	DOCS-108 through DOCS-112
Page health	Page label remains Verification Required.	Accept with limits	Browser-local health data is useful for launch watch but is not production analytics or RUM.	docs platform and privacy reviewers
Glossary	Page label remains Verification Required; the label definition stays visible.	Accept with limits	Terms cross product boundaries and include overloaded maturity, tenancy, and support language.	DOCS-113
Community	Page label remains Verification Required.	Accept with limits	Contribution intake is public-safe, but review routing and claim escalation stay bounded.	docs lead and support reviewer
Changelog	Page label remains Verification Required.	Accept with limits	Release notes can change maturity or claim posture and need explicit reviewer decisions.	release owner
Roadmap	Page label remains Verification Required.	Accept with limits	Roadmap language must stay scoped to documentation work, not product delivery commitments.	docs product lead

Facet And Taxonomy Exposure

Reviewer-facing maturity taxonomy decisions
Surface	Disposition	Required boundary
Search maturity facet	Keep visible	Reviewers need to locate every Verification Required route before launch.
Status maturity filter	Keep visible	Product and docs platform records need filtering by maturity before go/no-go.
Compatibility row taxonomy	Keep visible	Supported, partial, unsupported, preview, future, and verification-required rows remain the shared matrix language.
Glossary term	Keep visible	The term explains that the label weakens a claim until evidence and owner review exist.
Page-health local events	Keep local only	Failed-search and journey data stay in the reader's browser; remote analytics remain out of scope.
Search index metadata	Keep as an allowed value	Search results should show route maturity truthfully instead of hiding reviewer-bound pages.

Launch Blocking Rules

Global-route blocker rules before DOCS-104
Severity	Condition	Required action
P0	A global route exposes private source paths, credentials, internal deployment details, or customer data.	Remove the exposure before launch review continues.
P1	A global route materially misleads readers about product availability, support, legal/privacy posture, status, or limits.	Rewrite, relabel, or block through DOCS-104.
P2	A global route keeps Verification Required because it aggregates mixed maturity or reviewer policy.	Accept with limits while keeping the owning follow-up visible.
P3	Taxonomy, templates, tooling, README, automation, or project-management files mention the label as review process.	Keep as taxonomy unless DOCS-114 changes the model.

Remaining Boundaries

DOCS-108

Still owns

Product chooser, product hub, and availability posture

DOCS-109

Still owns

ObjectDB route and row labels

DOCS-110

Still owns

Message Broker route and row labels

DOCS-111

Still owns

Concordia route and row labels

DOCS-112

Still owns

LogDB route and row labels

DOCS-113

Still owns

Cross-product concepts, operations, support, privacy, community, and roadmap source notes

DOCS-114

Still owns

Frontmatter, templates, search/status models, icons, validators, generated metadata, and automation fixtures

DOCS-104

Still owns

Exact build, reviewer signoffs, accepted risks, launch watch, and go/no-go decision