Reading guide
Read Nereus Delay in dependency order. The site summarizes the V1 design; exact numbers, bytes, fields, and codes remain in the Protocol Registry.
- Why Nereus Delay? establishes goals, non-goals, and the not-before delivery boundary.
- Architecture identifies the Command Topic, Shard Runtime, RocksDB, Scheduler, adapters, Oxia, and Object Store.
- Delivery time and action time fixes the time vocabulary and fail-closed clock behavior.
- Commands, messages, and receipts separates prepared bytes, queued outcomes, applied results, and destination evidence.
- Schedule flow follows source-ordered application from preparation to durable message state.
- Destination Lane isolation explains fairness, retry, capability, and target-failure isolation.
- Checkpoints and recovery explains Recovery Set, Recovery Floor, replay, and activation.
- Current project status distinguishes local implementation evidence from release blockers.
Authority reminder
When a summary and a normative source disagree, update the summary. Do not choose the more convenient interpretation. See Authority order.