Concordia known limits.

Known Concordia unsupported behavior, local alpha runtime boundaries, validation-only surfaces, and review-required claim areas.

Current availability

Private Beta. Public beta is scheduled for December 7, 2026.

Audience

Use this page before building on Concordia local services, describing Gateway or Storage behavior, or reviewing claims about identity, routing, replication, protocol frames, or Edge Workflows.

Maturity Status

Local Alpha Behavior

Alpha

Cache, TSDB, Gateway, and active compatibility rows preserve local, diagnostic, or in-memory limits.

Future And Review Boundaries

Verification Required

Identity, routing, Storage serving, future frames, Edge Workflows, and stronger readiness wording require reviewer acceptance.

Scope

Concordia Cache, TSDB, Gateway, Storage validation, active compatibility service, protocol registry, Edge Workflows direction, and claim-promotion boundaries.

Prerequisites

Read the Concordia runtime boundary compatibility matrix.
Use the runtime reference for exact command and route behavior.

Current Limits

Concordia known limits. current limits
Limit	Applies to	Runtime behavior	Next best path	Evidence
Production identity and JWT validation	Cache, TSDB, and Gateway protected local routes	Protected routes use fixed local bearer tokens. Missing or invalid bearer tokens are rejected by the documented route handlers.	Keep docs to local admission unless security reviewers accept JWT, key-source, and identity-provider evidence.	CONC-EVID-003, CONC-EVID-011, CONC-EVID-012
Gateway commit and visibility	Gateway alpha cache write route	The alpha write route can return an accepted diagnostic response with committed:false, visible:false, and diagnostic_only:true.	Use the TSDB and Gateway tutorial for the diagnostic workflow and avoid committed-read wording.	CONC-EVID-010, CONC-EVID-011, CONC-EVID-012
General Storage serving	Storage startup validation and local-alpha flags	Dry-run and require-ready modes report readiness without opening sockets; local-alpha flags are narrow evidence commands.	Use the runtime reference and compatibility matrix to keep Storage claims validation-bound.	CONC-EVID-011, CONC-EVID-012
Future protocol frames and Edge Workflows	Future cache mutation, replica append IDs, and Edge Workflows runtime	Registry allocations and roadmap direction do not create active runtime behavior.	Keep these items future-facing until runtime paths and reviewer acceptance exist.	CONC-EVID-001, CONC-EVID-007, CONC-EVID-012

Unsupported Behavior

Concordia known limits. unsupported behavior
Scenario	What happens	Recommended action
Use Gateway accepted output as committed proof	The documented alpha response remains diagnostic and reports committed:false plus visible:false.	Describe the result as diagnostic alpha evidence only.
Run Storage dry-run expecting a serving node	Normal dry-run and require-ready modes do not open network sockets.	Use Storage commands as validation evidence until a serving contract is documented.
Depend on future protocol frame IDs	Allocated future IDs are not active runtime support by themselves.	Wait for parser, serializer, runtime path, compatibility evidence, and reviewer acceptance.

Claims Requiring Review

Concordia known limits. review-bound claims
Claim area	Required reviewer	Publication status
JWT, key-source, or identity-provider behavior	security-reviewer and concordia-product-sme	Verification Required
Owner forwarding, quorum commit, visible reads, or replication	concordia-product-sme and operations-reviewer	Verification Required
Edge Workflows runtime behavior or side-effect semantics	concordia-product-sme and docs lead	Future

Evidence

Concordia known limits. evidence
Limit or unsupported behavior	Evidence	Status
Runtime surface boundaries	DOCS-035, DOCS-041, CONC-EVID-011, and CONC-EVID-012	pending
Cache, TSDB, and Gateway local workflows	DOCS-025, DOCS-026, CONC-EVID-008, CONC-EVID-009, and CONC-EVID-010	pending
Concordia limits page artifact	DOCS-042	pending

The evidence table summarizes the reviewed basis for each known limit without exposing internal source locations.

Limits

This page summarizes current Concordia local, alpha, validation, fixture, and future boundaries.
Do not use diagnostic accepted output as committed or visible behavior.
Future protocol IDs and Edge Workflows require runtime evidence before promotion.

Safe Next Steps

Available: DOCS-041
Map runtime boundaries
Use row status and evidence before relying on local, alpha, validation, fixture, or future Concordia behavior.
Available: DOCS-035
Read runtime surface reference
Check command, route, auth, response, error, maturity, and evidence boundaries.
Available: DOCS-053
Use validation runbooks
Use proves and does-not-prove rows before interpreting local validation output.
Available
Review Concordia evidence
Confirm source records before strengthening Concordia limits wording.