coulomb/frontend-patterns
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Record activity-core GitOps delivery and outstanding release gates

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e241-8285-7a63-8c0c-51c9cb824dc3
This commit is contained in:
tegwick 2026-09-27 15:49:58 +02:00
parent 10f0131f67
commit a21a614eae
3 changed files with 200 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

32
docs/ActivityCoreLoop.md
View file

@ -52,19 +52,27 @@ October 1 at 09:00, respectively, in Europe/Berlin. All verified reports correct
say `no_consumers`, zero model calls and automatic edits disabled. Reports are
stored in State Hub under the frontend-patterns topic and the event types above.
The worker overlay changes only the resolver module and registration. API/router
images remain pinned. Rollback restores `activity-core:fi-publication-20260914`
and disables these three source definitions and their ConfigMap projections,
then syncs definitions and schedules after projected files have refreshed.
The reporting binaries are now deployed through Git and ArgoCD using immutable
registry digests. The user authorized this adoption separately on September 27
(decision `78a4b859-dd00-4623-b95b-121b0e1c915d`). Nine runtime resources are
managed; secrets and infrastructure remain with their existing owners. The first
adoption changed tracking metadata only. The subsequent digest rollout preserved
the same binaries; all three deployments are ready and ArgoCD is Synced/Healthy.
A post-release Temporal scheduled smoke completed successfully at 13:39 UTC.
To remove future exceptions, [ACTIVITY-WP-0041](../../activity-core/workplans/ACTIVITY-WP-0041-gitops-adoption.md)
owns the concrete follow-up: reconcile manifests and publish immutable registry
images; adopt activity-core into railiance01 ArgoCD with a verified resource set;
and approve standing, bounded merge/sync authority after the adoption soak.
Existing policy requires separate authorization for adoption and automation.
ArgoCD adoption alone does not remove per-change human approval. Routine releases
must pass automated tests, scoped review, deployment-health checks and rollback;
policy/access/budget changes remain monthly decisions.
[Release evidence](evidence/2026-09-27-activity-core-gitops.json) records revisions,
digests, CI, health and registry retention protection. The conservative 24-hour
healthy observation window begins at 13:38:21 UTC; earliest eligibility is
September 28 at 15:38:21 Berlin, conditional on healthy evidence. Automatic sync
and pruning remain disabled.
[ACTIVITY-WP-0041](../../activity-core/workplans/ACTIVITY-WP-0041-gitops-adoption.md)
retains authenticated review/health receipts, narrowly bound unattended release
identity and failed-health automatic rollback proof. RPF-WP-0048 owns platform
observation and digest-aware retention; current baseline tag aliases are already
protected. A tested image-only validator exists, but is not an authority grant.
These remaining gates prevent routine releases from needing fresh exceptions.
Policy/access/budget changes remain monthly decisions.
The owner handoff is [ACTIVITY-WP-0040](../../activity-core/workplans/ACTIVITY-WP-0040-frontend-patterns-feedback.md).