1.8 KiB
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 |
|
|
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