Concordia verification dispositions.

This launch-readiness review decides how Concordia hub, quickstart, tutorials, compatibility rows, runtime references, limits, evidence, guides, local curl examples, and validation runbooks keep or bound Verification Required labels before final launch acceptance.

Decision Snapshot

Concordia routes: 12
Source groups: 2
Rows reviewed: 15
P0/P1 blockers: 0
Product lanes open: 0

Route Dispositions

DOCS-111 Concordia route Verification Required decisions
Route or surface	Current exposure	Disposition	Rationale	Evidence
Concordia hub	Controlled Beta product-family hub with alpha Cache, Gateway, Storage, Time Series, active compatibility, and future Edge Workflows labels.	Accept with limits	The hub makes uneven maturity visible and keeps local, diagnostic, validation, and future surfaces separate from broader product-family readiness.	CONC-EVID-001 and CONC-EVID-007
Cache quickstart	Local Cache first-success workflow with Alpha behavior and a Verification Required broader-claim boundary.	Accept with limits	The tutorial proves loopback Cache behavior, local bearer-token admission, key operations, placement diagnostics, TTL, stale-version checks, and node-local persistence without implying distributed deployment behavior.	CONC-EVID-002 through CONC-EVID-008 and DOCS-025
TSDB and Gateway alpha tutorial	Local TSDB append/query and Gateway readiness/write tutorial with diagnostic alpha wording.	Accept with limits	The tutorial keeps TSDB process-local and memory-only, and keeps Gateway accepted output diagnostic through committed:false, visible:false, and diagnostic_only:true.	CONC-EVID-009, CONC-EVID-010, and DOCS-026
Compatibility matrix	Row labels separate supported, partial, unsupported, preview, future, and verification-required runtime boundaries.	Accept with limits	The matrix keeps Cache, Gateway, Storage, TSDB, active compatibility, protocol, identity, routing, Edge, and claim-promotion boundaries visible until owners promote or reject rows.	CONC-EVID-012 and DOCS-041
Runtime reference	Source-backed commands, routes, auth, responses, errors, examples, maturity labels, and runtime limits.	Accept with limits	The page names product binaries and active local routes while blocking production identity, distributed routing, broad Storage serving, and future-frame runtime support.	CONC-EVID-011 and DOCS-035
Known limits	Current limits for identity, Gateway diagnostic writes, Storage validation, future protocol frames, Edge Workflows, and claim review.	Accept with limits	The page directly owns unsupported and review-required claim areas, so the conservative label helps launch reviewers rather than hiding risk.	CONC-EVID-013 and DOCS-042
Evidence index	Evidence records remain owner-pending and page maturity remains Verification Required.	Accept with limits	The page is an evidence tracker; pending status prevents local and alpha records from becoming approved product commitments.	CONC-EVID-001 through CONC-EVID-015
Guides and local curl examples	Guide family remains Verification Required while local curl examples and validation context stay bounded.	Accept with limits	The guide pages preserve current examples and references without promoting identity, routing, Storage, protocol, or workflow claims.	CONC-EVID-015 and DOCS-061
Operations and validation runbooks	Runbooks cover Cache, TSDB, Gateway, Storage, active service, protocol fixtures, validation scripts, and evidence handoff.	Accept with limits	The runbooks name what each check proves and does not prove, including identity, routing, storage, quorum, support, security, performance, scale, and customer-commitment exclusions.	CONC-EVID-014 and DOCS-053

Compatibility Row Dispositions

Concordia runtime boundary row posture
Row area	Current state	Disposition	Rationale
Cache local binary startup and local HTTP routes	Supported / Alpha	Keep alpha	The local Cache binary, protected routes, count, key, placement, TTL, stale-version, and node-local persistence evidence is source-backed, but it remains local behavior.
Time Series local HTTP shell	Partial / Alpha	Keep alpha with row limits	Append, recent query, retention, and newest-first behavior are useful local evidence but remain process-local, memory-only, non-durable, and non-replicated.
Gateway readiness diagnostics and alpha cache write route	Partial / Alpha	Keep alpha with diagnostic limits	Readiness blockers, local bearer admission, idempotency, fixture metadata, and in-process owner output are bounded alpha evidence, not committed or visible read proof.
Fixture-backed Gateway placement metadata	Preview / Preview Contract	Keep preview contract	The fixture is valuable compatibility evidence, but it does not prove external metadata watches or deployed placement control.
Storage startup validation and local-alpha boundary flags	Preview / Preview Contract	Keep preview contract	Dry-run, require-ready, listener, frame, owner, follower, and quorum flags are narrow evidence modes, not general Storage serving.
Active compatibility service and active binary protocol frames	Partial / Alpha	Keep alpha with row limits	The active service and legacy or active frame families have local HTTP/TCP and parser evidence, but state remains in-memory and future frames stay excluded.
Future protocol registry allocations and Edge Workflows runtime	Future / Future	Keep future	Registry allocation and product direction do not create runtime behavior until routes, parsers, serializers, workflow semantics, side-effect boundaries, and evidence land.
Production identity and JWT validation	Verification Required / Verification Required	Accept with limits	Local bearer-token checks are development admission only; JWT parsing, signature verification, key-source loading, and identity-provider integration need security acceptance.
Distributed routing, shared storage, quorum, visible reads, and replication	Unsupported / Verification Required	Keep unsupported and review-bound	Current docs do not approve owner forwarding, external metadata watches, quorum commit, visible reads, shared storage, restart recovery, or cross-node replication.
Claim promotion to stronger readiness wording	Verification Required / Verification Required	Accept with limits	Support, security, operations, performance, scale, release, and customer-commitment wording needs separate accepted evidence before promotion.

Launch Blocking Rules

Concordia blocker rules before DOCS-104
Severity	Condition	Required action
P0	A Concordia route exposes private source paths, credentials, internal deployment details, customer data, or unsupported security/legal/support promises.	Remove the exposure before launch review continues.
P1	A core Concordia page presents local alpha behavior as production identity, distributed routing, shared storage, quorum commit, visible reads, broad Storage serving, GA, support, security, availability, performance, or scale.	Rewrite, relabel, or block through DOCS-104.
P2	A page or row keeps Verification Required because behavior is local, alpha, validation-bound, fixture-backed, future-facing, owner-pending, or awaiting sensitive review.	Accept with limits and keep the evidence or known-limit path visible.
P3	Source notes, README, generated manifests, project-management records, or automation mention Concordia labels as review taxonomy.	Keep as tracker language unless DOCS-114 changes it.

Remaining Boundaries

DOCS-113 and DOCS-114

Still owns

Cross-product concepts, operations, support, privacy, community, roadmap source notes, and generated metadata.

DOCS-104

Still owns

Exact build, reviewer signoffs, accepted risks, launch watch, and go/no-go decision.