Record live reporting schedules and scoped deployment exception

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e241-8285-7a63-8c0c-51c9cb824dc3

docs/ActivityCoreLoop.md

@@ -35,25 +35,36 @@ from silently producing a successful empty report.
 
 ## Activation and proof
 
-Current state: source definitions are disabled; collector and deployment are
-prepared under ACTIVITY-WP-0040. No scheduled production execution is claimed.
-[Setup evidence](evidence/2026-09-27-activity-core-setup.json) records 63 passing
-checks, the built image, real Forgejo collection smoke and production dry-run.
-The worker overlay changes only the resolver module and registration, based on
-the existing production worker image. API, router and dependencies stay pinned.
+Current state: deployed and all three schedules enabled on 2026-09-27 under the
+founder's explicit scoped exception, State Hub decision
+`e5dd02cb-b5b2-45c8-a600-748ea2ffd31b` (`ADMINISTER @ realm:kubernetes/railiance01`,
+`activation=APPROVED`). This is not a standing waiver of the estate deployment gate.
 
-Activation requires the documented cluster change path. The estate's
-`the-custodian/docs/kubernetes-change-gate-decision.md` treats unmapped targets as
-production-tier and requires Git/ArgoCD reconciliation. Activity-core currently has
-no ArgoCD application. A direct rollout therefore needs an explicit scoped policy
-exception, or prior ArgoCD adoption; ordinary permission to implement is not a
-claim that the estate gate has already been satisfied.
+[Setup evidence](evidence/2026-09-27-activity-core-setup.json) records the tests,
+image and preflight. [Activation evidence](evidence/2026-09-27-activity-core-activation.json)
+records the successful worker rollout, three completed manual workflows and their
+State Hub reports, active Temporal schedules without drift, and a completed
+one-shot scheduled smoke at 11:28:45 UTC. That smoke was started by Temporal;
+it is distinct from the first natural recurring runs, which are still ahead.
 
-Once deployed, sync definitions, run one manual smoke per definition, verify the
-State Hub report sink, enable and re-project the definitions, then sync schedules.
-Record workflow IDs, schedule state and first natural scheduled executions here.
-Use manual smoke evidence only as manual evidence. Rollback restores the previous
-worker image and disables these three definitions followed by schedule sync.
+The next regular runs are September 28 at 02:00, September 29 at 03:00, and
+October 1 at 09:00, respectively, in Europe/Berlin. All verified reports correctly
+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.
+
+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.
 
 The owner handoff is [ACTIVITY-WP-0040](../../activity-core/workplans/ACTIVITY-WP-0040-frontend-patterns-feedback.md).