From 630da369d046f3bfb3ea56780784d2ce07812c7e Mon Sep 17 00:00:00 2001 From: 732642856 <732642856@qq.com> Date: Fri, 17 Jul 2026 17:11:09 +0800 Subject: [PATCH] docs: calibrate VedAstro replay conflict --- .../vedastro_live_replay_conflict_2026_07_17.md | 16 +++++++++++----- ...ommercial_external_validation_release.v1.json | 2 +- 2 files changed, 12 insertions(+), 6 deletions(-) diff --git a/docs/research/vedastro_live_replay_conflict_2026_07_17.md b/docs/research/vedastro_live_replay_conflict_2026_07_17.md index 79cbde1e..3ce11d1c 100644 --- a/docs/research/vedastro_live_replay_conflict_2026_07_17.md +++ b/docs/research/vedastro_live_replay_conflict_2026_07_17.md @@ -16,6 +16,8 @@ claims, production tuning, or a three-engine closure claim. - Fresh local raw artifact: `scratch/local/vedastro_adapter/official_full_snapshot-1ff276e8fdee-ab172556e932.json` - Fresh official raw response SHA-256: `ab172556e9327f55ce5a14d2a2da91c7736690c5181ba59627d0acbf0d1b0ef8` - Runner output: `scratch/local/three_engine_parity_vedastro_live/three_engine_parity_replay.json` +- Independent repeat raw response SHA-256: `64c784ddfce22b83f2ba4a666983c1ca3a01f54c6f4d49dd1070167dbf850d54` +- Repeat runner output: `scratch/local/three_engine_parity_vedastro_retry/three_engine_parity_replay.json` ## Fresh Result @@ -29,14 +31,18 @@ claims, production tuning, or a three-engine closure claim. Mismatched fields: `Sun.longitude`, `Moon.longitude`, `Mars.longitude`, `Mercury.longitude`, `Venus.longitude`. +The independent repeat used the same visible request body and produced the same +five normalized mismatch values. The raw response hash differs, but the +normalized external discrepancy is stable for this endpoint replay. + ## Conflict Arbitration The prior commercial manifest referenced a research-local scratch artifact with -the same visible birth-time request but a different official response hash. The -fresh official response is authoritative for this run; its mismatch must remain -visible until the VedAstro endpoint/version/method contract explains the drift. -Do not replace the old packet with a pass result or tune local calculations to -match either response. +the same visible birth-time request but a different official response hash. Two +fresh official responses converge on the same five normalized discrepancies. +The mismatch must remain visible until the VedAstro endpoint/version/method +contract explains the drift. Do not replace the old packet with a pass result +or tune local calculations to match either response. ## Required Next Evidence diff --git a/references/evidence_manifests/commercial_external_validation_release.v1.json b/references/evidence_manifests/commercial_external_validation_release.v1.json index b7121907..256ff111 100644 --- a/references/evidence_manifests/commercial_external_validation_release.v1.json +++ b/references/evidence_manifests/commercial_external_validation_release.v1.json @@ -79,7 +79,7 @@ { "id": "vedastro_live_replay_conflict_2026_07_17", "path": "docs/research/vedastro_live_replay_conflict_2026_07_17.md", - "sha256": "758d21d917f2b5e423afacc49e91653385e3329827ddb5ea7acaa43281e5e0c7", + "sha256": "8697727742ebe19331b8de3ed3f6202af228c11944902c90e83f950fa8d4c652", "scope": "fresh official VedAstro same-chart replay conflict boundary" } ]