From dc9162f85ddc7162473d62ddf0c27db88352fcb9 Mon Sep 17 00:00:00 2001 From: Meta Vens Date: Tue, 29 Sep 2026 02:12:44 +0200 Subject: [PATCH] Correct the content-plane parity claim for metadata order and bad requests Co-Authored-By: Claude Sonnet 5 --- docs/runtime-parity-scope.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/runtime-parity-scope.md b/docs/runtime-parity-scope.md index 109a287f..6710c2dd 100644 --- a/docs/runtime-parity-scope.md +++ b/docs/runtime-parity-scope.md @@ -74,8 +74,10 @@ to speak CultNet or participate in CultMesh. semantic ones. A single rows-to-bytes path driving both halves in one call remains its own cut (R-AR) and is not part of this claim. - CultMesh content plane (`cultmesh.content_chunk_request.v1` and `.response.v1` - plus the CDN manifest, C#/Rust only): byte parity in both directions, and the - reference's answer to a chunk request, including its failure spellings. + plus the CDN manifest, C#/Rust only): byte parity in both directions (manifest metadata keeps its wire key order and a + duplicate key is refused, as the reference refuses it), and the reference's answer + to a chunk request, including its failure spellings: every bad request is + answered `found: false`, never refused at decode. `packages/cultnet-rs/tests/content.rs` and `tests/GameCult.Mesh.Tests/CultMeshContentVectorTests.cs` judge `contracts/cultmesh/content-vectors.cs-written.json` and