Files

tegwick e783dc9a2b Bootstrap coulomb-loop engagement: governance, loops, and activity definitions.

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.

2026-06-18 04:53:51 +02:00

2.0 KiB

Raw Blame History

DEC-001 — Pilot Roster Scope

Status: accepted Date: 2026-06-18 Owner: Bernd (Coulomb operator) Blocks: LOOP-WP-0001 T02, LOOP-WP-0003 T05

Question

Which repositories should participate in the bootstrap-phase self-improvement loops before fleet expansion?

Context

LOOP-WP-0001 proposes three custodian-domain pilots:

kaizen-agentic — supplier dogfood
the-custodian — state-hub / coordination operator
activity-core — scheduler owner

The full Coulomb fleet has 57 state-hub repos across 12 domains. Hourly bootstrap on all repos would create unsustainable task volume.

Options

A — Custodian pilot only (recommended default)

3 repos: kaizen-agentic, the-custodian, activity-core

Pros	Cons
All loop infrastructure owners in one batch	Does not exercise coulomb_social domain repos
Minimal noise; fast E2E proof	Fleet improvement delayed
Aligns with supplier WP-0006 pilot design

B — Custodian pilot + one coulomb_social repo

4 repos: option A + vergabe-teilnahme

Pros	Cons
Validates engagement under customer domain	Mixed stack (Django app vs infra repos)
Product-facing dogfood	Extra setup for app-specific agents

C — Domain-stratified mini-pilot (5 repos)

5 repos: option A + reuse-surface + vergabe-teilnahme

Pros	Cons
Covers helix_forge registry + coulomb_social product	More hourly tasks; slower bootstrap exit
Exercises LOOP-WP-0003 registry hygiene early

Recommendation

Option A for bootstrap; expand via LOOP-WP-0003 domain rollout after LOOP-WP-0004 approves first promotion to daily.

Decision record

Field	Value
Chosen option	A — custodian pilot only (3 repos)
Decided by	Bernd Worsch
Decided at	2026-06-18
Notes	Fleet expansion via expansion_queue; rotation per ADR-004 when diminishing returns detected

On approval

Update loops/kaizen-stack/roster.yaml and close LOOP-WP-0001 T02.

2.0 KiB Raw Blame History