tegwick
e783dc9a2b
Register with state-hub, accept DEC-001–004 and ADR-004 rotation policy, scaffold pilot roster, hourly ActivityDefinition copies, and bootstrap log after schedule init on three custodian pilot repos.
66 lines
No EOL
2.2 KiB
Markdown
66 lines
No EOL
2.2 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 (bootstrap)
|
|
- Implementation: planning artefacts + hub registration complete
|
|
- Stability: evolving (hourly cadence bootstrap pending)
|
|
- Usage: internal engagement
|
|
|
|
## 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 |