Supported
Implemented and validated for the exact documented scope.
Compatibility model
Verification RequiredStornamics compatibility matrices use one row model for supported, partial, unsupported, preview, future, and verification-required behavior. Every row carries notes, evidence, maturity, and a last-reviewed date so product-specific matrices can be updated without blurring runtime support and roadmap direction.
Implemented and validated for the exact documented scope.
Some behavior works, but documented gaps, limits, or exclusions apply.
Not implemented, intentionally unavailable, or rejected at runtime.
Contract, fixture, or bounded surface exists before complete customer-facing support.
Roadmap direction only; no current runtime behavior should be expected.
Evidence or reviewer acceptance is missing for a support claim.
Matrix owner: docs-platform-owner. Required reviewers: docs-qa-reviewer, docs-platform-reviewer.
| Capability | Status | Maturity | Notes | Evidence | Last reviewed |
|---|---|---|---|---|---|
| Supported row state | Supported | Live | Use only when source, tests, fixtures, or release evidence validate the documented scope. |
| 2026-08-16Due 2026-09-30Current |
| Partial row state | Partial | Verification Required | Use when behavior exists but limits, exclusions, or environment constraints change reader expectations. |
| 2026-08-16Due 2026-09-30Current |
| Unsupported row state | Unsupported | Verification Required | Use when a route, protocol, flag, operation, or deployment mode is rejected or absent. |
| 2026-08-16Due 2026-09-30Current |
| Preview row state | Preview | Preview Contract | Use for contracts, fixtures, or bounded implementations before complete customer-facing support. |
| 2026-08-16Due 2026-09-30Current |
| Future row state | Future | Future | Use for roadmap direction only; no current runtime behavior should be expected. |
| 2026-08-16Due 2026-09-30Current |
| Verification-required row state | Verification Required | Verification Required | Use when a claim needs product, docs QA, operations, security, legal, or support acceptance before publication. |
| 2026-08-16Due 2026-09-30Current |
Compatibility matrices follow an internal row standard, reusable page pattern, and shared rendering component so products can update reviewed status without changing the public model.
Available: DOCS-042
ObjectDB known limitsUnsupported S3 families, local adapter constraints, preview native API boundaries, and review-required ObjectDB claim areas.
Available: DOCS-042
Message Broker known limitsKafka listener exclusions, replication outcome boundaries, auth posture, remote CLI limits, and review-required broker claim areas.
Available: DOCS-042
Concordia known limitsLocal bearer-token identity, Gateway diagnostic writes, Storage validation flags, future protocol frames, and Edge Workflows boundaries.
Available: DOCS-042
LogDB known limitsMetrics/profile exclusions, S3 query-read behavior, replay API boundaries, external sink boundaries, and BYOC limits.
Available: DOCS-038
ObjectDB S3 Core compatibility matrixBucket, object, multipart, tag, CORS, policy, SSE, and presigned behavior for the active S3 Core profile.
Available: DOCS-039
LogDB OTLP and S3 query matrixOTLP HTTP, optional gRPC, JSON compatibility, query paths, S3 query reads, metrics/profile exclusions, and future publication work.
Available: DOCS-040
Message Broker route and auth matrixRoute families, auth modes, replication surfaces, queue behavior, and Kafka compatibility boundaries.
Available: DOCS-041
Concordia runtime boundary matrixCache, Gateway, Storage, TSDB, active compatibility, protocol fixtures, and Edge Workflows by runtime status.
Available: DOCS-043
Compatibility verification workflowOwner, review cadence, stale-warning, evidence, and release-note update workflow for matrix rows.