Local Tokens Only
Cache, TSDB, and Gateway examples use fixed local bearer tokens. They do not prove production identity or JWT verification.
Guides
Concordia guides collect local curl examples and decision support for Cache, TSDB, Gateway alpha readiness, active compatibility diagnostics, and review-bound runtime claims.
Current availability
Private Beta. Public beta is scheduled for .
Start here when a workflow is larger than a quickstart step but still needs current local evidence and visible alpha boundaries. The first Concordia guide publishes tested curl examples while keeping local bearer tokens, process-local TSDB state, Gateway diagnostic writes, and active compatibility limits in review-bound language.
Available: DOCS-061
Concordia local curl examplesTested local curl examples for Cache, TSDB, Gateway alpha readiness, and active compatibility diagnostics.
Available: DOCS-025
Concordia Cache quickstartUse the first-success path for local Cache health, bearer-token admission, key operations, placement diagnostics, and restart reload checks.
Available: DOCS-026
TSDB and Gateway alpha tutorialRun local Time Series append/query checks and Gateway readiness, placement, admission, idempotency, and diagnostic write checks.
Available: DOCS-035
Concordia runtime referenceCheck product binaries, HTTP routes, Storage startup flags, active compatibility ports, protocol registry rows, and current limits.
Available: DOCS-063
Example validationValidate example manifests, status labels, rendered routes, evidence links, validation modes, reviewers, and limits.
Cache, TSDB, and Gateway examples use fixed local bearer tokens. They do not prove production identity or JWT verification.
Gateway accepted output must keep committed:false, visible:false, and diagnostic_only:true near every alpha write example.
Active service diagnostics are migration-era compatibility evidence, not product-binary parity or future protocol-frame support.