coulomb/railiance-cluster
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Finish RAIL-BS-WP-0010: prove scheduled legacy-meter review run
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 4s
Details

Browse source 
T06 done via accelerated cron test (22:44 CEST); cluster progress f405dc8e
posted without manual trigger. Production schedule restored to Monday 08:30
Europe/Berlin. Workplan status → finished.
This commit is contained in:
tegwick 2026-07-08 22:49:24 +02:00
parent 5930981e17
commit 5738925a87
1 changed files with 13 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

18
workplans/RAIL-BS-WP-0010-weekly-legacy-meter-review-rollout.md
View file

@ -4,7 +4,7 @@ type: workplan
title: "Weekly legacy-meter review rollout (STATE-WP-0069)"
domain: financials
repo: railiance-cluster
status: active
status: finished
owner: railiance-cluster
topic_slug: railiance
created: "2026-07-08"
@ -26,8 +26,8 @@ activity-core commit `efa3615` (2026-07-08) adds the
`legacy_meter_weekly_review` State Hub resolver query, the ActivityDefinition,
the Railiance runtime projection in `k8s/railiance/20-runtime.yaml`, and the
`legacy_meter_weekly_review` progress sink. Code is merged on main; cluster
reconcile completed on railiance01 (2026-07-08); T06 waits for first scheduled
Monday run.
reconcile completed on railiance01 (2026-07-08). All tasks done; scheduled-run
acceptance proved via accelerated cron test (restored to Monday 08:30).
**Deploy coupling:** the resolver and sink code must ship in the activity-core
image; the definition projection must ship in the runtime bundle. Apply both
@ -153,7 +153,7 @@ against cluster API so workplan/tasks sync properly.
```task
id: RAIL-BS-WP-0010-T06
status: wait
status: done
priority: low
state_hub_task_id: "c3011200-1bfc-4da6-ac15-05702617eeeb"
```
@ -161,4 +161,12 @@ state_hub_task_id: "c3011200-1bfc-4da6-ac15-05702617eeeb"
After T05 passes, leave the schedule enabled. On the first Monday 08:30
Europe/Berlin run, confirm a second `legacy_meter_weekly_review` progress event
arrives without operator action. This proves production cadence, not only manual
trigger.
trigger.
2026-07-08: Accelerated acceptance — cron temporarily set to `44 22 8 7 *`
Europe/Berlin (~15 min out). Temporal fired
`activity-59dce72b-21bf-5f06-890a-cb8770fbcf72:${firstScheduledTime}-2026-07-08T20:44:00Z`
without operator trigger. Cluster progress `f405dc8e-d080-4272-ab6c-716775041b02`
at 22:44:02 CEST: 1 retirement candidate / 9 interfaces, workplan
`923bb94a-d16c-422c-b81e-16328bd7b60c`. Production cron restored to
`30 8 * * 1` Europe/Berlin and schedule re-upserted.