Source-backed lookup for Concordia local product binaries, HTTP routes, Storage validation flags, active compatibility service ports, and protocol registry boundaries.
Current availability
Private Beta. Public beta is scheduled for .
Audience
Use this page when you need the current command, route, auth, response, error, maturity, and evidence boundaries for Concordia runtime surfaces. It keeps active behavior separate from fixtures, validation modes, and future frame reservations.
Local Cache starts on 127.0.0.1:9101 by default, supports --bind, and can reload a node-local binary snapshot when --persistence-path is provided.
Reference fields
Method or command:concordia-cache-bin; GET /health; GET /v1/count; PUT /v1/{key}; GET /v1/{key}; GET /v1/{key}/placement.
Auth or permissions:/health is open. Protected routes require Authorization: Bearer local-cache-token.
Request or input:PUT /v1/{key} accepts value plus optional crdt_version and ttl_seconds; other protected routes use the path and headers.
Response or output: Health returns status and product. Writes return inserted, updated, ignored_stale, or ignored_equal_version. Placement returns routing_enabled:false.
Errors: Invalid CLI args exit before serving. Protected routes return missing_authorization or invalid_bearer_token; missing keys return not_found.
Limits: Placement is diagnostic and local persistence is node-local. This does not prove owner forwarding, shared storage, or cross-node behavior.
Evidence: CONC-EVID-002 through CONC-EVID-006 and CONC-EVID-011.
Concordia Time Series
Source-backed
The local TSDB shell starts on 127.0.0.1:9201 by default and stores samples in process memory with a configurable per-series retention count.
Reference fields
Method or command:concordia-tsdb-bin --bind <ADDR> --retention-max-records <N>; GET /health; POST /v1/samples; POST /v1/query/recent.
Auth or permissions:/health is open. Sample append and recent query require Authorization: Bearer local-tsdb-token.
Request or input: Append uses tenant, dataset, series name, tags, timestamp, and value. Recent query uses the same identity plus limit.
Response or output: Health reports local_memory_only, durability:none, replication:none, and projection_freshness:unavailable. Recent queries return newest-first records.
Errors: CLI rejects non-loopback binds and zero retention. Routes reject missing auth, malformed JSON, invalid series input, duplicate timestamps, and unavailable store state.
Limits: Accepted samples are local to the running process and are not persistent, replicated, or projection-fresh.
Evidence: CONC-EVID-009 and CONC-EVID-011.
Concordia Gateway
Source-backed
Gateway starts as a loopback diagnostics shell on 127.0.0.1:9301; writes stay blocked until explicit alpha-ready flags clear readiness blockers.
Reference fields
Method or command:concordia-gateway-bin; GET /health; GET /placement/cache; PUT /v1/cache/{key}.
Auth or permissions: The default protected write route requires Authorization: Bearer local-gateway-token; --admission disabled is diagnostic only.
Request or input: Startup accepts config-file, bind, write mode, owner transport, admission token, metadata fixture, retry budget, tenant quota, and route-boundary flags. Writes require Idempotency-Key and cache write JSON.
Response or output: Health reports readiness blockers. Placement reports accepted metadata state. Alpha-ready in-process writes can return diagnostic accepted output with committed and visible labels still false.
Errors: Startup rejects unsafe or malformed config. Writes can fail with auth, idempotency, metadata, quota, owner, or readiness blocker reason codes.
Limits: The alpha route does not approve broad owner forwarding, external metadata watches, user-visible committed reads, or cross-node routing.
Evidence: CONC-EVID-010 and CONC-EVID-011.
Concordia Storage
Source-backed
Storage currently provides startup validation and explicit local-alpha boundary commands rather than a general HTTP service.
Reference fields
Method or command:concordia-storage-bin --dry-run; --require-ready; --listener-bind-boundary; --process-frame-rejection-boundary; owner/follower boundary flags.
Auth or permissions: n/a: local startup validation command.
Request or input: Flags cover node ID, runtime root, WAL path and sync policy, snapshot directory, replica transport, TCP bind, replica targets, and boundary mode.
Response or output: Dry-run prints a deterministic startup report. Require-ready exits nonzero when blockers remain. Boundary modes print labeled evidence and exit.
Errors: Unknown or malformed flags reject startup input. Boundary modes fail closed when the TCP shape or readiness blockers do not match requirements.
Limits: Dry-run and require-ready do not open sockets. Boundary flags are narrow evidence commands with explicit side-effect labels.
Evidence: CONC-EVID-011 and bins/concordia-storage/src/startup.rs.
Active Compatibility Service
Source-backed
The migration-era concordia service remains runnable from Concordia/ while product binaries take over behavior incrementally.
Auth or permissions: Current active HTTP routes do not require authentication.
Request or input: HTTP covers nodes, status, details, health, local cache diagnostics, and timestamps. TCP accepts active binary frames.
Response or output: Accepted AddReplicationGroupKV frames update the node local in-memory cache and can be inspected through GET /node/cache/{key}.
Errors: Port mapping errors reject invalid node IDs. Protocol parsing rejects malformed or unsupported frames. Missing cache keys return 404.
Limits: State is in memory and local diagnostics do not create a replicated or durable write guarantee.
Evidence: CONC-EVID-011, Concordia/src/main.rs, Concordia/src/http/routes.rs, and Concordia/src/gossip/listener.rs.
Protocol Registry
Registry allocation names a message type and family. It does not make a future frame active runtime behavior until the matching parser, serializer, listener, route, and compatibility evidence are wired.
cd /path/to/Service.Concordia
cargo run -p concordia-cache-bin -- --bind 127.0.0.1:9101
cargo run -p concordia-tsdb-bin -- --bind 127.0.0.1:9201 --retention-max-records 1000
cargo run -p concordia-gateway-bin -- --bind 127.0.0.1:9301
cargo run -p concordia-storage-bin -- --dry-run
cargo run -p concordia -- --region 1 --replication-group 1 --node-id 1
Limits
Local Admission Only
Cache, TSDB, and Gateway local bearer tokens are development admission checks. Production JWT parsing, signature verification, and key-source behavior are outside this reference.
Diagnostic Writes
Gateway and active-service accepted writes must stay labeled as local or diagnostic unless the source explicitly reports committed and visible proof.
Storage Boundary Flags
Storage listener, frame, owner, follower, and quorum flags are local-alpha evidence modes with narrow side effects.
Future Frames
Protocol IDs reserved for future cache mutation or replica append frames are not active runtime behavior by registry allocation alone.
Review Boundary
Internal review records track this runtime reference and the evidence required to change any supported, diagnostic, or future-frame status. Review the evidence index before strengthening runtime claims.
