Keep every product limit reachable.

DOCS-088 records launch-foundation coverage for known limitations and unsupported scenarios across ObjectDB, Message Broker, Concordia, and LogDB. Each product limits page is published and linked from the required hub, quickstart, reference, and compatibility surfaces.

Coverage Summary

Limit pages: 4
Core surfaces covered: 16
Launch blockers: 0
Coverage posture: Complete

Product Results

DOCS-088 known-limit route coverage by product
Product	Limits route	Unsupported scenario summary	Linked from	Disposition
ObjectDB	ObjectDB known limits	Advanced S3 families, local adapter constraints, preview native API boundaries, and review-required claim areas.	Hub, quickstart, reference index, HTTP reference, configuration reference, compatibility matrix, guides, evidence, and operations.	Complete. Required hub, quickstart, reference, and compatibility paths expose the ObjectDB limits route.
Message Broker	Message Broker known limits	Kafka listener exclusion, replication outcome boundaries, direct identity-provider validation, remote CLI data writes, and review-required claim areas.	Hub, quickstart, reference index, HTTP reference, CLI/SDK reference, compatibility matrix, guides, evidence, and operations.	Complete. Required hub, quickstart, reference, and compatibility paths expose the Message Broker limits route.
Concordia	Concordia known limits	Local bearer-token identity, Gateway diagnostic writes, Storage validation-only flags, future protocol frames, Edge Workflows, and review-required claim areas.	Hub, quickstart, tutorials, reference index, runtime reference, compatibility matrix, guides, evidence, and operations.	Complete. Required hub, quickstart, reference, and compatibility paths expose the Concordia limits route.
LogDB	LogDB known limits	Metrics and profile exclusions, S3 query-read versus publication, replay API boundaries, external sink boundaries, BYOC gates, and review-required claim areas.	Hub, quickstart, reference index, OTLP/query reference, configuration reference, compatibility matrix, guides, evidence, and operations.	Complete. Required hub, quickstart, reference, and compatibility paths expose the LogDB limits route.

Surface Coverage

Required route-family link coverage
Surface	Required coverage	Link evidence	Disposition
Product hubs	Each product hub links to its product limits page before readers strengthen product, support, compatibility, or launch claims.	All four hubs include a direct Read known limits next-step card and the shared product navigation exposes Limits.	Complete.
Quickstarts and tutorials	First-success flows keep known limits available near setup, expected output, cleanup, and unsupported behavior sections.	All four quickstarts expose Limits through shared product navigation; Concordia tutorials do the same and include a local Limits section.	Complete.
References	Reference index and detail pages link to product limits before readers reuse API, CLI, SDK, runtime, configuration, or error behavior.	Reference indexes and detailed reference pages include Limits in shared product navigation; reference indexes also route to the shared errors and limits catalog.	Complete.
Compatibility matrices	Compatibility pages link to product limits wherever unsupported, partial, preview, future, or verification-required rows need reader context.	All four compatibility pages include direct Read known limits next-step cards and Limits in shared product navigation.	Complete.
Guides, evidence, and operations	Non-core but claim-adjacent product routes should keep limits visible for examples, evidence review, troubleshooting, and support handoff.	Product guides, evidence indexes, operations indexes, and runbooks expose Limits through shared product navigation; many also include route cards or inline limit references.	Complete as supporting coverage.

Blocking Rules

Known-limit coverage launch blocking rules
Severity	Blocks launch?	Condition	Required action
P0	Yes	A limits page is missing, not routable, or absent from generated public route manifests.	Restore the product limits route, regenerate manifests, and rerun link, SEO, and build validation.
P1	Yes	A product hub, quickstart, relevant reference, or compatibility page routes around a material known limitation.	Add or restore the product-specific limits link before launch foundation.
P2	No, if tracked	A secondary guide or operations page would scan better with an additional inline limit callout even though product navigation already links limits.	Track with owner and target date; do not block launch when core coverage is complete.

Remaining Owner Work

Follow-up work that remains outside DOCS-088
Work item	Owner	Disposition
DOCS-090	docs QA reviewer	Browser, device, navigation, search, code-block, accessibility, responsive, and route-smoke validation remain launch QA.
DOCS-091	support and docs	Post-launch triage remains open for feedback, search failures, broken examples, and missing docs reports.
DOCS-092	support, privacy, and docs platform	Public page feedback intake remains hidden until approved routing, privacy, retention, acknowledgement, triage, and browser coverage exist.
DOCS-094 and DOCS-107 through DOCS-114	launch-review owners	Verification Required label disposition remains tracked separately for final launch-review closure.