From 25f31c3851608945754dcfa5abf9e01bce9a337a Mon Sep 17 00:00:00 2001 From: tegwick Date: Thu, 18 Jun 2026 11:02:05 +0200 Subject: [PATCH] =?UTF-8?q?feat:=20complete=20LOOP-WP-0000=20bootstrap=20?= =?UTF-8?q?=E2=80=94=20reuse-surface=20capability=20D0?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Register capability.coulomb-social.loop-orchestrate; validate passes. Mark engagement bootstrap workplan done (8/8 tasks). --- loops/kaizen-stack/supplier-notes.md | 13 +-- ...ability.coulomb-social.loop-orchestrate.md | 96 +++++++++++++++++++ registry/indexes/capabilities.yaml | 9 +- .../LOOP-WP-0000-engagement-bootstrap.md | 12 +-- 4 files changed, 115 insertions(+), 15 deletions(-) create mode 100644 registry/capabilities/capability.coulomb-social.loop-orchestrate.md diff --git a/loops/kaizen-stack/supplier-notes.md b/loops/kaizen-stack/supplier-notes.md index d98e4d1..96bc60a 100644 --- a/loops/kaizen-stack/supplier-notes.md +++ b/loops/kaizen-stack/supplier-notes.md @@ -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` | \ No newline at end of file +| 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 | \ No newline at end of file diff --git a/registry/capabilities/capability.coulomb-social.loop-orchestrate.md b/registry/capabilities/capability.coulomb-social.loop-orchestrate.md new file mode 100644 index 0000000..5fff4b3 --- /dev/null +++ b/registry/capabilities/capability.coulomb-social.loop-orchestrate.md @@ -0,0 +1,96 @@ +--- +id: capability.coulomb-social.loop-orchestrate +name: Fleet Loop Orchestration Engagement +summary: Customer engagement capability for operating kaizen self-improvement loops across a registered fleet roster. +owner: coulomb-loop +status: draft +domain: coulomb_social +tags: + - coulomb-loop + - kaizen + - engagement + - activity-core + +maturity: + discovery: + current: D0 + target: D3 + confidence: low + rationale: Engagement repo registered; loop workplans and ADRs committed; automation partially live. + availability: + current: A0 + target: A2 + confidence: low + rationale: Orchestration depends on activity-core cron and manual operator steps during bootstrap. + +external_evidence: + completeness: + level: C0 + confidence: low + basis: scope_vs_intent_and_consumer_expectations + satisfied_expectations: + - INTENT and LOOP-WP workplans define loop map + broken_expectations: + - event-driven quality path blocked on activity-core event-payload resolver + out_of_scope_expectations: + - owning kaizen agent prompts + reliability: + level: R0 + confidence: low + basis: consumer_quality_signals + known_reliability_risks: + - bootstrap hourly E2E not yet at 3/3 consecutive cycles + +discovery: + intent: > + Make fleet-wide self-improvement loops operable as a governed engagement — + rosters, cadence policy, ActivityDefinitions, and health records — without + colocating agent runtime in the customer repo. + includes: + - pilot roster declaration + - activity-core definition copies and enable order + - cadence ramp and regulator policy (LOOP-WP-0004) + - supplier friction feedback to kaizen-agentic + excludes: + - kaizen agent definitions + - Temporal worker implementation + - per-repo .kaizen runtime in coulomb-loop + use_cases: + - Coulomb fleet kaizen bootstrap (kaizen-agentic, the-custodian, activity-core pilots) + research_memos: + - history/2026-06-18-initial-codebase-assessment.md + +availability: + current_level: A0 + target_level: A2 + current_artifacts: + - coulomb-loop/INTENT.md + - coulomb-loop/workplans/LOOP-WP-0000-engagement-bootstrap.md + - coulomb-loop/loops/kaizen-stack/roster.yaml + consumption_modes: + - informational + +relations: + depends_on: + - capability.activity.event-coordinate + supports: [] + related_to: + - capability.registry.validate + +consumer_guidance: + recommended_for: + - planning multi-repo kaizen engagements with activity-core orchestration + not_recommended_for: + - single-repo agent authoring (use kaizen-agentic directly) + known_limitations: + - D0 discovery only; automation maturity tracked in LOOP-WP-0001 bootstrap log + +promotion_history: [] +--- + +# Fleet Loop Orchestration Engagement + +`coulomb-loop` is the customer engagement repo for Coulomb fleet self-improvement +loops. Supplier: `kaizen-agentic`. Scheduler: `activity-core`. State: target repos. + +See `INTENT.md` and `workplans/LOOP-WP-0001` for operational status. \ No newline at end of file diff --git a/registry/indexes/capabilities.yaml b/registry/indexes/capabilities.yaml index f944e47..c8365ca 100644 --- a/registry/indexes/capabilities.yaml +++ b/registry/indexes/capabilities.yaml @@ -1,4 +1,7 @@ version: 1 -updated: '2026-06-16' -domain: helix_forge -capabilities: [] +updated: '2026-06-18' +domain: coulomb_social +capabilities: + - id: capability.coulomb-social.loop-orchestrate + path: registry/capabilities/capability.coulomb-social.loop-orchestrate.md + status: draft \ No newline at end of file diff --git a/workplans/LOOP-WP-0000-engagement-bootstrap.md b/workplans/LOOP-WP-0000-engagement-bootstrap.md index addf745..8f3705e 100644 --- a/workplans/LOOP-WP-0000-engagement-bootstrap.md +++ b/workplans/LOOP-WP-0000-engagement-bootstrap.md @@ -4,7 +4,7 @@ type: workplan title: "Engagement bootstrap (registration, assessment, governance)" domain: coulomb_social repo: coulomb-loop -status: active +status: done owner: coulomb-loop topic_slug: coulomb_social supplier: kaizen-agentic @@ -34,14 +34,14 @@ tasks: status: done title: Fill SCOPE.md and .claude/rules integration stubs - id: T08 - status: todo + status: done title: Register reuse-surface capability entry for loop orchestration state_hub_workstream_id: "0df6df54-4313-4c2d-93f2-dc6844fe47ec" --- # LOOP-WP-0000 — Engagement Bootstrap -**Status:** active +**Status:** done **Owner:** coulomb-loop **Purpose:** One-time (and ongoing governance) setup before loop automation runs. @@ -135,13 +135,13 @@ SCOPE.md and `.claude/rules/{repo-identity,architecture,repo-boundary,stack-and- ```task id: LOOP-WP-0000-T08 -status: todo +status: done priority: low state_hub_task_id: "54f5e683-0081-4db1-abdb-4f57323f840e" ``` -Add capability row for fleet loop orchestration engagement (D0 scaffold). -Run `reuse-surface validate` when entry drafted. +`capability.coulomb_social.loop-orchestrate` at D0 in `registry/capabilities/`. +Index updated; `reuse-surface validate` passes (2026-06-18). ## Definition of done