coulomb/activity-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: claim loop is primary for FI; dual-clock timer retired
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Record 2026-08-05 cutover after per-fire ops_run keys were fixed and
the FI host timer disabled on railiance01.
This commit is contained in:
tegwick 2026-08-05 15:33:21 +02:00
parent 21dc228cb1
commit 3b2528ab84
2 changed files with 6 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

3
docs/deploy-ops-run-queue-railiance.md
View file

@ -18,7 +18,8 @@ defaults `OPS_RUN_QUEUE_ENABLED=true`; railiance still needs image + migration
2. Expose claim API on **actcore-api** (image that includes WP-0026). 2. Expose claim API on **actcore-api** (image that includes WP-0026).
3. Worker **emit_tasks** dual-writes open `ops_run` rows. 3. Worker **emit_tasks** dual-writes open `ops_run` rows.
4. Smoke: FI (or Binky) one-shot → `GET /ops-runs?state=open` shows a row. 4. Smoke: FI (or Binky) one-shot → `GET /ops-runs?state=open` shows a row.
5. **Do not** remove host systemd timers until REIN-A-0002 claim loop is proven. 5. Host systemd timers are break-glass only once claim loop is proven
(FI dual-clock timer disabled 2026-08-05 after per-fire ops_run keys).
## Non-goals ## Non-goals

7
docs/recurring-automations-playbook.md
View file

@ -47,9 +47,10 @@ issue-core projection — never as the default ops claim queue.
**Anti-pattern:** workstation `crontab` that “does the daily brief” while **Anti-pattern:** workstation `crontab` that “does the daily brief” while
activity-core also schedules it — dual cadence and forgotten design. activity-core also schedules it — dual cadence and forgotten design.
**Correct interim (Binky / FI):** activity-core schedule is authority for *when **Primary (Binky / FI):** activity-core schedule → `ops_run` → rein-aharness
due*; railiance user-systemd timer invokes rein-aharness a few minutes later as **claim loop** on railiance01. Host user-systemd timers are **break-glass only**
executor. Document both; never pretend the host timer *is* the scheduler. (not cadence authority). FI dual-clock timer was disabled 2026-08-05 after the
ops_run per-fire idempotency fix landed; re-enable only if claim loop is down.
--- ---