agentic-resources/workplans/ADHOC-2026-08-20.md
repo-manager 091c7e25ad
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
chore(registrar): assign State Hub identifiers
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
2026-08-25 17:44:37 +02:00

3 KiB

id type title domain repo status owner topic_slug created updated state_hub_workstream_id
ADHOC-2026-08-20 workplan Clarify agentic-resources scope for leadership and workforce architecture infotech agentic-resources finished codex agent-workforce-governance 2026-08-20 2026-08-20 0f803d0d-cfba-5139-a476-3d0e54256daa

Clarify agentic-resources scope for leadership and workforce architecture

Review and refine the repository boundary

id: ADHOC-2026-08-20-T01
status: done
priority: medium
state_hub_task_id: "570d53c0-055b-54bb-ae07-17a3230f6bd1"

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

id: ADHOC-2026-08-20-T02
status: done
priority: medium
state_hub_task_id: "cf285ee4-709e-5cfc-8f2f-a8aad6486d57"

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.