Cross-Product Glossary

A maturity label for local, early, or limited surfaces that can be evaluated only inside the boundaries named on the owning page.

• Concordia: Use for current Cache, Gateway, Storage, and Time Series local evidence unless a page names a stronger status.

A configured credential used by examples or services to protect non-health routes in a local or controlled evaluation.

• Message Broker: One of the documented runtime authentication modes for protected broker routes.
• LogDB: Relevant to authenticated query examples; product pages still need to name the exact route and environment setting.

A reviewable record, export, packet, or log that supports a specific docs statement at the stated maturity level.

• Message Broker: Audit inspection and export are controlled-beta route families, not a support promise by themselves.
• LogDB: Replay and checkpoint wording should point to local audit evidence before customer-facing claims expand.

An object-storage namespace used by S3-style workflows and storage examples.

• ObjectDB: Use for scoped S3 Core bucket discovery, lifecycle basics, and selected configuration behavior.
• LogDB: Use only when discussing approved-bucket evidence for S3 publication or query-read direction.

Bring your own cloud: a deployment or packaging direction where the customer's account or environment owns the cloud resources.

• LogDB: Current docs must keep BYOC behind clean-account proof, S3 publication conformance, and support review.
• ObjectDB: Related to local-first and sovereign deployment discussion, but not an availability or disconnected-operation claim.

A Concordia product surface for local key/value behavior, count checks, TTL or version behavior, and placement diagnostics.

• Concordia: Keep Cache copy tied to local smoke validation until deployment, authorization, and operations evidence expands.

The exact scope that a public statement is allowed to cover based on source evidence, maturity label, and reviewer signoff.

• ObjectDB: Durability, S3 breadth, security, support, performance, and scale statements require named evidence.
• Message Broker: Replication, Kafka compatibility, and named-pilot readiness need selected packet evidence before stronger wording.
• LogDB: S3 publication, replay APIs, external sinks, and BYOC claims remain bounded by current evidence.

A scoped statement about which clients, protocols, operations, or behaviors are expected to work and which are excluded.

• ObjectDB: Means versioned S3 compatibility profiles such as s3-core-v1, never blanket S3 or IAM parity.
• Message Broker: Kafka wording refers to a typed prototype over the native contract, not a Kafka protocol listener.
• Concordia: Compatibility can describe active local service and protocol fixtures, not equal maturity across the family.
• LogDB: Often refers to OTLP HTTP JSON compatibility or S3 query-read selection, each with its own limits.

A named, versioned profile that lists included, partial, unsupported, preview, or future behavior.

• ObjectDB: s3-core-v1 is the first named profile and is the safe entry point for S3 wording.

A maturity label for a limited evaluation surface whose docs must keep scope, gaps, and signoff requirements visible.

• Message Broker: Use for the broker's current stream, replay, queue, diagnostics, auth, and replication-status documentation.

A saved read position used to continue stream or consumer-group processing from a known point.

• Message Broker: Use with commit, rewind, consumer-group inspection, and replay wording; keep it separate from LogDB query pagination.

A named grouping or filter boundary used by examples, queries, or source records. The owning product page defines the exact field.

• LogDB: Dataset is a query filter alongside source time, ingested time, record ID, trace ID, and pagination.
• ObjectDB: Use cautiously for native object-platform concepts until public references define a concrete route or field.

A queue outcome for work that cannot continue through normal claim, retry, or acknowledgment handling.

• Message Broker: Use with shared-queue retry and mutation operations in controlled-beta docs.

A URL-shaped access path used to delegate object upload or download work within a scoped compatibility profile.

• ObjectDB: Included in s3-core-v1 wording with browser POST uploads; do not imply every AWS URL behavior is covered.

A collected set of runtime observations used for investigation, review, or support-boundary discussion.

• Message Broker: A controlled-beta route family that can support pilot evidence without creating a support commitment.
• Concordia: Gateway and placement diagnostics are local or alpha-scoped unless the page states otherwise.

A bounded statement about what data remains available after a named failure model, topology, software version, and recovery path.

• ObjectDB: Requires topology, hardware, fault-model, and repair evidence before customer-facing wording expands.
• Message Broker: Strict cross-site durability wording needs selected packet evidence and operations review.
• LogDB: Direct-ingest durability must name WAL mode, segment publication, and process or node evidence.
• Concordia: Local or diagnostic evidence must not be treated as distributed durability proof.

A Concordia product direction for workflow actions connected to Time Series input. Public docs treat it as future-facing until runtime support exists.

• Concordia: Keep in Future status until implementation, workflow semantics, and side-effect boundaries are approved.

A routable HTTP or protocol address described by a product reference, quickstart, or operations page.

• LogDB: Endpoint JSON ingestion/readback is distinct from native OTLP and query routes.
• ObjectDB: S3 endpoint routes should stay tied to the named compatibility profile.

The timestamp associated with an event's meaning in the workload, distinct from when a service accepted it.

• Message Broker: Part of the temporal broker model together with ingest time, offsets, cursors, and replay.
• LogDB: Use source-time or signal timestamp wording when the route or payload defines the field.

A read operation that retrieves records from a stream or product route without implying queue ownership.

• Message Broker: Use fetch for stream records; use claim, ack, nack, renew, retry, or dead-letter for shared queue work.

A maturity label for product direction that is useful context but not a customer-usable surface today.

• Concordia: Edge Workflows are future-facing until runtime support exists.
• LogDB: Public replay APIs and external sinks remain future work unless later evidence changes that status.

A product-owned entry point that translates or admits requests for a narrower product surface. The meaning changes by product.

• ObjectDB: The S3 compatibility gateway is scoped by named profiles and does not imply every S3 or AWS IAM behavior.
• Concordia: Gateway refers to an alpha binary with diagnostics and protected local write behavior.
• LogDB: Use endpoint, ingest route, or query route unless a page intentionally names a gateway component.

A protocol option for services or examples where the product docs explicitly state that gRPC is exposed.

• LogDB: Optional OTLP/gRPC logs and traces are separate from native OTLP HTTP/protobuf and JSON compatibility routes.

A route used to check whether a local service is running and ready enough for the next documented step.

• Message Broker: Health is listed separately from protected runtime routes.
• Concordia: Health checks support local smoke paths; they do not prove broader deployment behavior.

The act of accepting records, objects, messages, logs, traces, or payloads into a product-owned route or workflow.

• Message Broker: Usually expressed as publishing records into streams before fetch, replay, or queue processing.
• LogDB: Covers endpoint JSON, native OTLP HTTP/protobuf, OTLP JSON compatibility, and optional OTLP/gRPC routes.

The time at which a service accepts a record, distinct from source time or event time.

• Message Broker: Part of the temporal model used with offsets, cursors, and replay.
• LogDB: One of the query boundaries that can sit beside source time and dataset filters.

A compatibility-facing adapter for Kafka-shaped concepts. Current broker docs must keep it separate from a Kafka protocol listener.

• Message Broker: The current surface is a typed prototype over the native broker contract.

A temporary claim on queue work that must be acknowledged, renewed, retried, or released through product routes.

• Message Broker: Use with shared-queue claim, ack, nack, renew, retry, and dead-letter operations.

A maturity label for behavior that can be documented as currently available within the precise scope named by the page.

• ObjectDB: Use only for the narrow S3 Core behavior the page and evidence identify.
• LogDB: Use for current local ingest, segment publication, and query behavior only where the page has evidence.

A local implementation path that helps examples and smoke checks run without implying final distributed behavior.

• ObjectDB: Name the data directory, platform capability, and failure-mode limits near local adapter claims.

A product posture where authorized local operation is part of the design, while hosted or external control surfaces remain explicitly scoped.

• ObjectDB: Do not turn this posture into a broad disconnected-operation, uptime, or support claim without release evidence.

A structured record that describes the contents, metadata, or publication state of a stored artifact.

• ObjectDB: Native object manifests are preview-contract direction until public references and evidence are ready.
• LogDB: Segment bundle v1 uses a manifest-controlled bundle and manifest-last local publication model.

Descriptive fields attached to an object, record, segment, or route result. The owning page defines which fields are available.

• ObjectDB: User metadata is part of the s3-core-v1 object behavior.
• LogDB: Segment bundles include retention and encryption metadata fields.
• Message Broker: Route responses and audit records may expose metadata, but exact fields belong in the HTTP reference.

A configured trust file used by mutual TLS authentication modes where a product explicitly supports it.

• Message Broker: One supported runtime authentication mode for non-health routes when configured.

A product's own API contract, separate from compatibility-shaped adapters or external protocol surfaces.

• ObjectDB: Native object versions, manifests, policies, placement, and events remain preview-contract language.
• Message Broker: The native contract is the source for stream, cursor, queue, retry, and dead-letter operations.

A stored item addressed through object-storage workflows. Do not reuse the word for unrelated telemetry or messaging records without context.

• ObjectDB: Object means the S3 Core item handled through single-object CRUD, range reads, metadata, tags, and multipart upload.
• LogDB: A segment bundle may be stored in an object store, but the telemetry record or segment is not an ObjectDB object.

A key/value marker attached to an object when the compatibility profile includes tag behavior.

• ObjectDB: Tags are included in s3-core-v1 wording; lifecycle or replication behavior tied to tags is excluded unless a later profile adds it.

A numeric or ordered position in a stream used to fetch, replay, or commit processing progress.

• Message Broker: Use with stream records, cursors, and replay; do not substitute it for LogDB record IDs.

The telemetry signal ecosystem used by LogDB examples for logs and traces over OTLP routes.

• LogDB: Current docs distinguish native OTLP HTTP/protobuf, optional OTLP/gRPC, and OTLP HTTP JSON compatibility.

A retained telemetry artifact organized as Parquet data plus bundle metadata and indexes.

• LogDB: Segment bundle v1 uses Parquet data, statistics, identifier indexes, retention metadata, and encryption metadata fields.

A policy direction for where data should live based on durability, residency, latency, retention, or cost intent.

• ObjectDB: Placement is product direction and must stay tied to evidence before promising a specific outcome.
• Concordia: Placement diagnostics in local Cache flows are not the same as final distributed placement behavior.

A maturity label for API or behavior shape that can guide implementation but still needs evidence before stronger public claims.

• ObjectDB: Use for native object model, manifests, policies, placement, and events until references are ready.
• LogDB: Use around S3 publication, replay API, or BYOC direction when the current page lacks stronger evidence.

A route used to read or search retained data according to the filters, limits, and authentication named by the reference.

• LogDB: POST /v1/query searches local segment bundles by default and can read from an explicitly configured S3 query store.

A work-distribution model where records are claimed, acknowledged, retried, or moved to dead-letter handling.

• Message Broker: The shared queue is modeled over durable broker records; do not imply every external queue pattern is covered.

A read operation that requests a byte range from an object rather than the whole object.

• ObjectDB: Included in s3-core-v1 object behavior and should be documented with the profile's explicit exclusions nearby.

A workflow that re-reads retained records or telemetry selections from a known point or filter. The product defines the boundary.

• Message Broker: Replay is a controlled-beta stream workflow tied to offsets, time, cursors, and current route behavior.
• LogDB: Local replay coordinator behavior can preview retained segment selections; public replay APIs and external sinks remain gated.

A local proof mode where WAL records require a local replica quorum before segment publication.

• LogDB: LOGDB_WAL_DURABILITY_MODE=replicated-local is not the final distributed WAL service.

A route or report that describes replication-related state without, by itself, proving an end-to-end outcome.

• Message Broker: Use with worker polling and target apply wording; cross-site outcomes need selected packet evidence.

The period or policy shape for keeping records, objects, or telemetry artifacts. Specific behavior belongs in the product limits or reference page.

• ObjectDB: Roadmap placement and policy wording can mention retention intent, not an unqualified promise.
• LogDB: Segment bundle metadata includes retention fields, while broader retention claims require evidence and review.

A group of related routes documented together because they support one product workflow or operations task.

• Message Broker: Route families include stream, replay, queue, audit, metrics, diagnostics, auth, and replication surfaces.
• LogDB: Ingest, query, and optional gRPC routes should stay separated by signal and maturity.

The scoped ObjectDB compatibility path for selected S3-style bucket and object workflows.

• ObjectDB: Write as s3-core-v1 when referring to the first profile, and keep exclusions visible.

An explicitly configured object-store read source for query workflows.

• LogDB: POST /v1/query can route reads through this configured store; this is distinct from ObjectDB S3 Core compatibility.

A retained telemetry grouping or bundle boundary used by LogDB ingest, publication, query, or replay docs.

• LogDB: Segment bundle wording belongs to telemetry retention and should not be treated as ObjectDB object-model wording.

A broker queue surface where workers claim and mutate durable delivery state.

• Message Broker: Use with claim, ack, nack, renew, retry, and dead-letter operations in controlled-beta docs.

An ordered broker record sequence used for publish, fetch, replay, and cursor workflows.

• Message Broker: Do not use stream as a generic word for LogDB telemetry selections unless the route or payload names it.

A product-scoped identity or partition boundary used to separate customers, workloads, records, or access policy.

• ObjectDB: Tenant isolation, key handling, and security wording require exact auth-mode and review evidence.
• Message Broker: Tenant limits and authentication mode should be documented with route behavior and controlled-beta status.
• LogDB: Tenant headers are part of ingest and query examples; privacy and retention claims need review.

A Concordia product surface for append/query primitives and retention-oriented time data.

• Concordia: Current TSDB docs should state local and memory-only limits until durable storage, route, and authorization evidence exists.

A telemetry signal that records a request or operation path across spans and can be ingested by LogDB where supported.

• LogDB: Use trace IDs as query examples only within the filters and payload formats named by the reference.

An external identity mode where an upstream component supplies identity through headers the service is configured to trust.

• Message Broker: One configured auth mode for protected routes; do not imply direct identity-provider validation.

A client, route, operation, behavior, or claim area that the docs intentionally mark outside the current supported scope.

• ObjectDB: s3-core-v1 explicitly excludes ACLs, versioning, Object Lock, lifecycle rules, replication configuration, inventory, SelectObjectContent, events, and website hosting.
• Concordia: Gateway quorum, cross-node replication, production authorization, and workflow runtime behavior remain out of current alpha copy.
• LogDB: Metrics/profile ingest, S3 publication, public replay APIs, external sinks, and GA wording remain gated by evidence.

A maturity label for copy that must stay tied to evidence, owner review, or future validation before it can be strengthened.

• ObjectDB: Many product, S3 breadth, local adapter, security, and support claims stay here until evidence records are approved.
• LogDB: Current pages use this label where ingest, query, WAL, S3, BYOC, and replay statements need explicit boundaries.

A way to distinguish revisions of APIs, compatibility profiles, objects, or docs statements.

• ObjectDB: S3 object versioning is excluded from s3-core-v1, while native object versions remain preview-contract direction.
• Cross-product: Use versioned names for profiles, templates, and evidence so later docs can change without rewriting older claims.

Write-ahead log: a local append path used to record accepted data before later publication or recovery behavior.

• LogDB: Direct ingest appends canonical envelopes through a local live WAL before segment publication.