Files
coulomb-loop/activity-definitions/hourly-ci-health-escalation.md
tegwick 169a71f3e3 feat: advance LOOP-WP-0002/0003/0004 without activity-core blockers
Document event payload contract, draft disabled ActivityDefinitions for
CI/regulator/registry hygiene, initialize loop health snapshots and
regulator dashboard, record DEC-005 kaizen-stack promotion, and close
supplier-independent workplan tasks.
2026-06-18 13:10:59 +02:00

46 lines
1.5 KiB
Markdown

---
id: coulomb-hourly-ci-health-escalation
name: Hourly CI Health Escalation (coulomb-loop bootstrap)
enabled: false
owner: coulomb-loop
governance: coulomb_social
status: proposed
trigger:
type: cron
cron_expression: "40 * * * *"
timezone: Europe/Berlin
misfire_policy: skip
context_sources:
- type: kaizen
query: discover_kaizen_projects
params:
marker: .kaizen/schedule.yml
roster: /home/worsch/coulomb-loop/loops/kaizen-stack/roster.yaml
bind_to: context.projects
---
# Hourly CI Health Escalation (bootstrap)
LOOP-WP-0002 T06 — pilot-only CI degradation signal. Deferred to daily phase for
full Gitea API integration; bootstrap uses manual probe task template.
```rule
id: flag-ci-degraded
for_each: context.projects
bind_as: p
condition: 'context.p.ci_failure_streak >= 2'
action:
task_template: "CI degraded on {context.p.repo} — test-maintenance review"
description: |
Pilot repo shows ≥2 CI failures in 24h (signal from state-hub or probe).
kaizen-agentic schedule prepare test-maintenance --target {context.p.root}
Run failing tests locally: make test
Load agents/agent-test-maintenance.md
target_repo: context.p.repo
priority: high
labels: ["kaizen", "quality-escalation", "test-maintenance", "coulomb-loop", "bootstrap"]
```
**Note:** `ci_failure_streak` requires a future state-hub query or shell resolver.
Keep `enabled: false` until probe resolver ships. Daily variant: rename cron to
`0 6 * * *` when promoting per `loops/quality-escalation/cadence.yml`.