Skip to main content
Source baselineNereuscommit c820391dc1de·verified 2026-08-07·authority reader-facing-summary

Glossary

Use this page for lookup; the concept and data-path pages provide the surrounding contracts.

TermMeaningDo not confuse with
StreamProtocol-neutral, logically continuous offset sequencePulsar ledger, Kafka segment, Object key
OffsetLogical record position in a streamBK entry ID or Object byte position
EntryIndivisible payload that may cover one or more logical recordsAlways one logical offset
Ranged entryEntry with recordCount > 1 covering a half-open offset rangeMultiple independent Objects
Half-open range[start,end), including start and excluding endClosed [start,end] range
ProjectionMapping from an upper protocol coordinate to stream identity/offsetData replication or a second log
Virtual ledger IDStable Pulsar-compatible ledger coordinatePhysical BookKeeper ledger ID
Primary WALFirst durable bytes required by a profileLogical commit authority by itself
Object WALImmutable Object Store representation of primary WAL slicesA higher generation automatically visible
Stream headAuthority summarizing committed end, commit anchor, trim, and sessionAll message indexes
Commit intentImmutable description written before head CASIndependently visible message
Reachable commitCommit reachable from the head’s last commit IDAny intent present in Oxia
CASConditional update that applies only when version/preconditions matchUnconditional overwrite
Linearization pointUnique instant an operation becomes logically committedAny provider success response
Append sessionStream-scoped epoch/token writer identityBroker ownership watch alone
FencingNew epoch/token invalidating an old writerMerely disconnecting a socket
Append authorityExternal monotonic Leader/owner term bound to a sessionKafka type inside L0
ReadTargetExact physical read description for one logical rangeCache handle or Object listing
Offset indexDerived mapping from offset range to ReadTargetAppend truth
Generation 0Append-time primary ReadTarget representationThe first logical message
Higher generationReplacement physical representation for one stream/view/rangeA new logical message
Read viewSemantic read domain such as COMMITTED or TOPIC_COMPACTEDStorage profile
MaterializationCopy/re-encode of committed source into an immutable output and publicationA new append
CompactionMaterialization that may be lossless or key-based/semanticAlways valid for ordinary reads
PREPARED generationOutput and index prepared but not visibleReader-selectable target
COMMITTED generationPublication CAS succeeded; eligible reader candidateAppend head commit in all contexts
QuarantineIsolation of damaged or identity-mismatched formal candidateLogical rollback
Reader pin/leaseCross-process bounded read protectionJVM reference count
ProtectionDurable task/append/cursor reference to a physical resourcePhysical replica itself
CheckpointImmutable recovery state at a stable boundaryAuthority that may lead the head
TrimMoves the earliest logically readable offsetImmediate physical deletion
RetentionPolicy deciding which logical ranges may expireConsumer ack synonym
Source retirementOld source no longer serves read/recovery dutiesObject necessarily deleted
GCAggregates references before reclaiming Object/ledgerDelete after LIST
OrphanBytes/intent not referenced by authoritative stateA damaged formal generation
Fail closedRefuse when safety cannot be provenGuessing a fallback path
Cursor rootSingle-key CAS authority for Pulsar durable subscription stateLocal read position
markDeleteOffsetFirst Entry offset not cumulatively acknowledgedPulsar’s last returned Position itself
Cursor generationSubscription delete/recreate lifecycle numberAck reset epoch
ackStateEpochSame-cursor-generation reset/clear replacement numberStream commitVersion
KRaftKafka control plane for Topic/partition/Leader metadataNereus stream metadata
LEOKafka next record offsetPhysical file length
HWKafka consumer-visible replicated boundaryNereus generation number
LSOKafka READ_COMMITTED transaction-stable boundaryStream trim offset
BindingDurable Topic/partition lifecycle to storage class or stream mappingA message index
ActivationProof that a cluster can use a durable protocol consistentlyA data commit

Source anchors