docs: align execution handoff with Glas

docs/CLI_CHEAT_SHEET.md

@@ -120,9 +120,11 @@ kaizen-agentic schedule prepare optimization --format json
 ```
 
 activity-core fires the schedule and creates durable `ops_run` work per
-(repo, agent). rein-aharness claims that work and runs the governed
-`agent-session`, including `schedule prepare`. kaizen-agentic does not run cron,
-own the queue, resolve credentials, or invoke an LLM.
+(repo, agent). Rein-local intake or another caller receives that work and runs
+`schedule prepare`; the blueprint/instance then hands an explicit versioned
+`harness_profile_ref` to Glas for rein/model/sandbox/tool resolution.
+kaizen-agentic does not run cron, own the queue, resolve credentials, select a
+concrete rein, or invoke an LLM.
 
 ### Forward-deployed engagements (WP-0009 / DEC-FDA-001)
 ```bash

docs/INTEGRATION_PATTERNS.md

@@ -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.
 
 ---
 

docs/adr/ADR-005-scheduled-agent-execution.md

@@ -55,18 +55,22 @@ specific durable implementation:
 activity-core Temporal schedule/event
   → rule evaluation and eligibility
   → unique, idempotent ops_run with lease/retry state
-  → rein-aharness claim loop
-  → agent-session approach and governed runtime/profile resolution
+  → rein-local intake or caller receives bounded work
   → kaizen-agentic schedule prepare <agent>
-  → bounded coding-agent session
+  → Glas ExecutionRequest(harness_profile_ref=...)
+  → versioned profile resolves rein + model + sandbox + tool policy + limits
+  → bounded session and normalized execution evidence
   → ops_run result + State Hub progress + .kaizen metrics/artifact evidence
 ```
 
-`activity-core` owns schedule and durable work state. `rein-aharness` owns
-claiming, execution policy, credential routing, runtime selection, and bounded
-session operation. Kaizen Agentic continues to own declaration, agent craft,
-preparation, and improvement evidence. A human-started coding-agent session
-remains a supported execution mode and reference smoke path.
+`activity-core` owns schedule and durable work state. Task intake stays with
+the caller or rein where already implemented. A Kaizen blueprint or agent
+instance supplies an explicit, versioned `harness_profile_ref`; glas-harness
+resolves the concrete execution constellation and normalizes evidence; the
+selected rein owns its inner loop, backend policy, and credential use. Kaizen
+Agentic continues to own declaration, agent craft, preparation, and improvement
+evidence. A human-started coding-agent session remains a supported execution
+mode and reference smoke path.
 
 ### 1. Schedule manifest — `.kaizen/schedule.yml`
 
@@ -149,9 +153,11 @@ kaizen-agentic schedule prepare <agent> [--target PATH] [--format markdown|json]
   rule evaluation, and `ops_run` state belong to activity-core; the roster query
   belongs to State Hub.
 - **No LLM invocation.** `prepare` produces a runner-agnostic bundle; a human or
-  rein-aharness-governed coding-agent session executes it.
-- **No runtime authority or credentials.** Those remain with rein-aharness and
-  the ecosystem credential/authorization owners.
+  Glas-selected rein executes it.
+- **No concrete rein/model selection.** Kaizen carries a versioned
+  `harness_profile_ref`; glas-harness resolves it without a hidden default.
+- **No runtime authority or credentials.** Those remain with Glas, the selected
+  rein, and the ecosystem credential/authorization owners.
 - **State-hub schema changes** (roster opt-in flag) are designed here but
   implemented in `the-custodian` (repo boundary).
 

docs/adr/ADR-007-forward-deployed-engagement-convention.md

@@ -132,16 +132,17 @@ should amend this ADR (or a successor), not re-open DEC-FDA-001 silently.
   `railiance-infra`; transfer requires explicit receiver acceptance before the
   supplier copy is removed or reduced to a pointer.
 - Manual preparation remains supported. Unattended host duties require an
-  engagement-specific activity-core definition and a rein-aharness execution
-  profile in addition to the generic `ops_run`/`agent-session` path.
+  engagement-specific activity-core definition and an approved versioned Glas
+  `harness_profile_ref` in addition to the generic `ops_run` intake path.
 - Kai is not a payment processor; EUR path remains future work
 
 ### Follow-ups
 
 - Complete the proposed pilot transfer to the client-owned `railiance-infra`
   evidence path and record its accepted commit
-- Register engagement-specific activity-core definitions and rein-aharness
-  profile for daily host-operator preparation when unattended operation is desired
+- Register engagement-specific activity-core definitions and a Glas execution
+  profile reference for daily host-operator preparation when unattended
+  operation is desired
 - EUR commercial FX after 2–3 engagement calibration cycles
 
 ## Pilot evidence

docs/agency-framework.md

@@ -332,9 +332,11 @@ kaizen-agentic schedule prepare coach   # orientation bundle for a scheduled run
 `schedule prepare <agent>` bundles the agent prompt, project memory, metrics
 summary, and repo pointers — offline, no State Hub required. kaizen-agentic does
 **not** run cron, own durable work, or invoke an LLM. activity-core fires the
-schedule and creates `ops_run` work; rein-aharness claims it and executes the
-prepared bundle through a governed `agent-session`. Manual sessions remain a
-supported fallback.
+schedule and creates `ops_run` work. Task intake remains rein-local where
+implemented. The blueprint/instance supplies a versioned
+`harness_profile_ref`; Glas resolves the concrete rein, model route, sandbox,
+tool policy, and limits and returns normalized evidence. Manual sessions remain
+a supported fallback.
 
 Schema: [integrations/schedule-schema.md](integrations/schedule-schema.md).
 

docs/assessments/2026-08-20-intent-role-automation-readiness.md

@@ -4,6 +4,15 @@
 
 **Workplan:** KAIZEN-WP-0012
 
+> **Execution-boundary update, 2026-08-21:** This assessment captured the
+> then-live activity-core → rein-aharness intake path. GLAS-WP-0004 subsequently
+> proved contract 1.0 across two rein/model constellations. Kaizen blueprints
+> and agent instances should now hand a versioned `harness_profile_ref` to
+> glas-harness rather than encode a concrete rein, provider, model, or sandbox.
+> Scheduling remains with activity-core and task/blueprint intake remains
+> caller- or rein-local; the assessment's ownership and budget findings remain
+> valid.
+
 **Assessment:** materially aligned, operationally useful, not yet at the full
 `INTENT.md` maturity target
 

docs/integrations/activity-core-handoff-wp0006.md

@@ -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
 

docs/integrations/forward-deployed-engagement-playbook.md

@@ -90,7 +90,7 @@ kaizen-agentic engagement close-session eng-... \
 - Enable entries in engagement `schedule.yml`; they declare intent but do not
   activate unattended work by themselves
 - Continue manual prepare until an engagement-specific activity-core definition
-  and rein-aharness profile have passed a bounded smoke test
+  and versioned Glas execution profile have passed a bounded smoke test
 - Daily: health + load; weekly: OS/security pass (privileged changes still gated)
 
 ### 8. Ramp-down (when ending)
@@ -161,9 +161,12 @@ Not required for operate. When ready:
 
 1. Customer or engagement repo owns the ActivityDefinition that identifies the
    engagement and emits idempotent, claimable `ops_run` work in activity-core.
-2. The run carries `agent-session` approach metadata and a compatible
-   rein-aharness profile reference; it does not carry secrets or raw prompts.
-3. rein-aharness claims the run, resolves credentials and policy, and executes
+2. The run or bound agent instance carries organizational references and an
+   approved versioned `harness_profile_ref`; it does not carry secrets or raw
+   provider prompts.
+3. Rein-local intake or another caller claims/receives the work and constructs
+   the Glas `ExecutionRequest`. Glas resolves the concrete rein, model, sandbox,
+   tool policy, and limits; the selected rein executes
    `kaizen-agentic engagement prepare <id>` inside the bounded session.
 4. Completion links the `ops_run`, engagement report, metrics, and State Hub
    progress without duplicating confidential content into coordination records.