From 7c15c0ea48981867fc1683d9b7576f6444c256da Mon Sep 17 00:00:00 2001 From: tegwick Date: Sat, 17 Oct 2026 02:15:58 +0200 Subject: [PATCH] Retain Cluster publication with failed historical row preservation Assistant: codex Assistant-Model: gpt-6.1-sol Assistant-Session: 01a1468b-63fa-7710-85dc-8f2e16b3ebfa --- ...MGR-WP-0019-historical-source-admission.md | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/workplans/RMGR-WP-0019-historical-source-admission.md b/workplans/RMGR-WP-0019-historical-source-admission.md index 5bc6b7d..98cc2d2 100644 --- a/workplans/RMGR-WP-0019-historical-source-admission.md +++ b/workplans/RMGR-WP-0019-historical-source-admission.md @@ -209,6 +209,34 @@ generated indexes. Preserve all three archived files and all 18 existing parent/task rows. Return actual receiving/publication receipts to STATE-WP-0095-T07. Do not infer TLS recovery, credential custody or native acceptance from sync. +Cluster publication returned, preservation acceptance failed, 2026-10-17: +normal owner publication at c562d7134c38679952a8ffd17a8a893a900aef0d +is applied on primary/railiance01 with expected and derived commits equal. +Read-only source/remote/Hub verification confirms WP0018's five task bindings +and three internal dependency edges. These publication results do not close T06. +The full-row guard after the required legacy deep consistency pass failed: +all three historical parent full-row hashes changed; all 15 historical task +full-row hashes remain equal. The entire pipeline therefore has no successful +18-row preservation acceptance. + +Custodian receipts under docs/changes/netkingdom-target-2026-10-17: +railiance-cluster-projection.json and cluster-publication-readback.json retain +the applied publication and bounded readback; receiver-rollout-r4/ +pre-publication-full-row-hashes.json retains the passing pre-publication guard; +receiver-rollout-r4/post-publication-full-row-hashes-FAILED.json retains the +failed native comparison. Exact receipt digests are retained in +registrar-t06-preservation-failure-r1/manifest.json. Coordinator and recovery +source review identified the unguarded PUT /workplans/index/bindings path +writing backing_synced_at and ORM updated_at, outside the native forge +projection's preservation guard. Full baseline rows were not retained, only +full-row hashes; no guessed database restoration is authorized or claimed. + +The original rollout's pre-Cluster preservation/refusal verification remains +valid for that earlier stage, and T05 remains done. T06 stays wait pending +the reviewed exact-frozen binding guard, regression coverage and a verified +recovery/preservation disposition. No source or native gate is promoted by the +successful publication alone; no TLS or credential-custody acceptance follows. + ## Receiver-first registrar source follow-through, 2026-10-17