coulomb/coulomb-loop
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: complete LOOP-WP-0000 bootstrap — reuse-surface capability D0

Browse Source 
Register capability.coulomb-social.loop-orchestrate; validate passes.
Mark engagement bootstrap workplan done (8/8 tasks).
This commit is contained in:
Bernd Worsch
2026-06-18 11:02:05 +02:00
parent 6948f10968
commit 25f31c3851
4 changed files with 115 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
loops/kaizen-stack/supplier-notes.md
View File

@@ -1,8 +1,9 @@
# Supplier Notes (kaizen-agentic friction log)
| Date | Observation | Suggested supplier fix |
|------|-------------|------------------------|
| 2026-06-18 | `schedule init` defaults weekly; bootstrap needs manual cron patch | KAIZEN-WP-0008 `schedule init --engagement --bootstrap-cadence hourly` |
| 2026-06-18 | `metrics optimize` runs with 0 records (OK) but message could link to engagement | Document bootstrap expectation in playbook |
| 2026-06-18 | No `--emit-event` yet for LOOP-WP-0002 | KAIZEN-WP-0008 T03 |
| 2026-06-18 | Rotation signals need aggregator CLI | KAIZEN-WP-0008 ADR-004 follow-on `metrics rotation-signals` |
| Date | Observation | Status |
|------|-------------|--------|
| 2026-06-18 | `schedule init` defaults weekly; bootstrap needs manual cron patch | **Shipped** — `schedule init --engagement --bootstrap-cadence hourly` |
| 2026-06-18 | `metrics optimize` with 0 records during bootstrap | **Documented** — playbook v1; expected until ≥10 records |
| 2026-06-18 | No `--emit-event` for LOOP-WP-0002 | **Shipped** — `metrics record --emit-event` |
| 2026-06-18 | Rotation signals need aggregator CLI | **Open** — `metrics rotation-signals` follow-on (ADR-004) |
| 2026-06-18 | activity-core `event-payload` resolver missing | **Open** — see kaizen `activity-core-handoff-engagement.md` R1 |