Guide

AlphaVerification Required

Concordia local curl examples.

Tested local curl examples for Concordia Cache, TSDB, Gateway alpha readiness, and active compatibility diagnostics with local-only and alpha boundaries visible.

Current availability

Private Beta. Public beta is scheduled for .

Example Status

Local Curl Examples

Alpha

These examples are tested through product route tests, smoke scripts, and active endpoint tests.

Review Boundary

Verification Required

Product SME, docs QA, security, and operations reviewers still need to accept exact local token, alpha write, and active compatibility wording.

Example Snapshot

Example status
Tested
Example areas
4
Validation
Product scripts
Evidence
CONC-EVID-015

Source Files

Example source bundle
WorkflowStatusValidationSource
Cache local curl workflowtested route behaviorcargo test -p concordia-cache -p concordia-cache-bindocs/examples/concordia/local-curl-examples/snippets/cache-local-curl.sh
TSDB local curl workflowtested route behaviorValidate-TSDB-Local.shdocs/examples/concordia/local-curl-examples/snippets/tsdb-local-curl.sh
Gateway alpha curl workflowtested alpha smoke behaviorValidate-Gateway-Alpha-Route-Smoke.shdocs/examples/concordia/local-curl-examples/snippets/gateway-alpha-curl.sh
Active compatibility diagnosticstested endpoint behaviorValidate-SingleNode.shdocs/examples/concordia/local-curl-examples/snippets/active-compatibility-diagnostics-curl.sh

Example Guardrails

Local Tokens Only

The bearer tokens in these examples are development admission checks. They are not production identity-provider, JWT signature, or key-source examples.

Memory And Diagnostics

TSDB samples and active compatibility state are local process memory; Gateway accepted writes are diagnostic alpha evidence only.

No Readiness Promotion

These examples do not approve distributed routing, shared storage, quorum commit, visible reads, cross-node replication, external metadata watches, support, scale, release readiness, or GA claims.

Local Service and curl Snippets

Active compatibility examples use HTTP diagnostics only. The TCP AddReplicationGroupKV frame path is validated by the active single-node harness, not by curl. Run service commands from the Concordia repository in separate terminals before using the curl snippets.

Concordia local shell and curl examples

Switch between local service startup, Cache, TSDB, Gateway alpha, and active compatibility diagnostics.

Shell

Local service commands to run from the Concordia repository in separate terminals.

# Run from <Concordia repository> in separate terminals.
cargo run -p concordia-cache-bin -- \
  --bind 127.0.0.1:9101 \
  --persistence-path "${TMPDIR:-/tmp}/concordia-cache-docs-061.bin"

cargo run -p concordia-tsdb-bin -- \
  --bind 127.0.0.1:9201 \
  --retention-max-records 2

cargo run -p concordia-gateway-bin -- \
  --bind 127.0.0.1:9301 \
  --write-mode alpha-enabled \
  --owner-transport in-process \
  --admission-token local-gateway-token \
  --metadata-fixture fixtures/metadata/placement-alpha-v2.txt \
  --metadata-fallback fail-closed \
  --retry-budget 1:1:250 \
  --tenant-quota-max-in-flight 64 \
  --tenant-quota-retry-after-millis 250

cargo run -p concordia -- \
  --region 1 \
  --replication-group 1 \
  --node-id 1

Coverage Map

Behavior, surface, and evidence mapping
BehaviorSurfaceEvidenceMaturity
Cache health, local admission, put/get, count, and placementconcordia-cache-bin HTTP routesCONC-EVID-002 through CONC-EVID-008Alpha; local bearer token only
TSDB sample append and recent queryconcordia-tsdb-bin HTTP routesCONC-EVID-009 and CONC-EVID-011Alpha; process-local memory only
Gateway readiness, placement, and diagnostic accepted writeconcordia-gateway-bin HTTP routesCONC-EVID-010 and CONC-EVID-011Alpha; diagnostic accepted output only
Active service HTTP diagnosticsconcordia active compatibility serviceCONC-EVID-011 and Validate-SingleNode.shAlpha; migration-era compatibility evidence

Expected Output

Outputs use safe synthetic tenants, datasets, keys, values, local tokens, and loopback ports. Exact dynamic fields are summarized rather than copied wholesale.

Text

Expected Output

Safe synthetic output shapes for the local alpha routes and validation scripts.

Cache:
HTTP/1.1 200 OK
{"status":"ok","product":"concordia-cache"}
HTTP/1.1 401 Unauthorized
{"error":"missing_authorization"}
HTTP/1.1 201 Created
{"key":"customer:42","outcome":"inserted","crdt_version":10,"expires_at_micros":null}

TSDB:
{"status":"ok","product":"concordia-tsdb","storage":"local_memory_only","durability":"none","replication":"none"}
{"outcome":"accepted","timestamp_micros":100,"retained_record_count":1,"durability":"local_memory_only","replication":"none"}

Gateway:
{"writes_enabled":true,"alpha_write_ready":true,"alpha_write_blockers":[]}
{"outcome":"accepted","accepted":true,"durable":true,"committed":false,"visible":false,"diagnostic_only":true}

Active compatibility:
HTTP/1.1 200 OK
"initializing"
{"region":1,"replicationGroup":1,"nodeId":1,"status":"initializing"}

Validation And Evidence

DOCS-061 validation evidence
CommandWhat it provesReviewer status
cargo test --manifest-path Cargo.toml -p concordia-cache -p concordia-cache-binCache store behavior, HTTP health, local bearer-token admission, put/get/count, TTL, stale writes, placement diagnostics, and persistence parsing.passed 40/40 on 2026-08-16
./Support/Validate-TSDB-Local.shTSDB model behavior, local HTTP route behavior, CLI constraints, retention, and local-only claim guardrails.passed 71 tests plus claim checks on 2026-08-16
./Support/Validate-Gateway-Alpha-Route-Smoke.shGateway disabled write-mode safety, alpha-ready health, placement fixture output, admission, idempotency, and diagnostic accepted write output.passed on 2026-08-16
./Support/Validate-SingleNode.shActive compatibility HTTP/TCP endpoint behavior for a single local node.passed 9/9 on 2026-08-16

Route Maturity Notes

Concordia examples stay scoped to local Cache, process-local TSDB, Gateway diagnostic alpha writes, and active compatibility diagnostics. Use the runtime boundary matrix and known limits before strengthening identity, routing, storage, replication, protocol, support, readiness, or Edge Workflows claims.

Safe Next Steps

  • Available: DOCS-025

    Run the Cache quickstart

    Use the first-success path for Cache before adapting these curl snippets.

  • Available: DOCS-026

    Try TSDB and Gateway tutorial

    Follow the full TSDB and Gateway alpha flow with readiness blockers and diagnostic write context.

  • Available: DOCS-035

    Read runtime reference

    Review route shapes, local tokens, response fields, errors, maturity, and evidence.

  • Available: DOCS-053

    Use validation runbooks

    Check what each product script proves and what remains outside the local alpha claim.

  • Available: DOCS-063

    Add example validation

    Use the manifest gate alongside product validation scripts before changing status or evidence wording.