Public docs roadmap.

Track the launch-foundation documentation work at a community-friendly level: what is already usable, what is next, and how to help without turning open work into product claims.

Roadmap Snapshot

Foundation areas: 4
Current work: 6
Launch checks: 15
Operating decisions: 6
Target foundation: Dec 31

Foundation Roadmap

Launch-foundation docs roadmap
Area	Window	Status	Outcome
Trust foundation	Available now	Complete	Product hubs, maturity labels, evidence indexes, claim review, and sensitive-review routing are in place.
First success and reference	Available now	Complete	Quickstarts, tutorials, examples, API references, compatibility matrices, limits, and runbooks cover the four launch products.
Community contribution system	Available now	Complete	Contributor guidance, docs style rules, issue templates, public roadmap notes, machine-readable surfaces, starter issues, and governance notes.
Launch readiness package	Available now	Complete	Content freeze, editorial review, product-owner review, sensitive-claims review, final limitations coverage, launch QA, post-launch triage, and public feedback intake are in place.

Current Work

Contributor guide

Available: DOCS-077

Document local setup, content types, review flow, and expected conduct for community docs changes.

Owner: docs-product-lead

Docs style guide

Available: DOCS-078

Capture voice, structure, code example, claim, status-label, and limitations wording that keeps product boundaries clear.

Owner: docs-lead

Community issue templates

Available: DOCS-079

Route public-safe docs issue reports by product and content type without exposing private source paths.

Owner: docs-product-lead

LLM-friendly docs surfaces

Available: DOCS-081

Expose public-route based llms.txt, full text, and JSON manifests for retrieval, summarization, and docs gap analysis without private source paths.

Owner: docs-platform

Good-first-docs starter issues

Available: DOCS-082

Seed 15 copy-ready starter issues across ObjectDB, Message Broker, Concordia, LogDB, and cross-product docs.

Owner: docs-product-lead

Community governance model

Available: DOCS-083

Define maintainer roles, response targets, merge requirements, escalation routing, and public-safe contributor credit.

Owner: docs-product-lead

Launch Operating Decisions

Ship Bounded Product Truth

Launch with private-beta posture, route-level maturity, evidence, and linked limits instead of waiting for every future product surface.

Review By Exception

Lead reviewers should accept, request a specific rewrite, defer with owner, or block with evidence so vague concern does not become hidden launch risk.

Keep Contribution Issue-First

Community contribution work starts with safe issue and report intake, not public source-edit links or private repository paths.

Gate Feedback Intake

Use the public feedback route for approved issue-template, support, redaction, and page-health intake; keep inline rating controls hidden until that separate surface is approved.

Keep Machine Surfaces Public-Safe

LLM-friendly docs should use canonical public routes, maturity labels, limits, and public summaries rather than private source locations.

Triage After Launch

Post-launch triage starts with support reports, issue templates, failed searches, broken journeys, stale-page signals, and release-doc updates.

Launch Readiness

Available: DOCS-084
Content freeze checklist
Define the final inventory, ownership, risk labels, and unresolved-claim criteria before launch foundation.
Owner: docs-product-lead
Available: DOCS-085
Editorial review pass
Record the consistency, concision, label integrity, duplicate-control, and route-flow review across product docs.
Owner: docs-lead
Available: DOCS-086
Product owner review pass
Record per-product owner outcomes for behavior, maturity, launch-significant limits, and blocker disposition.
Owner: product-smes
Available: DOCS-087
Security and legal claims review
Record sensitive-claim dispositions for security, privacy, legal, support, operations, availability, durability, performance, scale, compatibility, and feedback wording.
Owner: security-legal-support-reviewers
Available: DOCS-088
Known limitations pages
Record product limits pages, unsupported-scenario coverage, required route links, and known-limit blocker rules.
Owner: product-smes
Available: DOCS-089
Changelog and release notes
Track release-linked docs impact, release-note entries, claim-status changes, reviewer decisions, and validation evidence.
Owner: release owners and docs
Available: DOCS-090
Launch QA
Record final navigation, search, links, code blocks, accessibility, responsive, build, and browser QA blocker rules.
Owner: docs-qa-reviewer
Available: DOCS-091
Post-launch triage
Define the first 30 days of support reports, issue templates, failed searches, broken journeys, stale pages, severity, owners, and response expectations.
Owner: support and docs
Available: DOCS-092
Public feedback intake
Route docs gaps, product questions, sensitive evidence, and launch signals through approved customer-safe intake paths.
Owner: support, privacy, and docs platform
Available: DOCS-107
Global route verification dispositions
Record which global route, navigation, search, status, glossary, changelog, roadmap, and page-health Verification Required labels are accepted, bounded, or left to owner lanes.
Owner: docs lead, platform, and QA
Available: DOCS-108
Product hub verification dispositions
Record product chooser, availability schedule, product overview, product status summary, and hub next-step label posture before detailed product-family review.
Owner: product SMEs, docs product lead, and business owner
Available: DOCS-109
ObjectDB verification dispositions
Record ObjectDB overview, S3 Core quickstart, compatibility rows, references, limits, evidence, guides, examples, and operations label posture.
Owner: ObjectDB product SME, docs QA, support, and security
Available: DOCS-110
Message Broker verification dispositions
Record Message Broker overview, stream and queue quickstart, compatibility rows, references, limits, evidence, guides, examples, and operations label posture.
Owner: Message Broker product SME, docs QA, support, security, and operations
Available: DOCS-111
Concordia verification dispositions
Record Concordia hub, quickstart, tutorials, compatibility rows, runtime references, limits, evidence, guides, local curl examples, and validation runbooks label posture.
Owner: Concordia product SME, docs QA, operations, and security
Available: DOCS-112
LogDB verification dispositions
Record LogDB hub, quickstart, OTLP/query and configuration references, compatibility rows, limits, evidence, guides, collector examples, BYOC notes, and operator runbooks label posture.
Owner: LogDB product SME, docs QA, operations, and security

Ways To Help

Check product readiness before proposing copy

Use maturity labels, compatibility rows, limits, and evidence pages before strengthening a product claim.

Status

Validate examples against their evidence

Keep runnable, manually verified, illustrative, and future examples clearly separated.

Example validation

Report gaps with a route and product

Name the page path, product, content type, expected behavior, and whether the gap affects a claim, example, limit, or support flow.

Feedback

Decision Basis

This roadmap is anchored to product status, compatibility matrices, known limits, evidence pages, and launch-readiness review. Detailed story accounting remains internal, and product pages remain the source of truth for current product behavior.