core-hub/activity-definitions/core-hub-stabilization-daily.md
tegwick 7a95a8345c
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / pytest-smoke (push) Failing after 2s
Build and Publish Container Image / build-and-push (push) Successful in 19s
docs: prepare core-hub archive closeout
2026-08-21 21:23:57 +02:00

1.8 KiB

id name type version enabled owner governance status created updated trigger context_sources
b4c8e2f1-6a3d-4e5b-9f0c-2d7e8a1b3c4d Core Hub Stabilization Daily Check activity-definition 1.0 false core-hub core-hub archived 2026-07-07 2026-08-21
type cron_expression timezone misfire_policy
cron 0 9 * * * Europe/Berlin skip
type query required params bind_to
core-hub stabilization_check true
source closeout base_url window_start window_end min_widget_types evidence_sinks
activity-core false https://hub.coulomb.social 2026-07-03T00:00:00+00:00 2026-07-10T17:35:00+00:00 26
type event_type author workstream_id task_id
state-hub-progress core_hub_stabilization_check activity-core a8d66822-e435-4b1e-ad81-37a298d1795e 16eb7ce3-b574-4667-a189-c14ff5d0502b
context.core_hub_stabilization_check

ActivityDefinition: Core Hub Stabilization Daily Check

Historical definition for the completed July 2026 Core Hub/Inter-Hub stabilization window. It is disabled and must not be reused for the August hub-core cutover window.

Purpose

Scheduled hub-visible health gate for CORE-WP-0007-T02 during the post-cutover stabilization window (2026-07-03 → 2026-07-10). Complements the manual scripts/core_hub_stabilization_check.sh script with fleet-side evidence in State Hub progress.

Trigger

Daily at 09:00 Europe/Berlin while the stabilization window is open. Runs outside the window are recorded as skipped with reason=outside_stabilization_window.

Output Contract

  • one State Hub progress event with event_type: core_hub_stabilization_check
  • compact pass/fail detail for public production surface checks
  • no LLM call and no direct workplan edits