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.

Source scope: documented source scope

Think of the broker as private 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 private 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 support details, 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 limits and compatibility guidance.

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 private 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.

Source scope: documented source scope

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.

Source scope: documented source scope