DOCS-113 and DOCS-114
Still owns
Cross-product concepts, operations, support, privacy, community, roadmap source notes, and generated metadata.
DOCS-110
Verification RequiredMessage Broker verification dispositions.
This launch-readiness review decides how Message Broker overview, quickstart, compatibility rows, references, limits, evidence, guides, examples, and operations pages keep or bound Verification Required labels before final launch acceptance.
Decision Snapshot
- Message Broker routes
- 12
- Source groups
- 4
- Rows reviewed
- 17
- P0/P1 blockers
- 0
- Product lanes open
- 0
Route Dispositions
| Route or surface | Current exposure | Disposition | Rationale | Evidence |
|---|---|---|---|---|
| Message Broker hub | Controlled Beta hub with stream, replay, shared queue, diagnostics, configured auth, and replication boundary labels. | Accept with limits | The hub frames the broker as a single-cluster controlled-beta candidate and keeps replication, compatibility, auth, and support claims gated. | SMB-EVID-001, SMB-EVID-002, SMB-EVID-005, SMB-EVID-006 |
| Stream and queue quickstart | Local first-success workflow for stream create, publish, replay, queue claim, ack, inspection, cleanup, and replication status. | Accept with limits | The tutorial proves local route behavior and treats replication status as a route-level boundary instead of cross-site outcome proof. | SMB-EVID-003, SMB-EVID-007, DOCS-023 |
| Compatibility matrix | Row labels separate supported, partial, unsupported, preview, future, and review-bound route/auth/protocol behavior. | Accept with limits | The matrix keeps auth, replication, tenant/RBAC/quota, Kafka, CLI, and SDK boundaries visible until owners promote or reject rows. | SMB-EVID-010 and DOCS-040 |
| References | HTTP, CLI, SDK, errors, limits, compatibility, and evidence references under conservative page maturity. | Accept with limits | The reference family spans implemented controlled-beta routes and review-bound customer claims, so the conservative label remains useful. | DOCS-031, DOCS-032, DOCS-040 |
| HTTP reference | Source-backed route reference for health, auth, stream, record, cursor, queue, replication, audit, metrics, and storage administration. | Accept with limits | The page names exact routes, permissions, examples, errors, and limits while blocking broader support, security, scale, protocol, or topology claims. | SMB-EVID-002, SMB-EVID-008, DOCS-031 |
| CLI and SDK reference | Controlled-beta lifecycle flags, local and remote CLI reads, diagnostics, release artifacts, and Rust SDK entry points. | Accept with limits | Remote CLI is limited to HTTP management reads and diagnostics, while SDK auth, HTTPS, package, and production support claims remain unapproved. | SMB-EVID-009 and DOCS-032 |
| Known limits | Controlled-beta route limits plus Verification Required Kafka, replication, identity, and support claim rows. | Accept with limits | The page names unsupported Kafka listener behavior, replication outcome boundaries, auth posture, remote CLI limits, and claim-review owners. | SMB-EVID-005, SMB-EVID-011, DOCS-042 |
| Evidence index | Evidence records remain owner-pending and page maturity remains Verification Required. | Accept with limits | The page is an evidence tracker; pending status prevents route, tooling, and example records from becoming approved product promises. | SMB-EVID-001 through SMB-EVID-013 |
| Guides and Rust SDK examples | Guide family remains Verification Required because SDK examples are bounded until accepted. | Accept with limits | The guide pages preserve example and validation context without promoting package support, auth transport, or customer deployment readiness. | SMB-EVID-009, SMB-EVID-013, DOCS-059 |
| Operations and runbooks | Controlled-beta operations pages use Verification Required support and replication outcome boundaries. | Accept with limits | The runbooks cover current route behavior and evidence capture while blocking stronger failover, support, scale, security, or recovery promises. | SMB-EVID-012 and DOCS-051 |
Compatibility Row Dispositions
| Row area | Current state | Disposition | Rationale |
|---|---|---|---|
| Health readiness, streams, records, cursors, consumer groups, and shared queue delivery | Supported / Controlled Beta | Keep controlled beta | These route families are implemented and source-backed, with route permissions and local workflow evidence nearby. |
| Audit, metrics, storage administration, remote CLI management reads, and Rust SDK HTTP workflows | Partial / Controlled Beta | Keep controlled beta with row limits | The capabilities are useful for controlled-beta evaluation but carry explicit metrics, transport, admin, and credential boundaries. |
| Runtime auth modes | Partial / Verification Required | Accept with limits | Documented auth modes exist, but external identity and broker-side TLS proof remain review-bound. |
| Replication status, worker control, and target apply | Partial / Verification Required | Accept with limits | Routes exist, but cross-site durability, failover, and topology outcomes need selected packet evidence. |
| Tenant visibility, RBAC, and quota boundaries | Verification Required / Verification Required | Accept with limits | Tenant visibility, auth policy, quota accounting, metrics labels, and audit filtering need security and operations acceptance before promotion. |
| Compatibility adapter harness and Kafka-shaped migration prototype | Preview / Preview Contract | Keep preview contract | Harness and typed adapter behavior are useful contract evidence, but they are not external protocol support. |
| Kafka network listener and external Kafka clients | Unsupported / Verification Required | Keep unsupported and review-bound | There is no current Kafka network listener, Kafka wire-protocol compatibility, or external Kafka client smoke evidence. |
| Future protocol compatibility expansion | Future / Future | Keep future | Real Kafka protocol work and additional broker protocols remain roadmap direction until implementation and reviewer acceptance exist. |
Launch Blocking Rules
| Severity | Condition | Required action |
|---|---|---|
| P0 | A Message Broker route exposes private source paths, credentials, internal deployment details, customer data, or unsupported security/legal/support promises. | Remove the exposure before launch review continues. |
| P1 | A core Message Broker page presents controlled-beta route behavior as GA, production support commitment, strict cross-site durability, failover, broad security, scale, or performance. | Rewrite, relabel, or block through DOCS-104. |
| P2 | A page or row keeps Verification Required because behavior is partial, route-level, owner-pending, topology-bound, protocol-preview, or awaiting sensitive review. | Accept with limits and keep the evidence or known-limit path visible. |
| P3 | Source notes, README, generated manifests, project-management records, or automation mention Message Broker labels as review taxonomy. | Keep as tracker language unless DOCS-114 changes it. |
Remaining Boundaries
DOCS-104
Still owns
Exact build, reviewer signoffs, accepted risks, launch watch, and go/no-go decision.