From 1ae82e01aea6346d7c7c38431389bb2e9c78cf3d Mon Sep 17 00:00:00 2001 From: tegwick Date: Sun, 21 Jun 2026 21:46:43 +0200 Subject: [PATCH] feat(STATE-WP-0064): enable consistency sweep for parallel week Activate the Railiance01 schedule alongside the local timer during T03. --- .../state-hub-consistency-sweep.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/activity-definitions/state-hub-consistency-sweep.md b/activity-definitions/state-hub-consistency-sweep.md index f508cf1..55ce623 100644 --- a/activity-definitions/state-hub-consistency-sweep.md +++ b/activity-definitions/state-hub-consistency-sweep.md @@ -3,10 +3,10 @@ id: "7c4e9a12-8f3b-4d5e-9c6a-1b2d3e4f5a6b" name: "State Hub Consistency Sweep" type: activity-definition version: "1.0" -enabled: false +enabled: true owner: custodian governance: custodian -status: proposed +status: active created: "2026-06-21" trigger: type: cron @@ -19,6 +19,7 @@ context_sources: required: true params: max_seconds: 300 + source: activity-core bind_to: context.consistency_sweep_remote_all --- @@ -37,14 +38,14 @@ cron schedule and ActivityRun audit trail. ## Runner Status -This definition stays `enabled: false` until a successful manual canary -against Railiance01 Temporal. +`enabled: true` during `STATE-WP-0064-T03` parallel week (started +2026-06-21) alongside the local `custodian-sync.timer`. Both invoke the +same State Hub API; the process lock makes overlapping runs idempotent. Cutover boundary: -- The local `custodian-sync.timer` remains the interim primary runner - during the parallel week in `STATE-WP-0064-T03`. -- After cutover, disable the local timer and enable this definition as +- **Parallel week (T03):** cluster schedule and local timer both active. +- **After T04 cutover:** disable the local timer; this definition remains the sole primary runner. - Do not treat the local timer and this activity-core schedule as two independent primary runners after cutover.