Compatibility workflow

Verification Required

Compatibility verification workflow.

Use this workflow to keep product matrices tied to tests, fixtures, references, release notes, evidence records, owner review, and visible stale-row warnings.

Workflow Snapshot

Matrix owners
4
Default cadence
45 days
Warning window
14 days
Stale rows
0

Owner And Cadence Registry

Compatibility matrix review ownership
MatrixOwnerReviewersCadenceReview basisReview status
ObjectDB S3 Core compatibilityobjectdb-docs-owner
  • objectdb-product-sme
  • docs-qa-reviewer
45 days; warn 14 days before dueObjectDB S3 Core matrix review
2026-08-16Due 2026-09-30Current
LogDB OTLP and S3 query compatibilitylogdb-docs-owner
  • logdb-product-sme
  • docs-qa-reviewer
45 days; warn 14 days before dueLogDB OTLP and S3 query matrix review
2026-08-16Due 2026-09-30Current
Message Broker route and auth compatibilitymessage-broker-docs-owner
  • message-broker-product-sme
  • docs-qa-reviewer
45 days; warn 14 days before dueMessage Broker route and auth matrix review
2026-08-16Due 2026-09-30Current
Concordia runtime boundary compatibilityconcordia-docs-owner
  • concordia-product-sme
  • docs-qa-reviewer
45 days; warn 14 days before dueConcordia runtime boundary matrix review
2026-08-16Due 2026-09-30Current

Update Triggers

ObjectDB S3 Core compatibility

  • S3 profile, route, local adapter, credential, or unsupported behavior change
  • ObjectDB evidence index or product reference update

LogDB OTLP and S3 query compatibility

  • OTLP, query, S3 query-read, BYOC, metrics, profile, or replay behavior change
  • LogDB evidence index, reference, or release-note update

Message Broker route and auth compatibility

  • Route, auth, queue, replication, CLI, SDK, or Kafka compatibility change
  • Message Broker evidence index, reference, tutorial, or release-note update

Concordia runtime boundary compatibility

  • Cache, Gateway, Storage, TSDB, protocol, or Edge Workflows boundary change
  • Concordia evidence index, reference, tutorial, or release-note update

Review Workflow

Collect Change Signals

Check product source changes, tests, fixtures, generated references, release notes, evidence indexes, and known-limits pages for rows that need review.

Refresh Evidence

Update evidence IDs, fixture names, release-note references, or owner signoff before changing any row status or maturity.

Review Row Wording

Product SME reviews runtime truth; docs QA checks notes, unsupported behavior, stale dates, evidence, and copy/paste safety.

Update The Matrix

Change the rendered matrix, evidence index, known-limits links, and internal tracking records in the same PR when behavior changes.

Record The Date

Set `last_reviewed` only after required reviewers accept the row for the stated scope.

Stale Warning Rules

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.

Review Boundary

Compatibility review records are maintained internally. Public matrices should expose owner, reviewer, cadence, evidence ID, and review status without publishing private source locations.

Safe Next Steps

  • Available: DOCS-038

    Review ObjectDB matrix

    Check S3 Core compatibility rows, unsupported S3 family behavior, and local adapter limits.

  • Available: DOCS-039

    Review LogDB matrix

    Check OTLP, query, S3 query-read, signal exclusion, replay, and BYOC boundaries.

  • Available: DOCS-040

    Review Message Broker matrix

    Check route, auth, queue, replication, CLI, SDK, and Kafka compatibility boundaries.

  • Available: DOCS-041

    Review Concordia matrix

    Check Cache, Gateway, Storage, TSDB, protocol, and future workflow boundaries.

  • Available: DOCS-042

    Read known limits

    Use the product known-limits pages when unsupported behavior or runtime outcomes change.