Skip to main content
Source baselineNereus Delaycommit 9281890f4277·verified 2026-08-07·authority reader-facing-summary

Glossary

The product repository's CONTEXT.md is the terminology authority. This page is a navigable reader-facing subset and does not add protocol values or new semantics.

TermV1 meaning
deliverAtEarliest instant at which a destination consumer may become eligible to receive a delayed message.
actionAtEarliest instant at which Nereus Delay may start the destination action needed to satisfy deliverAt.
Trusted UTC intervalBounded [earliestUtcNow, latestUtcNow] estimate used for fail-closed timing decisions.
Managed DeliveryDefault mode with server-side Command, query, cancel, reschedule, quota, audit, and recovery boundaries.
AUTO_FASTExplicit SDK permission to choose a prepared managed branch or a certified native Pulsar branch before I/O.
CommandImmutable request to Schedule, Cancel, Reschedule, or perform another registered operation.
Source PositionIngress Broker position that orders Client Commands and System Mutations within one route partition.
Queued CommandCommand durably accepted by the ingress Broker but not yet authoritatively applied by its Delay Shard.
Applied CommandCommand whose authoritative outcome is durably recorded by the Delay Shard.
Delayed MessageManaged logical message created only after a Schedule Command is successfully applied.
Destination LaneBounded group sharing destination, tenancy, and Ordering Domain characteristics for fairness, retry, and isolation.
Recovery SetBounded ordered set of published checkpoints from which recovery may choose.
Recovery FloorOldest checkpoint still permitted by the Recovery Set; resources needed by permitted checkpoints remain protected.
Uncertain EnqueueOutcome where the client cannot prove whether the ingress Broker persisted the prepared command.

Avoid these substitutions

  • Do not call a queued command a scheduled message.
  • Do not call deliverAt publish time or exact consumer receive time.
  • Do not call a timeout definitely-not-queued.
  • Do not call a local uploaded checkpoint authoritative until it is published in the catalog.
  • Do not treat a Lane as an ownership or recovery unit.