Files
kaizen-agentic/workplans/kaizen-agentic-WP-0004-ecosystem-integration.md
tegwick b1fceeebc8
Some checks failed
ci / test (push) Failing after 37s
docs: close WP-0004 workplan and bind State Hub tasks
Add frontmatter tasks list with state_hub_task_id links and completion
section for ecosystem integration (Helix, activity-core, artifact-store).
2026-06-17 01:07:12 +02:00

283 lines
10 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
id: KAIZEN-WP-0004
type: workplan
title: "Ecosystem Integration: Helix Forge, activity-core, and artifact-store"
domain: custodian
repo: kaizen-agentic
status: completed
owner: kaizen-agentic
topic_slug: custodian
state_hub_workstream_id: 76be7294-e201-4074-91c0-6421992470fe
created: "2026-06-16"
updated: "2026-06-17"
tasks:
- id: T01
title: Document Helix Forge correlation contract cross-repo
status: done
state_hub_task_id: f365d19e-9619-4453-bebf-f1fd596b1bd1
- id: T02
title: Add HELIX_SESSION_UID to metrics record
status: done
state_hub_task_id: e7f47683-5957-49db-bcbd-3aa47f44a073
- id: T03
title: Add kaizen-agentic metrics correlate command stub
status: done
state_hub_task_id: 6ef8ba99-7d0c-44f4-835d-7a66e9d55984
- id: T04
title: Integration test for helix_session_uid correlation
status: done
state_hub_task_id: 9875422c-a54b-40f1-a444-6b485a9e57d6
- id: T05
title: Update EcosystemIntegration.md with worked example
status: done
state_hub_task_id: 0dc33d13-0e0b-4336-a7ad-371fc533b823
- id: T06
title: Draft weekly metrics optimize ActivityDefinition
status: done
state_hub_task_id: dbaa5f46-f66a-4a74-b4a0-97978e47d1c3
- id: T07
title: Draft post-install metrics scaffold ActivityDefinition
status: done
state_hub_task_id: 161a264a-8f70-4e37-a854-bd5a76a0e54b
- id: T08
title: Draft low success_rate review ActivityDefinition
status: done
state_hub_task_id: 3b58ad38-839c-436a-8d97-ef5a8f9beefe
- id: T09
title: Document activity-core triggers in INTEGRATION_PATTERNS.md
status: done
state_hub_task_id: a004b60f-4e8f-4881-b088-229ac9ab242f
- id: T10
title: Smoke test activity-core activation
status: done
state_hub_task_id: 84866bf1-5830-470d-87a5-9786222332c2
- id: T11
title: Define optimizer artifact package manifest
status: done
state_hub_task_id: 033a19db-fbd2-411f-9d2e-779d210400d4
- id: T12
title: Add kaizen-agentic metrics publish command
status: done
state_hub_task_id: 54517f2b-23e3-433b-a483-c59227625dbc
- id: T13
title: Map raw-evidence retention class in publish manifest
status: done
state_hub_task_id: 3b378789-a761-4472-b072-a346541be239
- id: T14
title: Integration test artifact-store publish
status: done
state_hub_task_id: a3566713-db58-4519-b9c4-5003421c1f1e
- id: T15
title: Document publish workflow in agency-framework.md
status: done
state_hub_task_id: 5d8255aa-fd7a-4fe6-bce2-3a176f954c7f
- id: T16
title: Map KaizenAgentTemplate to info-tech-canon profile outline
status: done
state_hub_task_id: 852c9cbf-0b0c-4f23-8594-905ca280c268
- id: T17
title: Draft info-tech-canon agent brief for tdd-workflow
status: done
state_hub_task_id: 62e05097-9033-401d-bbe0-d5d773da50fe
- id: T18
title: Spike kontextual-engine wiki ingestion manifest
status: done
state_hub_task_id: cd6962c7-aaed-4d7d-81de-37c0e3ed715e
- id: T19
title: Update ecosystem assessment with Part 4 outcomes
status: done
state_hub_task_id: 2c1f66f5-e6ab-4e19-88ca-818acb15a706
---
# KAIZEN-WP-0004 — Ecosystem Integration: Helix Forge, activity-core, and artifact-store
**Status:** completed
**Owner:** kaizen-agentic
**Repo:** kaizen-agentic
**Depends on:** KAIZEN-WP-0003 Part 3 (metrics CLI + `metrics optimize` operational)
## Goal
Compose KaizenAgentic with adjacent ecosystem repos so INTENT's measurement and
improvement vision spans **project** and **fleet** layers without duplicating
capabilities or violating repo boundaries.
Primary integrations: **agentic-resources** (Helix Forge), **activity-core**
(scheduled triggers), **artifact-store** (evidence retention). Secondary
integrations (info-tech-canon, kontextual-engine) are Part 4 stretch goals.
Reference: `wiki/EcosystemIntegration.md`, `history/2026-06-16-ecosystem-assessment.md`
---
## Part 1 — Helix Forge Correlation (agentic-resources)
Wire project metrics (ADR-004) to fleet session metrics without re-implementing
session ingestion.
### Tasks
- [x] T01 — Document correlation contract in `agentic-resources` (cross-repo PR or shared doc link from both repos)
- [x] T02 — Add optional `helix_session_uid` population to `metrics record` when env `HELIX_SESSION_UID` is set
- [x] T03 — Add `kaizen-agentic metrics correlate` — lookup Helix digest summary by UID (read-only adapter stub if Helix API not ready)
- [x] T04 — Integration test: synthetic project record with `helix_session_uid` round-trips through show/brief
- [x] T05 — Update `wiki/EcosystemIntegration.md` with worked correlation example
### Definition of done
- Project execution records can carry Helix correlation fields per ADR-004
- Documentation is bidirectional (kaizen-agentic + agentic-resources reference each other)
- No session JSONL ingestion code in kaizen-agentic
---
## Part 2 — activity-core Triggers
Define ActivityDefinitions for recurring kaizen operations.
### Tasks
- [x] T06 — Draft ActivityDefinition: weekly `metrics optimize` on repos with `.kaizen/metrics/`
- [x] T07 — Draft ActivityDefinition: post-install metrics scaffold validation (`memory init` check)
- [x] T08 — Draft ActivityDefinition: success_rate below 0.8 → issue-core review task
- [x] T09 — Document ActivityDefinition paths and activation contract in `docs/INTEGRATION_PATTERNS.md`
- [x] T10 — Smoke test: manual activation against a test repo with populated metrics
### Definition of done
- Three ActivityDefinition markdown files committed (location per activity-core convention)
- kaizen-agentic docs describe how activity-core triggers map to CLI commands
- No scheduling code in kaizen-agentic
---
## Part 3 — artifact-store Evidence Retention
Persist optimizer outputs as registered artifact packages.
### Tasks
- [x] T11 — Define artifact package manifest for optimizer run (`analysis.json` + `recommendations.jsonl`)
- [x] T12 — Add `kaizen-agentic metrics publish` — register optimizer output with artifact-store API (configurable endpoint)
- [x] T13 — Map retention class `raw-evidence` (180d) in publish manifest metadata
- [x] T14 — Integration test with artifact-store local backend (skip if service unavailable; mark `@pytest.mark.integration`)
- [x] T15 — Document publish workflow in `docs/agency-framework.md` metrics section
### Definition of done
- Optimizer outputs can be registered as artifact packages when artifact-store is reachable
- Retention metadata matches ADR-004 default
- Publish is optional — local-only workflows still work without artifact-store
---
## Part 4 — Canon and Knowledge (stretch)
Secondary integrations for template conformance and knowledge asset lifecycle.
### Tasks
- [x] T16 — Map `wiki/KaizenAgentTemplate.md` sections to info-tech-canon profile outline (design doc only)
- [x] T17 — Draft one InfoTechCanon-style agent brief for `tdd-workflow` pilot
- [x] T18 — Spike: kontextual-engine ingestion manifest for `wiki/` directory (design note, no runtime dependency)
- [x] T19 — Update `history/2026-06-16-ecosystem-assessment.md` with Part 4 outcomes
### Definition of done
- Design artifacts committed; no hard dependency on info-tech-canon or kontextual-engine services
- tdd-workflow brief serves as reference for fleet-wide brief rollout (future WP)
---
## Sequencing
```
WP-0003 Part 3 complete
Part 1 (T01T05) ──→ Part 2 (T06T10)
│ │
└──────────┬───────────┘
Part 3 (T11T15)
Part 4 (T16T19) [stretch]
```
Part 1 can start once `metrics record` and `metrics optimize` exist.
Parts 23 can overlap. Part 4 is non-blocking.
Estimated effort: 35 sessions after WP-0003 Part 3.
---
## Out of Scope
- Cloning or implementing tele-mcp (assess separately)
- phase-memory graph migration (future WP)
- Full KaizenGuidance codemod pipeline
- Owning activity-core, artifact-store, or agentic-resources code
---
## Success Criteria
1. Two-layer measurement model is documented, implemented at correlation layer,
and operable without repo merges.
2. Recurring kaizen checks can be triggered via activity-core without custom cron.
3. Optimizer evidence can be preserved in artifact-store when configured.
4. Canon/knowledge integration has a clear design path for later work.
---
## Completion
**Shipped:** v1.1.0v1.2.0 ecosystem integration layer.
| Part | Outcome |
|------|---------|
| 1 Helix | `HELIX_SESSION_UID` on `metrics record`, `metrics correlate`, bidirectional docs |
| 2 activity-core | Three ActivityDefinitions under `docs/integrations/activity-definitions/` |
| 3 artifact-store | `metrics publish` with `raw-evidence` retention manifest |
| 4 Canon/knowledge | Design docs for info-tech-canon and kontextual-engine (no runtime deps) |
All 19 tasks complete. Reciprocal Helix link verified in WP-0005 T16.
---
## State Hub Task IDs
| Code | UUID |
|------|------|
| T01 | f365d19e-9619-4453-bebf-f1fd596b1bd1 |
| T02 | e7f47683-5957-49db-bcbd-3aa47f44a073 |
| T03 | 6ef8ba99-7d0c-44f4-835d-7a66e9d55984 |
| T04 | 9875422c-a54b-40f1-a444-6b485a9e57d6 |
| T05 | 0dc33d13-0e0b-4336-a7ad-371fc533b823 |
| T06 | dbaa5f46-f66a-4a74-b4a0-97978e47d1c3 |
| T07 | 161a264a-8f70-4e37-a854-bd5a76a0e54b |
| T08 | 3b58ad38-839c-436a-8d97-ef5a8f9beefe |
| T09 | a004b60f-4e8f-4881-b088-229ac9ab242f |
| T10 | 84866bf1-5830-470d-87a5-9786222332c2 |
| T11 | 033a19db-fbd2-411f-9d2e-779d210400d4 |
| T12 | 54517f2b-23e3-433b-a483-c59227625dbc |
| T13 | 3b378789-a761-4472-b072-a346541be239 |
| T14 | a3566713-db58-4519-b9c4-5003421c1f1e |
| T15 | 5d8255aa-fd7a-4fe6-bce2-3a176f954c7f |
| T16 | 852c9cbf-0b0c-4f23-8594-905ca280c268 |
| T17 | 62e05097-9033-401d-bbe0-d5d773da50fe |
| T18 | cd6962c7-aaed-4d7d-81de-37c0e3ed715e |
| T19 | 2c1f66f5-e6ab-4e19-88ca-818acb15a706 |
**Hub workstream:** `kaizen-wp-0004-ecosystem-integration` (`76be7294-e201-4074-91c0-6421992470fe`)
---
## Notes
- ADR-004 Helix Forge correlation section is the authoritative field mapping
- WP-0001 T04 (telemetry) should evaluate tele-mcp as adapter candidate
- activity-core ActivityDefinitions live in activity-core repo per ACT-ADR-002/003;
kaizen-agentic commits reference copies or links under `docs/integrations/`