Model goal-driven agent workforce governance
All checks were successful
ci / test (push) Successful in 3m26s
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

This commit is contained in:
tegwick 2026-08-20 13:03:26 +02:00
parent d1dece7409
commit 6ed5708c21
5 changed files with 373 additions and 51 deletions

View file

@ -52,8 +52,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, llm-connect, State Hub, artifact-store, Helix
Forge, and Custodian discovery
rein-aharness, 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
@ -67,6 +68,8 @@ boundary in `INTENT.md`, not an unfinished runtime hidden in this repository.
- Holding credentials or granting authentication, authorization, decision
rights, or tool permissions
- Live assignment of a person or agent to an organizational role
- Setting organizational goals, granting leadership authority, allocating the
agent workforce, or owning financial/resource budgets
- Owning the complete organizational role catalog; role-engine is the current
definition source, while this repository may consume roles and package
execution-oriented reference Roles
@ -89,6 +92,8 @@ boundary in `INTENT.md`, not an unfinished runtime hidden in this repository.
- Declaring a repo-local agent instance and preparing it for scheduled execution
- Designing a staffed digital Role engagement or mapping an organizational role
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
- Understanding the KaizenAgentic product and agency operating model
@ -101,6 +106,11 @@ boundary in `INTENT.md`, not an unfinished runtime hidden in this repository.
- The need is purely schedule/runtime operation; use activity-core and the
selected rein/harness
- 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
ratified and implemented
- The need is authoritative budget, burn, runway, resource capacity, or
procurement evidence; use fin-hub and resource-control
- The need is identity, credentials, or authorization; use the owning identity,
OpenBao/credential-routing, and policy systems
- The need is repository capability profiling or SCOPE generation at scale; use
@ -124,8 +134,9 @@ boundary in `INTENT.md`, not an unfinished runtime hidden in this repository.
standardized
- **Repository health:** Forgejo CI, release checks, agent validation, and
metadata/workplan conventions are normalized through KAIZEN-WP-0011
- **Open maturity gap:** a canonical role-definition → assignment → agent-instance
contract and an end-to-end role-based pilot remain to be implemented
- **Open maturity gap:** canonical goal/leadership/resource-envelope → role →
assignment → agent-instance contracts and an end-to-end role-based pilot
remain to be implemented
---
@ -133,9 +144,14 @@ boundary in `INTENT.md`, not an unfinished runtime hidden in this repository.
| Concern | Owning system | KaizenAgentic relationship |
|---|---|---|
| Organizational goals and leadership mandates | Accountable organization/engagement control source (`binky-control` for Binky) | Consume goal, outcome, decision-right, and escalation references; never invent strategic authority |
| Organizational role definitions | `role-engine` | Consume stable role references and translate duties/evidence into blueprint inputs |
| Agent workforce inventory, assignment, capacity, and portfolio review | `agentic-resources` (recommended boundary; not yet implemented) | Provide blueprint/metric contracts and receive assignment/performance references |
| Human workforce planning and mixed-team boundaries | `human-resources` | Align compatible vocabulary without sharing human-sensitive records or treating people as compute |
| Agent blueprints and improvement | `kaizen-agentic` | Own |
| Repo-local agent instance | Consuming repository | Define through `.kaizen/` contracts owned jointly with runtime extensions |
| 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 |
| Model/provider abstraction | `llm-connect` | Runtime dependency outside this repository |
@ -144,8 +160,10 @@ boundary in `INTENT.md`, not an unfinished runtime hidden in this repository.
The workspace currently has `role-engine`, not a component named
`role-manager`. Role-engine explicitly excludes live assignment and execution.
An assignment/binding contract therefore needs an explicit owner before roles
can be automated at scale.
Agentic-resources is the best-fit existing assignment/workforce owner, but its
current implemented scope is session improvement and its root SCOPE is stale;
that responsibility needs an explicit boundary decision before roles can be
automated at scale.
---
@ -159,7 +177,12 @@ can be automated at scale.
containing blueprint/protocol/ramp assets; currently not the canonical
organization-wide role catalog
- **Assignment / binding**: a record that selects who or what fills a role in a
specific context; ownership is not yet standardized
specific goal/context under a leadership mandate and resource envelope;
agentic-resources is the recommended owner
- **Leadership mandate**: explicit delegation of goal decomposition, decision
rights, review, and escalation; not implied by an agent or role name
- **Resource envelope**: provenance-bearing financial, token, time, capacity,
and attention constraints delegated to an assignment
- **Instance**: consumer-owned declaration binding a blueprint to target,
cadence, policy lane, tool profile, budget, memory, and metrics
- **Engagement**: a client-scoped lifecycle and custody boundary for staffed work