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

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

View file

@ -118,8 +118,10 @@ contract. Current unattended execution composes it as follows:
|-------|-------|----------|
| Schedule/event and eligibility | activity-core | Temporal definition/rule plus repo/agent context |
| Durable work | activity-core | Unique idempotency key, `ops_run` state, lease, retry, result |
| Claim and execution | rein-aharness | Claim loop, `agent-session` approach, policy/profile/runtime resolution |
| Task intake | Caller or selected rein | Claim/receive bounded work; intake remains rein-local where implemented |
| Agent orientation | kaizen-agentic | `schedule prepare <agent>` offline bundle |
| Execution resolution | glas-harness | Explicit versioned `harness_profile_ref` → rein/model/sandbox/tools/limits; normalized evidence |
| Inner execution | Glas-selected rein | Backend-specific bounded loop, policy enforcement, and credential use |
| Coordination evidence | State Hub | Roster, workplan/progress references; never prompts or secrets |
| Improvement evidence | kaizen-agentic / artifact-store | Project metrics and optional durable artifacts |
@ -128,7 +130,8 @@ work. The automated path should keep prompts, secrets, and raw model output out
of `ops_run` and State Hub records.
**Boundary:** kaizen-agentic declares and prepares; activity-core schedules and
queues; rein-aharness executes; State Hub owns the roster and coordination view.
queues; glas-harness resolves the explicit execution profile; the selected rein
executes; State Hub owns the roster and coordination view.
---