docs: align execution handoff with Glas

SCOPE.md

@@ -24,9 +24,11 @@ and optimization proposes the next safe refinement.
 KaizenAgentic **declares and prepares** agent work. It does not own the clock,
 credentials, policy enforcement, or LLM session runtime. In the current
 ecosystem, activity-core decides when/what/where and emits claimable work;
-rein-aharness binds a repo-owned instance to a Kaizen blueprint and executes a
-bounded session. This separation is the implementation of the strategic
-boundary in `INTENT.md`, not an unfinished runtime hidden in this repository.
+a repo-owned instance binds a Kaizen blueprint to a versioned
+`harness_profile_ref`; glas-harness resolves the concrete execution
+constellation; and the selected rein executes a bounded session. This
+separation is the implementation of the strategic boundary in `INTENT.md`, not
+an unfinished runtime hidden in this repository.
 
 ---
 
@@ -52,9 +54,9 @@ boundary in `INTENT.md`, not an unfinished runtime hidden in this repository.
   packages, staffed-role lifecycle, bound agent definitions, ramp-up/down,
   client-custodied memory, engagement metrics, and reference pilot artifacts
 - **Interoperability contracts and reference patterns** for activity-core,
-  rein-aharness, role-engine, agentic-resources, human-resources, fin-hub,
-  resource-control, llm-connect, State Hub, artifact-store, Helix Forge, and
-  Custodian discovery
+  glas-harness, the selected reins, role-engine, agentic-resources,
+  human-resources, fin-hub, resource-control, llm-connect, State Hub,
+  artifact-store, Helix Forge, and Custodian discovery
 - **ADRs, workplans, tutorials, and integration handoffs** that make these
   conventions human-readable and machine-consumable
 
@@ -94,8 +96,8 @@ boundary in `INTENT.md`, not an unfinished runtime hidden in this repository.
   to an executable agent blueprint
 - Translating leadership-owned goals and budget-constrained assignments into
   measurable blueprint, protocol, schedule, and evidence contracts
-- Integrating Kaizen work with activity-core, rein-aharness, State Hub, Helix
-  Forge, or artifact-store
+- Integrating Kaizen work with activity-core, glas-harness, a selected rein,
+  State Hub, Helix Forge, or artifact-store
 - Understanding the KaizenAgentic product and agency operating model
 
 ---
@@ -103,8 +105,8 @@ boundary in `INTENT.md`, not an unfinished runtime hidden in this repository.
 ## Not Relevant When
 
 - A task needs only ad-hoc automation with no reusable agent or improvement loop
-- The need is purely schedule/runtime operation; use activity-core and the
-  selected rein/harness
+- The need is purely schedule/runtime operation; use activity-core,
+  glas-harness, and the selected rein
 - The need is organizational role definition only; use role-engine
 - The need is agent inventory, assignment, capacity planning, portfolio review,
   or retirement; agentic-resources is the intended owner once its boundary is
@@ -127,8 +129,9 @@ boundary in `INTENT.md`, not an unfinished runtime hidden in this repository.
 - **Improvement loop:** metrics storage, summary, optimization, correlation,
   publishing, and `kaizen.metrics.recorded` event emission are implemented
 - **Automation contract:** schedule manifests and offline prepare bundles are
-  implemented; activity-core has a durable `ops_run` queue and rein-aharness has
-  a live claim loop plus a generic `agent-session` approach
+  implemented; activity-core has a durable `ops_run` queue; glas-harness
+  contract 1.0 resolves versioned execution profiles and is proven across two
+  rein/model constellations; rein-local intake remains where already implemented
 - **Agency model:** one supplier Role package and one staffed host-operator pilot
   prove the file conventions; broader role-catalog integration is not yet
   standardized
@@ -153,7 +156,8 @@ boundary in `INTENT.md`, not an unfinished runtime hidden in this repository.
 | Monetary budgets, commitments, burn, runway, and AI-plan booked cost | `fin-hub` | Consume provenance-bearing constraints; publish goal/assignment/duty attribution evidence |
 | Resource demand, capacity, allocation, utilization, and technical economics | `resource-control` | Consume capacity/cost evidence; do not duplicate resource or procurement authority |
 | Scheduling and claimable work | `activity-core` | Supply manifests, definitions, prepare commands, and event contracts |
-| Governed unattended execution | `rein-aharness` (selected rein) | Supply blueprint/orientation bundle; receive metrics and improvement evidence |
+| Governed execution abstraction | `glas-harness` | Supply versioned `harness_profile_ref` plus blueprint/orientation and organizational references; consume normalized evidence |
+| Inner execution loop and backend policy | Glas-selected rein (`rein-aharness`, `rein-openweights`, …) | Remain rein-neutral; receive metrics and improvement evidence |
 | Model/provider abstraction | `llm-connect` | Runtime dependency outside this repository |
 | Credentials and authorization | OpenBao/credential routing, identity and policy systems | Reference named routes/profiles only; never hold grants or secrets |
 | Durable coordination evidence | Custodian State Hub | Publish/index progress and workplan state; do not own hub code |
@@ -245,7 +249,7 @@ keywords: [metrics, feedback, optimization, evidence, events]
 type: integration
 title: Scheduled-agent declaration and preparation
 description: Validate repo-local schedules and assemble offline orientation bundles for activity-core-triggered, harness-executed runs.
-keywords: [schedule, activity-core, rein-aharness, preparation, automation]
+keywords: [schedule, activity-core, glas-harness, preparation, automation]
 ```
 
 ```capability
@@ -264,5 +268,6 @@ keywords: [kaizen, intent, template, optimization, operating-model]
   `make agents-sync-package`.
 - Agent definitions still use less structure than the full
   `wiki/KaizenAgentTemplate.md`; schema conformance is a maturity gap.
-- `.kaizen/schedule.yml` base fields are owned here. rein-aharness adds runtime
-  policy extensions and validates them separately.
+- `.kaizen/schedule.yml` base fields are owned here. Consumer-owned agent
+  instances carry a versioned `harness_profile_ref`; Glas and the selected rein
+  validate runtime policy separately.