Files
coulomb-loop/SCOPE.md
tegwick 3225cf9dd6 Mark activity-core weekly sync complete (DEC-008)
Definitions and Temporal schedules synced; daily/hourly coulomb defs
disabled. Weekly resolver returns 6 scheduled_runs on pilot roster.
2026-06-19 02:04:00 +02:00

2.4 KiB

SCOPE

One-liner

Customer engagement repository for Coulomb fleet self-improvement loops — contracts, rosters, and activity definitions; not agent runtime.

Core Idea

Coulomb hires kaizen-agentic as supplier. coulomb-loop organizes what runs, where, and how often; supplier agents execute in target fleet repos with project-scoped memory and metrics.

In Scope

  • Engagement INTENT, workplans (LOOP-WP-*), ADRs, decision proposals
  • Loop rosters, cadence state, health records under loops/
  • ActivityDefinition copies for activity-core sync
  • state-hub workstream and progress event coordination
  • History and assessment artefacts
  • reuse-surface capability registration for the engagement itself

Out of Scope

  • Kaizen agent definitions (supplier: kaizen-agentic)
  • Temporal scheduling and context resolvers (owner: activity-core)
  • State-hub service code (owner: state-hub / the-custodian)
  • Application code for Coulomb products (e.g. vergabe-teilnahme)
  • .kaizen/ runtime state in this repo (lives in target repos)

Relevant When

  • Operating or extending Coulomb fleet self-improvement loops
  • Onboarding a new loop or cadence phase
  • Reviewing supplier engagement health (LOOP-WP-0004)

Not Relevant When

  • Authoring or publishing kaizen agents (use kaizen-agentic)
  • Implementing activity-core resolvers (use activity-core)
  • Product feature work in coulomb_social apps

Current State

  • Status: active (operate — weekly cadence)
  • Implementation: four loops operational on custodian pilot roster (3 repos)
  • Stability: observation window closed 2026-06-19 via DEC-008 operator override (LOOP-WP-0005 done)
  • Usage: internal engagement; weekly Mon crons live; activity-core synced 2026-06-19

How It Fits

  • Upstream: kaizen-agentic (supplier), state-hub (roster), reuse-surface (registry signals)
  • Downstream: activity-core (task factory), target fleet repos (execution)
  • Often used with: the-custodian, issue-core

Getting Oriented

  • Start with: INTENT.md, .custodian-brief.md
  • Key paths: workplans/, docs/adr/, docs/decisions/, history/
  • Pending decisions: docs/decisions/DEC-*.md
  • kaizen-agentic — supplier agents and CLI
  • activity-core — scheduled task execution
  • reuse-surface — capability registry federation
  • the-custodian — coordination and state-hub operator