docs: consolidate agent execution and custody
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s
ci / test (push) Successful in 52s

This commit is contained in:
tegwick 2026-08-20 22:43:55 +02:00
parent 6ed5708c21
commit d691135c4a
19 changed files with 372 additions and 64 deletions

View file

@ -0,0 +1,89 @@
---
id: KAIZEN-WP-0014
type: workplan
title: "Repository documentation, execution, and custody consolidation"
domain: agents
repo: kaizen-agentic
status: finished
owner: codex
topic_slug: repository-consolidation
created: "2026-08-20"
updated: "2026-08-20"
---
# Repository documentation, execution, and custody consolidation
Bring the public repository description, capability registration, automated execution
documentation, and remaining pilot evidence custody into agreement with the implemented
Kaizen Agentic architecture.
## Register and baseline the workplan
```task
id: KAIZEN-WP-0014-T01
status: done
priority: high
```
Register this file-first workplan through State Hub consistency tooling and capture the
current repository baseline before making changes.
## Refresh repository-facing documentation
```task
id: KAIZEN-WP-0014-T02
status: done
priority: high
```
Update the README and related repository-facing descriptions to reflect the current
release, packaged agents, CLI surfaces, governance model, and integration boundaries.
## Refresh capability registration metadata
```task
id: KAIZEN-WP-0014-T03
status: done
priority: high
```
Align the capability record and capability index with the agents domain and the current
memory, metrics, scheduling, role, engagement, and downstream-consumer surfaces.
Normalize the repo classification to canonical capability-family tags.
## Document the current scheduled-execution contract
```task
id: KAIZEN-WP-0014-T04
status: done
priority: high
```
Update the activity-core integration material to describe the durable `ops_run` and
rein-aharness execution path while retaining manual execution as a supported fallback.
## Resolve pilot-vault custody
```task
id: KAIZEN-WP-0014-T05
status: done
priority: high
```
Assess the Railiance pilot evidence, define its present classification and owner, select
the appropriate client-side custody target, and establish a safe handoff contract. Do not
move or delete client material until the receiving repository accepts custody.
## Validate and close out
```task
id: KAIZEN-WP-0014-T06
status: done
priority: high
```
Run repository validation, synchronize file state into State Hub, record progress, and
publish the completed work.
Validation completed with repository standards, lint, and the full test suite:
152 passed and 2 existing optional-integration skips.