Alpha Scope
Concordia Cache, TSDB, and Gateway docs can name local HTTP workflows, but broader product-family readiness stays alpha and evidence-bound.
Evidence index
Verification Required
Concordia Evidence
Reviewed evidence for Concordia Cache local behavior, Gateway alpha boundaries, Time Series local model, Storage validation, active compatibility, future workflows, and claim boundaries.
Current availability
Private Beta. Public beta is scheduled for .
Evidence Records
| Evidence ID | Claim or surface | Type | Evidence basis | Owner | Evidence date | Status | Last checked |
|---|---|---|---|---|---|---|---|
| CONC-EVID-001 | Concordia is framed as a Rust product family around Cache, Time Series, and Edge Workflows on a shared platform foundation. | source | Product-family overview and positioning review | concordia-product-sme | 2026-08-13 | pending | 2026-08-13 |
| CONC-EVID-002 | The concordia-cache binary starts an HTTP Cache service on a loopback bind address, supports --bind and --persistence-path, and keeps /health open. | source | Cache service startup and local runbook review | concordia-product-sme | 2026-08-13 | pending | 2026-08-13 |
| CONC-EVID-003 | Cache protected routes require Authorization: Bearer local-cache-token and return stable missing or invalid authorization error codes. | source | Cache protected-route authorization review | security-reviewer | 2026-08-13 | pending | 2026-08-13 |
| CONC-EVID-004 | Local Cache put, get, count, TTL metadata, stale-version conflict, and equal-version conflict behavior are implemented in the Cache HTTP adapter and product crate. | source | Cache HTTP adapter and product behavior review | concordia-product-sme | 2026-08-13 | pending | 2026-08-13 |
| CONC-EVID-005 | Cache placement diagnostics return tenant, dataset, hash version, partition, replica node IDs, and routing_enabled:false for the local diagnostic path. | source | Cache placement diagnostic review | concordia-product-sme | 2026-08-13 | pending | 2026-08-13 |
| CONC-EVID-006 | Optional Cache binary persistence reloads accepted local entries from the same node-local binary snapshot file after restart. | source | Cache persistence and restart behavior review | operations-reviewer | 2026-08-13 | pending | 2026-08-13 |
| CONC-EVID-007 | The Concordia fact sheet separates local Cache validation, Gateway alpha, Time Series local model, Storage validation, active compatibility, future workflows, and claims requiring verification. | manual-review | Concordia fact-sheet review | docs-lead | 2026-08-13 | pending | 2026-08-13 |
| CONC-EVID-008 | The Concordia Cache quickstart covers local startup, bearer-token admission, put/get/count, stale-version behavior, TTL expiration, placement diagnostics, restart reload, cleanup, and local limits. | source | Concordia Cache quickstart review | docs-qa-reviewer | 2026-08-13 | pending | 2026-08-13 |
| CONC-EVID-009 | The Concordia TSDB local HTTP shell exposes open health, protected sample append, protected recent query, newest-first records, and process-local retention behavior. | source | TSDB local HTTP shell behavior review | concordia-product-sme | 2026-08-13 | pending | 2026-08-13 |
| CONC-EVID-010 | The Concordia Gateway alpha tutorial covers readiness blockers, protected local bearer admission, idempotency validation, fixture-backed placement metadata, and diagnostic accepted write behavior through the in-process owner runtime. | source | Gateway alpha tutorial and validation review | concordia-product-sme | 2026-08-13 | pending | 2026-08-13 |
| CONC-EVID-011 | The Concordia runtime reference separates product binaries, Cache/Gateway/TSDB HTTP routes, Storage startup flags, active compatibility service ports, and protocol registry allocations by runtime-active, validation, diagnostic, and future-frame status. | source | Runtime reference and protocol registry review | concordia-product-sme | 2026-08-16 | pending | 2026-08-16 |
| CONC-EVID-012 | The Concordia runtime boundary compatibility matrix separates Cache, Gateway, Storage, TSDB, active compatibility, protocol fixtures, Edge Workflows, and claim-promotion gates by supported, partial, unsupported, preview, future, and verification-required status. | source | Runtime boundary compatibility matrix review | docs-qa-reviewer | 2026-08-16 | pending | 2026-08-16 |
| CONC-EVID-013 | The Concordia known limits page explains local bearer-token identity, Gateway diagnostic writes, Storage validation-only flags, future protocol frames, Edge Workflows, and review-required claim areas. | source | Concordia known-limits review | docs-qa-reviewer | 2026-08-16 | pending | 2026-08-16 |
| CONC-EVID-014 | The Concordia validation runbooks document Cache, Gateway, Storage, TSDB, active service, protocol fixture, validation-script, and evidence handoff workflows with explicit proves and does-not-prove boundaries. | source | Validation runbook review | operations-reviewer | 2026-08-16 | pending | 2026-08-16 |
| CONC-EVID-015 | The Concordia local curl examples cover Cache local routes, TSDB local routes, Gateway alpha readiness and diagnostic accepted writes, and active compatibility HTTP diagnostics with product tests and local validation scripts. | test | Local curl examples and validation-script review | docs-qa-reviewer | 2026-08-16 | pending | 2026-08-16 |
Publication Boundary
Identity Boundary
The local bearer token is not production JWT parsing, signature verification, key-source loading, or identity-provider integration.
Routing Boundary
Placement diagnostics expose hash and replica information with routing disabled; they do not approve owner forwarding or cross-node routing claims.
Gateway Boundary
Gateway alpha writes are fixture-backed and diagnostic; they do not approve quorum commit, visible reads, TCP owner forwarding, or external metadata-watch claims.
Persistence Boundary
Binary persistence reloads a local snapshot file. It does not approve shared storage, replication, recovery, availability, support, scale, or performance claims.