coulomb/railiance-platform
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
railiance-platform/workplans/ADHOC-2026-10-19.md
repo-manager 4583b22fd6
All checks were successful
CCR intake gate / gate (push) Successful in 1m10s
Details
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
repo.work.assign_missing_identifiers 
source: repo-manager
reason: deterministic projection registration

Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a17f16-d99c-7ea3-95f0-8212897fba6b
2026-10-27 22:22:58 +01:00

2.4 KiB
Raw Blame History

id type title domain repo status flavor owner topic_slug created updated state_hub_workstream_id
RPF-WP-ADHOC-2026-10-19 workplan Reconcile railiance01 child Application pins with live and guard root syncs financials railiance-platform finished implementation claude-code railiance 2026-10-19 2026-10-20 3a9ae079-aac3-5967-b1f4-f6ec9b602d92

Align the activity-core pin with the founder-approved live release

id: RPF-WP-ADHOC-2026-10-19-T01
status: done
priority: high
state_hub_task_id: "10e13445-c9de-5155-a3cc-37b75229de67"

The activity-core releases on 2026-10-04 (a86a143) and 2026-10-19 (8884b12) patched the live child Application without committing its pin here. Git still pinned ce9a8f8 (2026-09-28), and railiance-apps-root was OutOfSync, so the next hand root sync would have rolled activity-core back by two releases. The pin is now 8884b123c54877bec44fb8355792244a8353a8ff, which equals live. This is a Git-only change: live state is already at this revision, and no sync was run.

Add a read-only pin drift check before root syncs

id: RPF-WP-ADHOC-2026-10-19-T02
status: done
priority: medium
state_hub_task_id: "80828bb6-1423-5e89-8062-6a8ac963c511"

make argocd-pin-drift (scripts/argocd_child_pin_drift.py) compares every child Application's targetRevision in argocd/railiance01/applications with live, and exits 1 on drift. The applications README now requires it before any hand sync of the root. activity-core docs/gitops-release.md now requires releases to commit their pin here and pass this check.

informed-decision pin drift (owner confirmation)

id: RPF-WP-ADHOC-2026-10-19-T03
status: done
priority: medium
state_hub_task_id: "07f43738-eef0-5549-9150-f1020a1ce7e4"

Live informed-decision runs 312ab97e876e… ("Prepare owner-reviewed zlib-only native release decision", 2026-10-11). Git pins 9207a513 (2026-10-05). Live is a descendant of the pin, so this is likely the same skipped-pin pattern. It is not changed here, because this session cannot verify that 312ab97 was an admitted release. Once the informed-decision owner confirms it, commit that pin. Until then, do not hand sync railiance-apps-root, because the sync would revert informed-decision.

2026-10-20: the founder confirmed that 312ab97e was an approved release. The pin is now 312ab97e876e17341bf16f9e95397e14c2ac2720, which equals live. This is a Git-only change, and no sync was run.