Files
coulomb-loop/SCOPE.md
tegwick d74d3b5447 Open LOOP-WP-0005: stabilize observation and dashboard refresh
Bootstrap sprint complete; daily defs active. Start 14-day ADR-003 observation
window (review 2026-07-02). Refresh regulator dashboard and SCOPE current state.
2026-06-18 15:16:28 +02:00

66 lines
2.3 KiB
Markdown

# 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 (stabilize — daily cadence)
- Implementation: four loops operational on custodian pilot roster (3 repos)
- Stability: observation window 2026-06-18 → 2026-07-02 (LOOP-WP-0005)
- Usage: internal engagement; weekly promotion gated on regulator review
## 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`
## Related Repositories
- `kaizen-agentic` — supplier agents and CLI
- `activity-core` — scheduled task execution
- `reuse-surface` — capability registry federation
- `the-custodian` — coordination and state-hub operator