ObjectDB S3 Core compatibility
- S3 profile, route, local adapter, credential, or unsupported behavior change
- ObjectDB evidence index or product reference update
Compatibility workflow
Verification RequiredUse this workflow to keep product matrices tied to tests, fixtures, references, release notes, evidence records, owner review, and visible stale-row warnings.
| Matrix | Owner | Reviewers | Cadence | Review basis | Review status |
|---|---|---|---|---|---|
| ObjectDB S3 Core compatibility | objectdb-docs-owner |
| 45 days; warn 14 days before due | ObjectDB S3 Core matrix review | 2026-08-16Due 2026-09-30Current |
| LogDB OTLP and S3 query compatibility | logdb-docs-owner |
| 45 days; warn 14 days before due | LogDB OTLP and S3 query matrix review | 2026-08-16Due 2026-09-30Current |
| Message Broker route and auth compatibility | message-broker-docs-owner |
| 45 days; warn 14 days before due | Message Broker route and auth matrix review | 2026-08-16Due 2026-09-30Current |
| Concordia runtime boundary compatibility | concordia-docs-owner |
| 45 days; warn 14 days before due | Concordia runtime boundary matrix review | 2026-08-16Due 2026-09-30Current |
Check product source changes, tests, fixtures, generated references, release notes, evidence indexes, and known-limits pages for rows that need review.
Update evidence IDs, fixture names, release-note references, or owner signoff before changing any row status or maturity.
Product SME reviews runtime truth; docs QA checks notes, unsupported behavior, stale dates, evidence, and copy/paste safety.
Change the rendered matrix, evidence index, known-limits links, and internal tracking records in the same PR when behavior changes.
Set `last_reviewed` only after required reviewers accept the row for the stated scope.
The matrix component derives each row's next due date from lastReviewed plus the page cadence. Rows show Current until the warning window opens, Due Soon during the warning window, and Stale after the due date passes or the review date cannot be parsed.
A stale row should stay visible, but its wording must not be promoted to stronger support, security, durability, performance, scale, compliance, or customer-commitment language until the owner refreshes evidence and required reviewers accept the row again.
Compatibility review records are maintained internally. Public matrices should expose owner, reviewer, cadence, evidence ID, and review status without publishing private source locations.
Available: DOCS-038
Review ObjectDB matrixCheck S3 Core compatibility rows, unsupported S3 family behavior, and local adapter limits.
Available: DOCS-039
Review LogDB matrixCheck OTLP, query, S3 query-read, signal exclusion, replay, and BYOC boundaries.
Available: DOCS-040
Review Message Broker matrixCheck route, auth, queue, replication, CLI, SDK, and Kafka compatibility boundaries.
Available: DOCS-041
Review Concordia matrixCheck Cache, Gateway, Storage, TSDB, protocol, and future workflow boundaries.
Available: DOCS-042
Read known limitsUse the product known-limits pages when unsupported behavior or runtime outcomes change.