2026-08-21 00:21:53 +02:00
|
|
|
---
|
2026-08-28 00:28:23 +02:00
|
|
|
id: AGENTIC-WP-ADHOC-2026-08-20
|
2026-08-21 00:21:53 +02:00
|
|
|
type: workplan
|
|
|
|
|
title: "Clarify agentic-resources scope for leadership and workforce architecture"
|
|
|
|
|
domain: infotech
|
|
|
|
|
repo: agentic-resources
|
|
|
|
|
status: finished
|
|
|
|
|
owner: codex
|
|
|
|
|
topic_slug: agent-workforce-governance
|
|
|
|
|
created: "2026-08-20"
|
|
|
|
|
updated: "2026-08-20"
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
# Clarify agentic-resources scope for leadership and workforce architecture
|
|
|
|
|
|
|
|
|
|
## Review and refine the repository boundary
|
|
|
|
|
|
|
|
|
|
```task
|
2026-08-28 00:28:23 +02:00
|
|
|
id: AGENTIC-WP-ADHOC-2026-08-20-T01
|
2026-08-21 00:21:53 +02:00
|
|
|
status: done
|
|
|
|
|
priority: medium
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
Review the implemented Helix Forge subsystem, `INTENT.md`, and the current
|
|
|
|
|
cross-repository architecture proposal from KAIZEN-WP-0013. Replace the stale
|
|
|
|
|
generated `SCOPE.md` with an evidence-based operational boundary that:
|
|
|
|
|
|
|
|
|
|
- distinguishes implemented agent-performance learning from proposed
|
|
|
|
|
workforce-management contracts;
|
|
|
|
|
- relates leadership-owned goals and mandates to agent workforce assignments;
|
|
|
|
|
- maps role, blueprint, budget, resource, scheduling, runtime, human-workforce,
|
|
|
|
|
and policy ownership without creating a monolithic control plane; and
|
|
|
|
|
- records the unimplemented inventory, `RoleAssignment`, capacity,
|
|
|
|
|
development, portfolio, and retirement gap.
|
|
|
|
|
|
|
|
|
|
Completed 2026-08-20. `SCOPE.md` now documents the current implementation, the
|
|
|
|
|
recommended agent-workforce boundary, the leadership-to-execution control
|
|
|
|
|
spine, explicit ecosystem ownership, and current maturity gaps.
|
|
|
|
|
|
|
|
|
|
## Correct the execution-layer abstraction
|
|
|
|
|
|
|
|
|
|
```task
|
2026-08-28 00:28:23 +02:00
|
|
|
id: AGENTIC-WP-ADHOC-2026-08-20-T02
|
2026-08-21 00:21:53 +02:00
|
|
|
status: done
|
|
|
|
|
priority: medium
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
Review `glas-harness` and `rein-aharness` implementation, intent, scope,
|
|
|
|
|
contracts, registry, and accepted ADRs. Correct the agentic-resources
|
|
|
|
|
architecture so the workforce and instance contracts target `glas-harness` as
|
|
|
|
|
the primary execution-layer abstraction rather than coupling directly to
|
|
|
|
|
`rein-aharness`.
|
|
|
|
|
|
|
|
|
|
Completed 2026-08-20. The scope now identifies Glas as owner of the harness
|
|
|
|
|
contract, execution profiles, rein routing, sandbox coordination, and gateway
|
|
|
|
|
evidence. Concrete reins—including the live Claude-Code-based
|
|
|
|
|
`rein-aharness` and the implemented `rein-openweights` alternative—remain
|
|
|
|
|
replaceable inner-loop backends. Assignment and instance contracts should
|
|
|
|
|
reference a versioned Glas profile or compatible execution requirements so
|
|
|
|
|
the rein, sandbox, tool policy, and base-model constellation can vary without
|
|
|
|
|
rewriting workforce architecture.
|
|
|
|
|
|
|
|
|
|
Follow-through later on 2026-08-20: `GLAS-WP-0004` implemented the referenced
|
|
|
|
|
contract as Glas contract `1.0`, including explicit versioned profiles for
|
|
|
|
|
`rein-aharness` and `rein-openweights`, common execution evidence, and
|
|
|
|
|
assignment/role/duty/goal/resource-envelope reference fields. The
|
|
|
|
|
agentic-resources boundary above is now an available execution integration,
|
|
|
|
|
not only an architectural target.
|
|
|
|
|
|
|
|
|
|
Live follow-through completed 2026-08-21: both the Claude-backed and
|
|
|
|
|
open-weight profiles completed the same bounded task with real commits and
|
|
|
|
|
verified sandbox teardown through the Glas contract.
|
