Protocol Registry guide
The V1 Protocol Registry is the normative numeric and byte-level contract for Nereus Delay V1. It applies only to V1-FROZEN-2026-08-01; unlisted enum values, tags, fields, and stable codes are unknown.
What the Registry fixes
NDL1Shard Log framing, version, kind, length, and CRC32C boundary.- Fixed-width integer and identity encodings.
- Canonical Protobuf field order, presence, enum validation, and round-trip bytes.
- Command and System Mutation envelopes, body hashes, and signature preimages.
- RocksDB Column Family key tags, widths, ordering, and checkpoint JSON.
- Stable result codes, retryability, uncertainty branches, and conformance vectors.
How to read a website summary
The product pages and concept pages explain why a boundary exists and how it relates to the end-to-end flow. They intentionally do not reproduce the complete Registry tables. For implementation, compatibility, or conformance work, open the pinned Registry commit and verify the exact field/value rule there.
Conflict rule
The Registry does not replace the design's business context, and prose does not authorize an unregistered wire extension. If the design, Registry, and accepted ADRs conflict, the V1 release gate fails until all affected artifacts are revised together.