# ActivityDefinition Override Manifest (design)

**Status:** design-only (DEC-003 option C future)
**Implements:** KAIZEN-WP-0008 T08
**Runtime:** none in v1 — customer-owned copies (option A) during bootstrap

## Problem

Customer repos copy supplier ActivityDefinitions and tune cron, labels, and
`enabled` flags. When supplier templates change, manual merge is error-prone.
A manifest declares **source + overrides** without duplicating full definition bodies.

## Proposed file

`activity-definitions/manifest.yaml` in the customer repo:

```yaml
version: "1"
supplier_repo: kaizen-agentic
supplier_path: docs/integrations/activity-definitions
engagement: coulomb-loop

definitions:
  - supplier_id: kaizen-weekly-coach-orientation
    customer_id: coulomb-hourly-coach-orientation
    source: ../../kaizen-agentic/docs/integrations/activity-definitions/weekly-coach-orientation.md
    overrides:
      id: coulomb-hourly-coach-orientation
      name: Hourly Kaizen Coach Orientation (coulomb-loop bootstrap)
      owner: coulomb-loop
      governance: coulomb_social
      enabled: true
      trigger:
        cron_expression: "15 * * * *"
      context_sources:
        - params:
            roster: /home/worsch/coulomb-loop/loops/kaizen-stack/roster.yaml
            cadence: daily

  - supplier_id: kaizen-low-success-rate-review
    customer_id: coulomb-low-success-rate-review
    overrides:
      enabled: false
      owner: coulomb-loop
```

## Merge rules (future tooling)

1. Parse supplier definition markdown (frontmatter + body)
2. Deep-merge `overrides` (customer wins on conflict)
3. Write customer copy to `activity-definitions/<customer_id>.md`
4. `sync_activity_definitions` reads customer copies only (unchanged today)

## Ownership

| Layer | Owner |
|-------|-------|
| Manifest schema | kaizen-agentic (supplier ADR/extension) |
| Manifest instance | customer repo |
| Merge CLI | TBD — `coulomb-loop` or `activity-core` |
| Sync runtime | activity-core (unchanged) |

## Bootstrap path (today)

Use **option A**: hand-copy definitions, edit cron/labels, track drift in
`loops/kaizen-stack/supplier-notes.md`. Revisit manifest when a second customer
engagement starts.

## Related

- coulomb-loop `docs/decisions/DEC-003-activity-definition-ownership.md`
- [customer-engagement-playbook.md](customer-engagement-playbook.md)