Community milestone status was stale after DOCS-083 merged.
Fixed in this pass by marking the Community Contribution System complete and moving Launch Readiness to current focus.
Roadmap milestone copy updated in this PR.
Editorial review
Verification RequiredKeep launch docs consistent and concise.
DOCS-085 records the editorial pass across product hubs, quickstarts, tutorials, guides, references, compatibility, limits, and evidence routes. The pass found no editorial launch blockers and keeps final product, sensitive-claim, known-limit, and browser QA review in their owning stories.
Review Summary
- Products reviewed
- 4
- Route families
- 5
- Editorial blockers
- 0
- Owner follow-ups
- 4
Editorial Checks
| Check | Question | Outcome |
|---|---|---|
| Consistency | Do page titles, route labels, maturity labels, and next-step names use the same vocabulary across products? | Pass. Product hubs, quickstarts, guides, references, compatibility, limits, and evidence routes use the shared launch vocabulary. |
| Concision | Does each route lead with the reader task and avoid burying the useful next action? | Pass. Product routes start with current posture, first task, route family, or reference surface before deeper evidence. |
| Label Integrity | Do Live, Controlled Beta, Alpha, Preview Contract, Future, and Verification Required labels stay attached to their owning evidence? | Pass with follow-up. Label usage is editorially clear; DOCS-086 through DOCS-087 still own final product and sensitive-claim acceptance. |
| Duplicate Control | Are repeated limitations, maturity notes, and evidence reminders useful boundaries rather than accidental duplication? | Pass. Repeated boundary language is intentional where it keeps known limits near copyable workflows and references. |
| Route Flow | Can readers move from product hub to quickstart, guides, reference, compatibility, limits, evidence, and operations without dead ends? | Pass. Route families expose next steps and keep evidence or limits close to claim-sensitive decisions. |
Route Family Results
| Family | Scope | Outcome | Follow-up |
|---|---|---|---|
| Product chooser and hubs | Product chooser, ObjectDB, Message Broker, Concordia, and LogDB hubs. | Passed editorial consistency review for product posture, maturity splits, first paths, boundary callouts, and evidence-linked next steps. | Product owner review in DOCS-086 must still accept product behavior and launch-significant positioning. |
| Quickstarts and tutorials | Product quickstarts, Concordia tutorials, and shared prerequisites. | Passed editorial review for prerequisite framing, command flow, expected output, cleanup notes, local-only boundaries, and known-limit adjacency. | Example and route validation remains owned by DOCS-090 launch QA. |
| Guides and examples | Examples framework, ObjectDB SDK examples, Message Broker Rust SDK examples, LogDB collector examples, and Concordia local curl examples. | Passed editorial review for example status labels, reviewer-run rationale, copyable command boundaries, and product-specific next steps. | DOCS-087 still owns final sensitive-claim review for examples that touch support, privacy, security, or operations language. |
| References | ObjectDB HTTP and configuration, Message Broker HTTP plus CLI/SDK, Concordia runtime, LogDB OTLP/query and configuration, and shared errors and limits. | Passed editorial review for section order, source-backed item shape, auth/request/response/error/limit separation, and route labels. | DOCS-086 must still record product-owner acceptance for reference behavior. |
| Compatibility, limits, and evidence | Product compatibility matrices, known limits pages, and evidence indexes across ObjectDB, Message Broker, Concordia, and LogDB. | Passed editorial review for clear status vocabulary, visible unsupported paths, evidence proximity, and no obvious duplicated reader journey. | Known-limit coverage and link completeness are recorded separately in DOCS-088. |
Findings
No editorial launch blockers found across reviewed product route families.
Accepted for DOCS-085 with product-owner, sensitive-claim, known-limit, and launch-QA records kept in their owning stories.
Route-family review recorded in this page and docs/audits/DOCS-085-editorial-review-pass.md.
Repeated maturity and limits language appears across routes.
Accepted as intentional boundary copy because quickstarts, references, examples, and compatibility pages can be entered independently.
Style guide and content-freeze posture both prefer nearby limits over hidden launch risk.
Remaining Owner Work
| Work item | Owner | Reason |
|---|---|---|
| DOCS-086 | product-smes | Product owners must accept behavior, maturity, limits, and launch-significant positioning. |
| DOCS-087 | security-reviewer, legal-reviewer, support-reviewer | Sensitive language is recorded separately in the DOCS-087 claim-review route and remains outside editorial acceptance. |
| DOCS-088 | product-smes and docs lead | Known-limit route coverage is recorded separately from editorial acceptance. |
| DOCS-090 | docs-qa-reviewer | Browser, device, navigation, search, code block, accessibility, and responsive checks remain separate launch QA. |