generated from coulomb/repo-seed
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.
This commit is contained in:
66
docs/decisions/DEC-003-activity-definition-ownership.md
Normal file
66
docs/decisions/DEC-003-activity-definition-ownership.md
Normal file
@@ -0,0 +1,66 @@
|
||||
# DEC-003 — ActivityDefinition Copy vs Reference
|
||||
|
||||
**Status:** accepted
|
||||
**Date:** 2026-06-18
|
||||
**Owner:** Bernd
|
||||
**Blocks:** LOOP-WP-0001 T04, activity-core sync workflow
|
||||
|
||||
---
|
||||
|
||||
## Question
|
||||
|
||||
How should coulomb-loop ActivityDefinitions relate to kaizen-agentic supplier templates?
|
||||
|
||||
## Context
|
||||
|
||||
ADR-002 assigns ActivityDefinition **copies** to the customer repo. activity-core
|
||||
syncs from its own catalog path (ACT-ADR-002). Two sync models are possible.
|
||||
|
||||
## Options
|
||||
|
||||
### A — Customer-owned copies (recommended)
|
||||
|
||||
Copy supplier templates into `coulomb-loop/activity-definitions/`. activity-core
|
||||
syncs from coulomb-loop path (or vendored subtree). Customer edits cron, labels,
|
||||
roster params without supplier release.
|
||||
|
||||
| Pros | Cons |
|
||||
|------|------|
|
||||
| Coulomb controls cadence ramp (hourly bootstrap) | Drift from supplier templates |
|
||||
| Matches ADR-002 | Manual merge when supplier updates templates |
|
||||
|
||||
### B — Supplier catalog only
|
||||
|
||||
Reference supplier repo path; activity-core syncs `kaizen-agentic/docs/integrations/activity-definitions/`.
|
||||
|
||||
| Pros | Cons |
|
||||
|------|------|
|
||||
| Single source of truth | Hourly bootstrap crons don't match supplier weekly defaults |
|
||||
| Less copy maintenance | Customer cannot tune without supplier PR |
|
||||
|
||||
### C — Hybrid manifest
|
||||
|
||||
`coulomb-loop/activity-definitions/manifest.yaml` lists supplier source + local overrides (cron, enabled, labels). activity-core merge tool applies patches.
|
||||
|
||||
| Pros | Cons |
|
||||
|------|------|
|
||||
| Drift-aware automation | Requires new activity-core or coulomb-loop tooling |
|
||||
| Best long-term for multiple customers | Not available today |
|
||||
|
||||
## Recommendation
|
||||
|
||||
**Option A** for bootstrap (minimal tooling). Track **Option C** in KAIZEN-WP-0008
|
||||
as supplier playbook enhancement for second customer.
|
||||
|
||||
## Decision record
|
||||
|
||||
| Field | Value |
|
||||
|-------|-------|
|
||||
| Chosen option | **A** — customer-owned copies |
|
||||
| Decided by | Bernd Worsch |
|
||||
| Decided at | 2026-06-18 |
|
||||
| Notes | Option C hybrid manifest tracked in KAIZEN-WP-0008 T08 |
|
||||
|
||||
## On approval
|
||||
|
||||
Proceed with LOOP-WP-0001 T04 copy step; document merge procedure in `loops/kaizen-stack/supplier-notes.md`.
|
||||
Reference in New Issue
Block a user