Product mental models.

Begin with the scoped S3 Core bucket/object path, then treat native object version and manifest language as preview-contract direction unless a reference page names the behavior.

Bucket

Meaning: An S3-shaped namespace for current bucket and object workflows.

Use now: Use for scoped s3-core-v1 bucket discovery, create/list behavior, policy subset copy, CORS, tagging, location, multipart, and object routes.

Boundary: Does not imply IAM parity, lifecycle, replication configuration, inventory, Object Lock, notifications, SelectObjectContent, ACLs, or website hosting.

Object

Meaning: A payload addressed through a bucket/key workflow, with metadata, tags, range reads, multipart state, and delegated upload shapes where listed.

Use now: Use for live S3 Core object CRUD, listing, metadata/tagging, checksum, ETag, range, multipart, and local request-limit language.

Boundary: Does not imply every S3 operation or customer durability, recovery, performance, scale, or support claim.

Version

Meaning: A native object-model concept and operation-adjacent identifier that must stay distinct from S3 bucket versioning support.

Use now: Use when explaining why native object-platform direction can talk about object history separately from the active s3-core-v1 compatibility profile.

Boundary: S3 versioning is excluded from s3-core-v1; do not publish customer-facing version-management guidance until public references and evidence exist.

Manifest

Meaning: A preview native object-model word for describing object state and related platform metadata beyond compatibility-facing S3 fields.

Use now: Use as planning vocabulary for native object model, placement, policy, and event-oriented discussions.

Boundary: Does not imply a public native manifest API, hosted control plane, automatic event delivery, or reviewed placement outcome.

Evidence: DOCS-029, DOCS-030, DOCS-038, ODB-EVID-009, ODB-EVID-010

Think of the broker as controlled-beta stream and queue workflows over one route surface, with replay and cursor concepts kept separate from external protocol compatibility claims.

Stream

Meaning: A named broker surface that holds records for publish, fetch, replay, cursor, group, and queue workflows.

Use now: Use for controlled-beta stream create, describe, list, publish, fetch, storage inspection, and retention wording.

Boundary: Does not imply every external streaming pattern, Kafka listener support, or production topology outcome.

Record

Meaning: A published message with identifiers, payload, optional key, event time, ingest time, headers, offsets, and route diagnostics.

Use now: Use for publish acknowledgements, fetch pages, replay pages, queue deliveries, audit evidence, and replication-status boundaries.

Boundary: Does not imply unlimited payloads, exactly-once cross-site behavior, or stable ordering outside the named route behavior.

Replay

Meaning: A controlled read of stream records from an offset, time selector, tail window, or SDK subscription start position.

Use now: Use for fetch/replay workflows, replay-consumer inspection, local CLI replay, and SDK subscribe-replay examples.

Boundary: Does not imply LogDB replay APIs, external sink delivery, Kafka consumer semantics, or selected pilot readiness.

Cursor

Meaning: A saved read position for a consumer group or named processing path.

Use now: Use for commit, rewind, cursor inspection, group lag, and reader coordination over broker stream records.

Boundary: Do not confuse broker cursors with LogDB query pagination or promise global consumer-state durability beyond the current route evidence.

Queue

Meaning: A shared-work model built from claim, lease, ack, nack, renew, retry, and dead-letter operations over stream records.

Use now: Use for controlled-beta queue worker flows, delivery mutation, retry, and dead-letter handling.

Boundary: Does not imply every queue pattern, remote CLI write support, or cross-site availability guarantee.

Evidence: DOCS-031, DOCS-032, DOCS-040, SMB-EVID-010, SMB-EVID-011

Read Concordia as an uneven product family: Cache, Gateway, Storage, Time Series, active compatibility, and Edge Workflows do not all carry the same maturity.

Cache

Meaning: A local key/value surface for health, protected operations, count checks, placement diagnostics, and optional node-local persistence.

Use now: Use for alpha local smoke workflows and loopback HTTP routes that require the documented local bearer token for protected routes.

Boundary: Does not imply production identity, shared storage, restart recovery beyond named evidence, cross-node routing, or scale support.

Placement

Meaning: A diagnostic view of local routing or fixture-backed metadata used to reason about where cache work would be directed.

Use now: Use for Cache placement diagnostics, Gateway placement cache inspection, and fixture-backed Gateway alpha evidence.

Boundary: Does not prove external metadata watches, owner forwarding, quorum commit, visible reads, or distributed routing.

Gateway

Meaning: A local alpha diagnostic and protected write surface that is fail-closed until explicit write-mode, metadata, owner transport, retry, and quota gates pass.

Use now: Use for readiness, blockers, placement diagnostics, and accepted diagnostic output in the alpha tutorial.

Boundary: Does not imply production JWT enforcement, TCP owner forwarding, cross-node replication, or customer-facing write guarantees.

Storage

Meaning: A validation-bound startup and protocol-boundary surface, not a general storage server in current public docs.

Use now: Use for dry-run, require-ready, listener, frame, owner, follower, quorum, and boundary-flag evidence commands.

Boundary: Do not present validation flags as broad Storage serving, shared durable storage, or general quorum behavior.

Time Series

Meaning: A local HTTP shell for append, recent query, retention, and routing-diagnostic primitives.

Use now: Use for alpha TSDB local model examples and the Gateway tutorial when samples and recent queries are the workflow.

Boundary: Does not imply durable storage, replicated storage, production authorization, or projection freshness.

Evidence: DOCS-035, DOCS-041, DOCS-042, CONC-EVID-012, CONC-EVID-013

Read LogDB as an OTLP-first logs/traces retention and query system, with segment storage and S3 query-read language separated from future S3 publication and BYOC claims.

Envelope

Meaning: A canonical telemetry record shape produced by endpoint JSON helpers or OTLP compatibility ingest, with deterministic record IDs where documented.

Use now: Use for JSON endpoint payloads, OTLP JSON compatibility batches, tenant admission, record IDs, and recent readback wording.

Boundary: Does not imply metrics/profile ingest, dashboarding, SIEM replacement, or arbitrary telemetry transformation.

WAL

Meaning: The local live write-ahead log path used before segment publication and during startup replay evidence.

Use now: Use for local publication ordering, startup replay, replicated-local proof slices, and process-fault evidence only when the source is named.

Boundary: Does not imply final distributed WAL, network replication, node-level failure coverage, or durability commitments.

Segment

Meaning: A manifest-controlled retained-record bundle with Parquet data, statistics, exact identifier indexes, retention metadata, and encryption metadata fields.

Use now: Use for local segment publication, segment-bundle v1 storage, retained query, and configured S3 query-read discussions.

Boundary: Configured S3 query-read changes the query read path only; it is not S3 publication or BYOC production readiness.

Query

Meaning: The authenticated retained-record search path over local or configured S3 segment bundles.

Use now: Use for POST /v1/query by dataset, exact record ID, exact trace ID, source time, ingested time, pagination, and deadline controls.

Boundary: Does not imply distributed query workers, cost controls, long-retention outcomes, public replay APIs, external sinks, or support commitments.

Evidence: DOCS-033, DOCS-034, DOCS-039, LDB-EVID-010, LDB-EVID-011