Concordia Reference

Concordia references keep local product binaries, alpha HTTP routes, Storage validation commands, active compatibility behavior, and fixture-backed protocol contracts separated by maturity and evidence.

Current availability

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

Reference Scope

Start with the runtime reference for what can be invoked today: loopback Cache, Time Series, and Gateway binaries; Storage startup validation flags; the active compatibility service; and the binary protocol registry. The page keeps local bearer tokens, diagnostic writes, fixture-backed frames, and future runtime behavior explicitly labeled.

Reference Pages

Available: DOCS-035
Concordia runtime reference
Product binaries, Cache/Gateway/TSDB routes, Storage startup flags, active compatibility service ports, and protocol registry boundaries.
Available: DOCS-036
Shared error and limits catalog
Map local bearer-token, idempotency, readiness, validation, and future-frame boundaries to shared retry guidance.
Available: DOCS-041
Concordia runtime boundary matrix
Classify Cache, Gateway, Storage, TSDB, active compatibility, fixtures, and Edge Workflows as alpha, future, or verification-required.
Available: DOCS-061
Concordia local curl examples
Tested local curl examples for Cache, TSDB, Gateway alpha readiness, and active compatibility diagnostics.
Available: DOCS-053
Concordia validation runbooks
Check what Cache, Gateway, Storage, TSDB, active service, protocol fixture, and validation script output proves and does not prove.