Authority order
When a website summary conflicts with a product source, the summary is wrong and must be corrected. The V1 repository defines this order:
docs/Nereus Delay V1 设计.md— V1 semantics, lifecycle, recovery, resource, security, and acceptance baseline.docs/V1-PROTOCOL-REGISTRY.md— exact wire fields, enum values, canonical bytes, key tags, stable codes, and union/presence rules.docs/adr/— accepted architecture decisions and the reasons for them.docs/IMPLEMENTATION-STATUS.md— current code and test evidence plus remaining release blockers. It cannot relax the design.docs/V1-DESIGN-AUDIT.md— cross-document drift and release-evidence view. It is not a new protocol authority.CONTEXT.md— fixed terminology and forbidden substitutions. It does not add protocol semantics.
Website policy
The website keeps a fixed source commit, verification date, and authority label on every Delay page. It summarizes reader-facing concepts and links to the exact repository material for normative details. A future full Registry mirror would need automated content and hash verification; manual copying is not a second source of truth.
Status versus semantics
An implementation-status row can say that a codec or local projection exists; it cannot turn a missing production Broker adapter, Oxia authority, or release-evidence artifact into a V1 guarantee. The public state remains V1 in development until the release gates are satisfied.