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

RAIL-BS-WP-0011: recheck notes and T04 revisit after 16:00 UTC
Some checks are pending
CI Smoke / host-smoke (push) Waiting to run
Details
CI Smoke / container-smoke (push) Waiting to run
Details

Browse source 
Record Temporal schedule upsert from recheck, reopen workplan to active,
and document T04 cadence proof criteria for the 16:00 UTC production tick.
This commit is contained in:
tegwick 2026-07-09 12:00:04 +02:00
parent a0be3b53ff
commit 7d3de31f41
1 changed files with 21 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

25
workplans/RAIL-BS-WP-0011-legacy-meter-8h-capture-image-reconcile.md
View file

@ -4,7 +4,7 @@ type: workplan
title: "Legacy-meter 8h capture image reconcile (STATE-WP-0073)" title: "Legacy-meter 8h capture image reconcile (STATE-WP-0073)"
domain: financials domain: financials
repo: railiance-cluster repo: railiance-cluster
status: finished status: active
owner: railiance-cluster owner: railiance-cluster
topic_slug: railiance topic_slug: railiance
created: "2026-07-09" created: "2026-07-09"
@ -83,6 +83,12 @@ relay logged `GET /legacy-meter/weekly-review?hours=8` 200 OK. Definition
`a0fae182-52e9-5990-9fa6-6fea12a14753` enabled in DB; ConfigMap carries `a0fae182-52e9-5990-9fa6-6fea12a14753` enabled in DB; ConfigMap carries
`hours: 8` and cron `0 */8 * * *` UTC. `hours: 8` and cron `0 */8 * * *` UTC.
Recheck (same day): image digest `sha256:7f8e56a3…` still live. Temporal
schedule `activity-schedule-a0fae182-52e9-5990-9fa6-6fea12a14753` was missing
from the 13-schedule inventory (bulk `sync_schedules` blocked by unrelated
`ScheduleAlreadyRunningError`). Targeted `upsert_schedule` created it: every 8h
at `:00` UTC, `paused=false`, schedule count 13 → 14.
## Manual trigger acceptance smoke ## Manual trigger acceptance smoke
```task ```task
@ -121,6 +127,17 @@ After T03 passes, leave the schedule enabled. On the next `0 */8 * * *` UTC
tick, confirm a second `legacy_meter_8h_capture` progress event arrives without tick, confirm a second `legacy_meter_8h_capture` progress event arrives without
operator action. Proves production cadence, not only manual trigger. operator action. Proves production cadence, not only manual trigger.
Schedule left enabled; next production tick at 16:00 UTC 2026-07-09. Manual **Revisit after 16:00 UTC 2026-07-09.** Schedule enabled and registered in
acceptance (T03) closes suggestion `8b3301d6`; cadence proof deferred to Temporal (see T02 recheck). Poll cluster State Hub for a third
scheduled watch. `legacy_meter_8h_capture` progress event with `scheduled_for` at the 16:00 UTC
tick and no manual `trigger_key` in the workflow id.
Evidence so far (not sufficient to close T04):
- `92893da2` — manual acceptance (T03), `scheduled_for` 09:47:49Z
- `47d461b9` — catchup run, `scheduled_for` 09:42:30Z (predates schedule
registration; not a clean cadence proof)
**Done when:** unattended 16:00 UTC fire posts progress with `window_label: 8h`
linked to workplan `44e2e123-9934-4b5e-8b50-1bac548c5b70`, then mark T04 done
and workplan `finished`.