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

Complete release dispatch groundwork and mark remaining work blocked
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
Build and Publish Container Image / build-and-push (push) Successful in 1m32s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e429-436c-73f1-9144-bac4336c06e8
This commit is contained in:
tegwick 2026-09-27 20:51:56 +02:00
parent 9ebe56bb4f
commit 7b55261bd7
9 changed files with 385 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

32
workplans/ACTIVITY-WP-0041-gitops-adoption.md
View file

@ -4,7 +4,7 @@ type: workplan
title: "Remove recurring deployment exceptions through governed GitOps adoption"
domain: infotech
repo: activity-core
status: active
status: blocked
owner: codex
topic_slug: activity-core
created: "2026-09-27"
@ -44,7 +44,7 @@ server-dry-run the proposed managed set; no unintended spec change or pruning.
```task
id: ACTIVITY-WP-0041-T02
status: progress
status: wait
priority: high
state_hub_task_id: "af09865d-8cc9-5571-9c34-20ae679a1e4e"
```
@ -67,7 +67,7 @@ one-time governance decision.
```task
id: ACTIVITY-WP-0041-T03
status: progress
status: wait
priority: high
state_hub_task_id: "8e2b4ed9-d455-5367-85d9-8e4222ce75f3"
```
@ -191,3 +191,29 @@ T03 remains progress for admitted identity/custody, authenticated isolated Kuber
verification, real build/review/retention issuers, production invariant probes,
Temporal observer/dispatcher registration and evidence sinks. The implemented
observer cannot retroactively assert the earlier soak interval. See docs/release-broker.md.
## Loose-end implementation and blockers — 2026-09-27
Completed another repo-side portion of T03: `release_dispatch.py` supplies a
Temporal workflow and explicitly constructed dedicated worker for resuming an
already-admitted ledger release. Requests carry only its ID; source, transport,
keys and sinks come from trusted worker configuration. Durable transition audit
acknowledgements survive restart, repeat the same event ID after a lost response,
and export only normalized facts. Nonterminal audit outages do not prevent
rollback; terminal completion waits for audit delivery. Adapter errors are
sanitized before reaching Temporal history. The ordinary worker remains unchanged.
Tests cover restart, lost publication and audit responses, rollback, unknown IDs,
identity disablement and Temporal sandbox construction. The image CI test target
includes the new suite. This is isolated implementation evidence, not authenticated
Kubernetes proof or production activation.
T02 and T03 are now wait and the workplan blocked. T02 cannot close before the
September 28 16:06:22 Berlin observation eligibility and healthy owner evidence
(RPF-WP-0048-T02). T03 still requires admitted identity/custody, real independent
receipt issuers, bounded production report/schedule probes, authenticated isolated
transport/denial/rollback proof, and deployment/registration of the observer,
dispatcher and audit sink. Local code cannot supply those trust inputs. The new
worker factory neither enables a schedule nor grants an identity; deployment and
continuous health observation must be established through the existing owner lane.
No new workplan/task, production mutation or authority expansion was introduced.