Some checks failed
ci / test (push) Has been cancelled
Update handoff checklist: discover_kaizen_scheduled_repos implemented and live on coulomb pilot definitions; document remaining weekly-template deferral.
4.1 KiB
4.1 KiB
activity-core Handoff — Scheduled Agent Execution (WP-0006)
Coordination checklist for the activity-core team to enable kaizen scheduled agent runs. kaizen-agentic owns the schedule contract, the prepare CLI, and the ActivityDefinition drafts; activity-core owns the resolver, the schedule firing, and task creation (repo boundary, ADR-005).
Open this as an activity-core issue/PR titled "Enable kaizen scheduled agent execution (WP-0006)" and track the boxes there.
What kaizen-agentic ships (done in this repo)
.kaizen/schedule.ymlschema +schedule validate|init|list|prepareCLI- ADR-005 contract
- Resolver spec: discover-kaizen-scheduled-repos.md
- State Hub roster fields design: state-hub-roster-fields.md
- Draft definitions (
enabled: false): weekly-coach-orientation, weekly-optimization-review - Event payload spec: kaizen-schedule-prepared-event.md
What activity-core must do
- Implement resolver
discover_kaizen_scheduled_reposper the spec (activity_core/context_resolvers/kaizen.py). - Add resolver unit tests —
tests/test_kaizen_context_resolver.py(7 passed). - Copy custodian weekly definitions from
docs/integrations/activity-definitions/(weekly-coach-orientation.md,weekly-optimization-review.md) into the activity-core catalog path (per ACT-ADR-002). Deferred: coulomb-loop engagement ships customer-owned daily bootstrap definitions instead (LOOP-WP-0001). - Register weekly definition slugs in the activity-core index (when custodian fleet moves off coulomb engagement copies).
- Run
make sync-activity-definitions— coulomb-loop definitions synced (coulomb-hourly-coach-orientation,coulomb-hourly-optimization-review, etc.). - Wire cron triggers — daily stabilize chain on pilot roster (08:00–10:00).
- Smoke test — resolver dry-run returns 6
scheduled_runson coulomb roster;schedule prepare coachsucceeds onkaizen-agenticandthe-custodian. - Enable gradually — coulomb bootstrap definitions
enabled: trueon pilot. - Verify runner prerequisites —
kaizen-agenticon PATH;KAIZEN_RUNNER_HOSTset on worker (bnt-lap001).
Supplier closure evidence (2026-06-18)
| Check | Result |
|---|---|
Resolver dry-run (coulomb roster, cadence: daily) |
6 runs across 3 pilot repos |
tests/test_kaizen_context_resolver.py |
7 passed |
schedule validate + prepare coach |
OK on kaizen-agentic, the-custodian, activity-core |
| Live definitions using resolver | f234bb1a coach, 097fc027 optimization (enabled) |
Remaining activity-core item: optional custodian-fleet weekly templates (enabled: false
in kaizen-agentic drafts) when engagement moves beyond coulomb-loop bootstrap copies.
State Hub team (the-custodian)
- Optional: add
kaizen_schedule_enabledrepo flag +GET /repos/filter (v2 pre-filter; the repo file remains the source of truth).
Smoke test (manual, runner-agnostic)
cd /path/to/pilot-repo
kaizen-agentic schedule init # if not already present
kaizen-agentic schedule validate # exit 0
kaizen-agentic schedule list # shows coach + optimization enabled
kaizen-agentic schedule prepare coach # non-empty orientation bundle
Then in activity-core: run the resolver (dry-run) and confirm one
scheduled_run per enabled (repo, agent) with a correct prepare_command.
Pilot roster
kaizen-agentic(dogfood)the-custodian(hub operator)- one additional custodian-domain repo with
.kaizen/state (TBD at pilot time)