coulomb/kaizen-agentic
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: align execution handoff with Glas
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details
ci / test (push) Successful in 2m10s
Details

Browse source
This commit is contained in:
tegwick 2026-08-21 08:30:13 +02:00
parent d691135c4a
commit 11fa383817
16 changed files with 126 additions and 61 deletions
Download patch file Download diff file Expand all files Collapse all files

19
docs/integrations/activity-core-handoff-wp0006.md
View file

@ -1,15 +1,18 @@
# activity-core Handoff — Scheduled Agent Execution (WP-0006)
> **Historical supplier handoff, completed for the initial resolver/pilot path.**
> The current production composition is activity-core durable `ops_run` work
> claimed by rein-aharness through its generic `agent-session` approach. The
> resolver and preparation contracts below remain compatible inputs.
> The initial production composition used activity-core durable `ops_run` work
> claimed by rein-aharness through its generic `agent-session` approach. Glas
> contract 1.0 now defines the rein-neutral execution boundary: new blueprint
> and agent-instance handoffs should carry a versioned `harness_profile_ref`.
> The resolver and preparation contracts below remain compatible inputs.
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, schedule firing,
and durable work creation (repo boundary, ADR-005); rein-aharness owns governed
execution.
and durable work creation (repo boundary, ADR-005). Task intake remains
rein-local where implemented; glas-harness owns explicit execution-profile
resolution and normalized evidence.
Open this as an activity-core issue/PR titled *"Enable kaizen scheduled agent
execution (WP-0006)"* and track the boxes there.
@ -74,9 +77,9 @@ 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`.
For unattended operation, confirm the resulting `ops_run` is claimable and the
rein-aharness worker selects the `agent-session` approach before enabling the
schedule broadly.
For unattended operation, confirm the resulting `ops_run` is claimable, the
blueprint/instance provides an approved `harness_profile_ref`, and Glas resolves
it without a hidden rein/model fallback before enabling the schedule broadly.
## Pilot roster