Model goal-driven agent workforce governance
This commit is contained in:
parent
d1dece7409
commit
6ed5708c21
5 changed files with 373 additions and 51 deletions
|
|
@ -0,0 +1,81 @@
|
|||
---
|
||||
id: KAIZEN-WP-0013
|
||||
type: workplan
|
||||
title: "Agent workforce, goal, leadership, and budget governance"
|
||||
domain: agents
|
||||
repo: kaizen-agentic
|
||||
status: finished
|
||||
owner: codex
|
||||
topic_slug: custodian
|
||||
created: "2026-08-20"
|
||||
updated: "2026-08-20"
|
||||
---
|
||||
|
||||
# KAIZEN-WP-0013 — Agent workforce, goal, leadership, and budget governance
|
||||
|
||||
## Assess sibling resource-management repositories
|
||||
|
||||
```task
|
||||
id: KAIZEN-WP-0013-T01
|
||||
status: done
|
||||
priority: high
|
||||
```
|
||||
|
||||
Review agentic-resources and human-resources intent, scope, workplans, and
|
||||
implementation evidence, plus authoritative budget and resource-control
|
||||
boundaries.
|
||||
|
||||
**Result:** agentic-resources is not intent-only: it implements a tested
|
||||
multi-agent session capture, pattern curation/distribution, measurement, and
|
||||
retrospective loop. Its root SCOPE is stale and it does not yet implement agent
|
||||
assignments, goal allocation, or portfolio budgets. Human-resources remains a
|
||||
planning/workflow-registry scaffold. Fin-hub owns budgets and viability signals;
|
||||
resource-control owns technical resource and cost evidence.
|
||||
|
||||
## Define goals, leadership, and constrained allocation model
|
||||
|
||||
```task
|
||||
id: KAIZEN-WP-0013-T02
|
||||
status: done
|
||||
priority: high
|
||||
```
|
||||
|
||||
Extend the role-agent readiness architecture with explicit organizational
|
||||
goals, leadership/accountability, agent-workforce allocation, and layered
|
||||
financial, resource, token, time, and attention constraints.
|
||||
|
||||
**Result:** the assessment now defines a leadership-to-workforce control spine,
|
||||
StrategicGoal, LeadershipMandate, ResourceEnvelope, RoleAssignment, and
|
||||
AgentInstance separation, layered constraint authority/enforcement, and a
|
||||
goal/budget-correlated pilot path.
|
||||
|
||||
## Reconcile KaizenAgentic ecosystem scope
|
||||
|
||||
```task
|
||||
id: KAIZEN-WP-0013-T03
|
||||
status: done
|
||||
priority: medium
|
||||
```
|
||||
|
||||
Update SCOPE ownership mappings so agentic-resources, human-resources, fin-hub,
|
||||
resource-control, and organization-specific leadership sources are represented
|
||||
without moving their responsibilities into kaizen-agentic.
|
||||
|
||||
**Result:** SCOPE now maps organization leadership, role-engine,
|
||||
agentic-resources, human-resources, fin-hub, resource-control, activity-core,
|
||||
and rein-aharness to distinct ownership concerns.
|
||||
|
||||
## Validate and close out
|
||||
|
||||
```task
|
||||
id: KAIZEN-WP-0013-T04
|
||||
status: done
|
||||
priority: medium
|
||||
```
|
||||
|
||||
Run repository checks, synchronize generated work records and State Hub, record
|
||||
the findings, and close the workplan.
|
||||
|
||||
**Result:** full pytest, `make release-check`, `make agents-validate`, and
|
||||
`git diff --check` pass. State Hub consistency and production UUID registration
|
||||
are handled through the normal closeout path.
|
||||
Loading…
Add table
Add a link
Reference in a new issue