DOCS-113 and DOCS-114
Still owns
Cross-product concepts, operations, support, privacy, community, roadmap, source notes, and generated metadata.
DOCS-108
Verification RequiredProduct hub verification dispositions.
This launch-readiness review decides how the product chooser, availability schedule, hub overview labels, status summaries, and next-step labels expose private-beta posture before final launch acceptance.
Decision Snapshot
- Product hubs
- 4
- Shared surfaces
- 5
- Public beta dates
- 4
- P0/P1 blockers
- 0
- Detail lanes open
- 0
Shared Surface Dispositions
| Surface | Current exposure | Disposition | Rationale | Next owner |
|---|---|---|---|---|
| Product chooser | Page label remains Verification Required; product cards show Controlled Beta. | Accept with limits | The chooser compares four private-beta products and should keep a broad reviewer boundary while cards name product-specific maturity. | Available: DOCS-112 |
| Product availability schedule | ObjectDB, Message Broker, LogDB, and Concordia are Private Beta with dated public-beta windows. | Accept | The schedule is precise enough for launch-foundation docs and does not imply GA, support coverage, or customer entitlement. | docs product lead |
| Product hub overview labels | Hubs use Controlled Beta with narrower Live, Alpha, Preview Contract, Future, or Verification Required surface labels. | Accept with limits | The hub label describes product-family availability; sub-surface labels keep evidence and unresolved claims visible. | product SMEs |
| Status dashboard product summaries | Page label remains Verification Required; product rows show Controlled Beta and known gates. | Accept with limits | The dashboard combines schedule, current surfaces, gated contracts, limitations, and evidence links. | Available: DOCS-112 |
| Hub next-step labels | Next steps use Available now or specific DOCS availability rather than maturity promotion. | Accept | These labels route readers to existing pages without strengthening product support, readiness, scale, or GA claims. | docs QA reviewer and SMEs |
Product Hub Dispositions
| Product | Current hub posture | Disposition | Remaining owner |
|---|---|---|---|
| ObjectDB | Controlled Beta hub led by scoped S3 Core, preview native API direction, and Verification Required customer-claim gates. | Accept with limits | Available: DOCS-109 |
| Message Broker | Controlled Beta hub for stream, replay, shared queue, diagnostics, configured auth, and replication route-family boundaries. | Accept with limits | Available: DOCS-110 |
| Concordia | Controlled Beta product-family hub with alpha Cache, Gateway, Storage, and Time Series surfaces and future Edge Workflows. | Accept with limits | Available: DOCS-111 |
| LogDB | Controlled Beta hub with narrow live OTLP ingest, WAL, segment bundle, and query surfaces plus gated S3, BYOC, replay, scale, and GA claims. | Accept with limits | Available: DOCS-112 |
Launch Blocking Rules
| Severity | Condition | Required action |
|---|---|---|
| P0 | A product hub, chooser card, availability row, or status summary exposes private source paths, credentials, internal deployment details, or customer data. | Remove the exposure before launch review continues. |
| P1 | A hub or status row materially misstates private-beta availability, current behavior, support, security, durability, performance, scale, or GA. | Rewrite, relabel, or block through DOCS-104. |
| P2 | A hub keeps Verification Required because a sub-surface, customer-facing claim, or evidence gate is unresolved but clearly bounded. | Accept with limits and keep the product-family owner visible. |
| P3 | Next-step status labels, roadmap references, README notes, or project-management records mention the label as review process. | Keep as tracker language unless the owning lane changes it. |
Remaining Detailed Boundaries
DOCS-104
Still owns
Exact build, reviewer signoffs, accepted risks, launch watch, and go/no-go decision.