coulomb/kaizen-agentic

Files

tegwick b48a2102d7 WP-0004: ecosystem integration complete

Add Helix Forge correlation (HELIX_SESSION_UID env, metrics correlate),
artifact-store publish (metrics publish), activity-core ActivityDefinition
references, integration patterns docs, and canon/knowledge design artifacts.

2026-06-16 01:53:01 +02:00

1.1 KiB

Raw Permalink Blame History

kontextual-engine Wiki Ingestion Spike

Design note (WP-0004 Part 4). No runtime dependency.

Proposed manifest

ingestion:
  source_repo: kaizen-agentic
  asset_class: strategic-knowledge
  paths:
    - wiki/**/*.md
    - INTENT.md
    - docs/adr/ADR-*.md
  exclude:
    - wiki/**/xxx
  metadata:
    domain: custodian
    topic_id: cee7bedf-2b48-46ef-8601-006474f2ad7a
    producer: kaizen-agentic
  refresh:
    trigger: git-push-main
    retention_class: operational-knowledge

Rationale

wiki/ holds product narrative and integration contracts not suited for agent prompts alone
ADRs are normative; kontextual-engine can index them for cross-repo retrieval
Agent definitions (agents/) remain separate — executable personas vs strategic docs

Open questions

Chunking strategy for KaizenAgentTemplate.md (section-aware vs whole-file)
Whether Coach synthesis outputs should be ingested as derived assets
Correlation with info-tech-canon profiles when both exist for one agent

Next step

Dedicated workplan after WP-0004 baseline; evaluate kontextual-engine ingestion API stability before hard dependency.