Concordia runtime boundary compatibility matrix.

Matrix Snapshot

Matrix rows

15

Status values

6

Surface families

7

Audience

Use this matrix when deciding whether a Concordia Cache, Gateway, Storage, Time Series, active compatibility, protocol fixture, or Edge Workflows statement is current local alpha behavior, fixture or validation evidence, unsupported, future-facing, or still waiting on reviewer acceptance.

Maturity Status

Compatibility Scope

Status Legend

Runtime Boundary Matrix

Concordia Cache, Gateway, Storage, TSDB, active compatibility, protocol, and workflow boundary rows

Capability	Status	Maturity	Notes	Evidence	Last reviewed
Cache local binary startup	Supported	Alpha	concordia-cache-bin starts a loopback HTTP service with --bind and optional --persistence-path; persistence is node-local and off unless configured.	CONC-EVID-002 CONC-EVID-006 DOCS-035	2026-08-16Due 2026-09-30Current
Cache local HTTP routes	Supported	Alpha	/health is open; protected put, get, count, and placement routes require Authorization: Bearer local-cache-token and stay local-alpha behavior.	CONC-EVID-003 CONC-EVID-004 CONC-EVID-005	2026-08-16Due 2026-09-30Current
Time Series local HTTP shell	Partial	Alpha	concordia-tsdb-bin exposes open health, protected sample append, protected recent query, newest-first reads, and process-local retention without durability or replication.	CONC-EVID-009 CONC-EVID-011 DOCS-026	2026-08-16Due 2026-09-30Current
Gateway readiness and placement diagnostics	Partial	Alpha	Gateway health and placement diagnostics expose readiness, blockers, and cache placement inspection before writes are allowed.	CONC-EVID-010 CONC-EVID-011 DOCS-026	2026-08-16Due 2026-09-30Current
Fixture-backed Gateway placement metadata	Preview	Preview Contract	The alpha Gateway tutorial uses fixtures/metadata/placement-alpha-v2.txt for bounded placement evidence; it does not prove external metadata watches.	CONC-EVID-010 placement-alpha-v2.txt DOCS-026	2026-08-16Due 2026-09-30Current
Gateway alpha cache write route	Partial	Alpha	PUT /v1/cache/{key} can return an accepted diagnostic response only after explicit local alpha write settings, owner transport, metadata fixture, retry budget, and tenant quota gates pass.	CONC-EVID-010 CONC-EVID-011 DOCS-035	2026-08-16Due 2026-09-30Current
Storage startup validation	Preview	Preview Contract	concordia-storage-bin supports dry-run, require-ready, and validation-bound startup checks; normal dry-run opens no sockets.	CONC-EVID-011 bins/concordia-storage/src/startup.rs DOCS-035	2026-08-16Due 2026-09-30Current
Storage local-alpha boundary flags	Preview	Preview Contract	Listener, frame, owner, follower, and quorum flags are narrow evidence modes, not general Storage serving or broad write-frame handling.	CONC-EVID-011 Service.Concordia README DOCS-035	2026-08-16Due 2026-09-30Current
Active compatibility service	Partial	Alpha	The concordia compatibility service exposes loopback HTTP and TCP ports for in-memory diagnostics, active AddReplicationGroupKV frames, and legacy gossip or heartbeat frames.	CONC-EVID-011 Concordia/src/main.rs DOCS-035	2026-08-16Due 2026-09-30Current
Active binary protocol frames	Partial	Alpha	Legacy gossip, legacy heartbeat, and active AddReplicationGroupKV frame families have parser and compatibility evidence; malformed frames remain rejected.	CONC-EVID-011 crates/concordia-protocol/src/registry.rs DOCS-035	2026-08-16Due 2026-09-30Current
Future protocol registry allocations	Future	Future	Cache mutation and replica append frame IDs are registry allocations for future use; allocation alone is not runtime support.	CONC-EVID-011 crates/concordia-protocol/src/registry.rs PROJECT_MANAGEMENT.md	2026-08-16Due 2026-09-30Current
Edge Workflows runtime	Future	Future	Edge Workflows remain product direction until runtime behavior, workflow semantics, idempotency, side-effect boundaries, and reviewer acceptance exist.	CONC-EVID-001 CONC-EVID-007 PROJECT_MANAGEMENT.md	2026-08-16Due 2026-09-30Current
Production identity and JWT validation	Verification Required	Verification Required	Local bearer tokens are development admission only. JWT parsing, signature verification, key-source loading, and identity-provider integration need security acceptance.	CONC-EVID-003 CONC-EVID-011 CONC-EVID-012	2026-08-16Due 2026-09-30Current
Distributed routing, shared storage, quorum, and cross-node replication	Unsupported	Verification Required	Current docs do not approve owner forwarding, external metadata watches, quorum commit, visible reads, shared storage, restart recovery, or cross-node replication claims.	CONC-EVID-006 CONC-EVID-010 CONC-EVID-011	2026-08-16Due 2026-09-30Current
Claim promotion to stronger readiness wording	Verification Required	Verification Required	Support, security, operations, performance, scale, release, and customer-commitment wording needs separate accepted evidence before promotion.	CONC-EVID-007 CONC-EVID-011 CONC-EVID-012	2026-08-16Due 2026-09-30Current

Current Limits

Explicit Exclusions

Production identity, direct identity-provider integration, owner forwarding, external metadata watches, quorum commit, visible reads, shared storage, cross-node replication, broad Storage serving, support, availability, performance, scale, security, and customer commitments are outside the active local and validation surfaces described by this matrix.

Evidence

Internal review records track this Concordia compatibility matrix and the evidence required to change row status.

Limits

This matrix covers current Concordia local, alpha, validation, fixture, and future-facing documentation only. Local bearer tokens, diagnostic Gateway accepted writes, Storage local-alpha flags, active compatibility memory, and future protocol IDs stay scoped to the rows above.

See the runtime reference for command and route behavior, the Cache quickstart for the local Cache workflow, and the TSDB and Gateway tutorial for alpha route boundaries.

Safe Next Steps

• 

  Available: DOCS-035

  Read runtime surface reference

  Check source-backed command, route, auth, response, error, maturity, and evidence boundaries behind the matrix rows.

• 

  Available: DOCS-025

  Run the Cache quickstart

  Exercise local Cache startup, admission, key operations, placement diagnostics, and node-local persistence limits.

• Available: DOCS-026

  Try TSDB and Gateway alpha tutorial

  Append local Time Series samples, inspect Gateway readiness, and keep alpha write behavior diagnostic.

• 

  Available: DOCS-061

  Use local curl examples

  Review bounded examples for matrix rows that are local, alpha, diagnostic, or active-compatibility only.

• 

  Available: DOCS-053

  Use validation runbooks

  Translate Cache, TSDB, Gateway, Storage, active service, and protocol validation output into bounded evidence.

• 

  Available

  Review Concordia evidence

  Check source records before expanding Cache, Gateway, Storage, TSDB, active compatibility, protocol, or workflow wording.

• 

  Available: DOCS-042

  Read known limits

  See local identity, Gateway diagnostic write, Storage validation, future frame, and Edge Workflows boundaries.

• 

  Available: DOCS-043

  Track matrix review workflow

  Use the workflow for stale-row checks, evidence refresh, owner review, and release-note updates.