docs: consolidate agent execution and custody
This commit is contained in:
parent
6ed5708c21
commit
d691135c4a
19 changed files with 372 additions and 64 deletions
|
|
@ -2,7 +2,7 @@
|
|||
# Custodian Brief — kaizen-agentic
|
||||
|
||||
**Domain:** infotech
|
||||
**Last synced:** 2026-08-20 11:03 UTC
|
||||
**Last synced:** 2026-08-20 20:43 UTC
|
||||
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
|
||||
|
||||
## Active Workstreams
|
||||
|
|
|
|||
|
|
@ -11,7 +11,6 @@ repo_classification:
|
|||
- infotech
|
||||
capability_tags:
|
||||
- orchestration
|
||||
- automation
|
||||
- coordination
|
||||
- knowledge
|
||||
- documentation
|
||||
|
|
|
|||
41
README.md
41
README.md
|
|
@ -37,7 +37,7 @@ python3 -m build && make install-local
|
|||
source .venv/bin/activate # Required for each session
|
||||
```
|
||||
|
||||
**From Forgejo PyPI (v1.1.0+):**
|
||||
**From Forgejo PyPI (current release: v1.4.0):**
|
||||
```bash
|
||||
pip install kaizen-agentic \
|
||||
--extra-index-url https://forgejo.coulomb.social/api/packages/coulomb/pypi/simple/
|
||||
|
|
@ -89,7 +89,7 @@ kaizen-agentic memory init sys-medic
|
|||
kaizen-agentic memory brief tdd-workflow
|
||||
|
||||
# Review an agent's accumulated knowledge
|
||||
kaizen-agentic memory show project-management
|
||||
kaizen-agentic memory show project-assistant
|
||||
```
|
||||
|
||||
See [docs/agency-framework.md](docs/agency-framework.md) for the full model.
|
||||
|
|
@ -105,17 +105,22 @@ Read in this order for strategic context:
|
|||
5. [SCOPE.md](SCOPE.md) — repository boundaries and current state
|
||||
6. [history/](history/) — persisted assessments and gap analyses
|
||||
|
||||
Released **v1.1.0** — see [CHANGELOG.md](CHANGELOG.md). Workplans: WP-0001 through WP-0004 completed.
|
||||
Released **v1.4.0** — see [CHANGELOG.md](CHANGELOG.md). Repository state and
|
||||
completed delivery are summarized in [SCOPE.md](SCOPE.md) and
|
||||
[WORK-RECORDS.md](WORK-RECORDS.md).
|
||||
|
||||
Feedback: `kaizen-agentic feedback` · [docs/FEEDBACK.md](docs/FEEDBACK.md)
|
||||
|
||||
## Features
|
||||
|
||||
- **20 Specialized Agents**: Project management, testing, code quality, infrastructure, meta
|
||||
- **20 Specialized Agents**: Planning, testing, code quality, infrastructure, release, and meta-agent craft
|
||||
- **Agency Framework**: Project-scoped agent memory + Coach meta-agent for cross-agent synthesis
|
||||
- **CLI Tool**: Easy agent installation, management, and memory commands (`kaizen-agentic`)
|
||||
- **Metrics and Improvement Loop**: Session evidence, optimizer recommendations, and optional artifact publication
|
||||
- **Roles and Engagements**: Versioned role packages, client-bound engagement records, lifecycle checklists, and custody controls
|
||||
- **Scheduled Preparation**: Repo-local schedules and offline orientation bundles for activity-core/rein-aharness execution
|
||||
- **CLI Tool**: Agent, memory, metrics, protocol, engagement, and schedule commands (`kaizen-agentic`)
|
||||
- **Project Templates**: Pre-configured setups for different project types
|
||||
- **Claude Code Integration**: Seamless integration with Claude Code workflows
|
||||
- **Runtime-neutral Contracts**: Instruction and preparation surfaces usable by governed coding-agent harnesses
|
||||
- **Comprehensive Testing**: Full test coverage with multiple testing strategies
|
||||
|
||||
## Available Agents
|
||||
|
|
@ -124,26 +129,44 @@ Feedback: `kaizen-agentic feedback` · [docs/FEEDBACK.md](docs/FEEDBACK.md)
|
|||
- **keepaTodofile**: Manages TODO.md files following Keep a Todofile format
|
||||
- **keepaChangelog**: Maintains CHANGELOG.md files following Keep a Changelog format
|
||||
- **keepaContributingfile**: Creates and updates CONTRIBUTING.md files
|
||||
- **project-management**: General project management and coordination
|
||||
- **project-assistant**: General project planning and coordination
|
||||
- **priority-evaluation**: Evaluates and orders competing work
|
||||
- **requirements-engineering**: Requirements analysis and documentation
|
||||
- **scope-analyst**: Maintains explicit product and repository boundaries
|
||||
- **releaseManager**: Coordinates release readiness and delivery
|
||||
|
||||
### Development Process
|
||||
- **tdd-workflow**: Test-driven development workflow guidance
|
||||
- **requirements-engineering**: Requirements analysis and documentation
|
||||
- **test-maintenance**: Test suite maintenance and optimization
|
||||
- **testing-efficiency**: Improves test feedback speed and signal quality
|
||||
|
||||
### Code Quality
|
||||
- **code-refactoring**: Code improvement and refactoring guidance
|
||||
- **optimization**: Agent definition optimization and improvement
|
||||
- **datamodel-optimization**: Data model design and optimization
|
||||
- **tooling-optimization**: Improves effective use of repository tooling
|
||||
|
||||
### Infrastructure
|
||||
- **setupRepository**: Repository initialization and standards compliance
|
||||
- **claude-documentation**: Claude Code configuration and documentation
|
||||
- **tooling-optimization**: Repository tooling usage optimization
|
||||
- **sys-medic**: Infrastructure health monitoring and diagnostics
|
||||
|
||||
### Meta
|
||||
- **coach**: Coaching meta-agent — reads all project agent memories, synthesises cross-agent briefs, and orients incoming agents
|
||||
- **wisdom-encouragement**: Encourages reflective, evidence-backed improvement
|
||||
|
||||
## Automated execution boundary
|
||||
|
||||
Kaizen Agentic defines agent craft, validates repo-local schedules, and prepares
|
||||
offline execution bundles. In the current unattended path, **activity-core**
|
||||
creates durable, claimable `ops_run` work and **rein-aharness** resolves policy,
|
||||
credentials, runtime profile, model, and sandbox before executing the bounded
|
||||
agent session. State Hub supplies roster and coordination evidence.
|
||||
|
||||
Manual execution remains supported. Kaizen Agentic itself does not own cron,
|
||||
the durable work queue, inference, credentials, or runtime authorization. See
|
||||
[Integration Patterns](docs/INTEGRATION_PATTERNS.md) and
|
||||
[ADR-005](docs/adr/ADR-005-scheduled-agent-execution.md).
|
||||
|
||||
[View complete agent list](docs/AGENT_DISTRIBUTION.md#agent-categories)
|
||||
|
||||
|
|
|
|||
|
|
@ -21,6 +21,7 @@
|
|||
| workplan | KAIZEN-WP-0011 | finished | — | workplans/KAIZEN-WP-0011-repository-health-normalization.md |
|
||||
| workplan | KAIZEN-WP-0012 | finished | — | workplans/KAIZEN-WP-0012-scope-intent-role-automation-assessment.md |
|
||||
| workplan | KAIZEN-WP-0013 | finished | — | workplans/KAIZEN-WP-0013-agent-workforce-goal-budget-governance.md |
|
||||
| workplan | KAIZEN-WP-0014 | finished | — | workplans/KAIZEN-WP-0014-repository-consolidation.md |
|
||||
| task | T01 | done | — | workplans/KAIZEN-WP-0003-measurement-loop.md |
|
||||
| task | T02 | done | — | workplans/KAIZEN-WP-0003-measurement-loop.md |
|
||||
| task | T03 | done | — | workplans/KAIZEN-WP-0003-measurement-loop.md |
|
||||
|
|
@ -143,3 +144,9 @@
|
|||
| task | KAIZEN-WP-0013-T02 | done | — | workplans/KAIZEN-WP-0013-agent-workforce-goal-budget-governance.md |
|
||||
| task | KAIZEN-WP-0013-T03 | done | — | workplans/KAIZEN-WP-0013-agent-workforce-goal-budget-governance.md |
|
||||
| task | KAIZEN-WP-0013-T04 | done | — | workplans/KAIZEN-WP-0013-agent-workforce-goal-budget-governance.md |
|
||||
| task | KAIZEN-WP-0014-T01 | done | — | workplans/KAIZEN-WP-0014-repository-consolidation.md |
|
||||
| task | KAIZEN-WP-0014-T02 | done | — | workplans/KAIZEN-WP-0014-repository-consolidation.md |
|
||||
| task | KAIZEN-WP-0014-T03 | done | — | workplans/KAIZEN-WP-0014-repository-consolidation.md |
|
||||
| task | KAIZEN-WP-0014-T04 | done | — | workplans/KAIZEN-WP-0014-repository-consolidation.md |
|
||||
| task | KAIZEN-WP-0014-T05 | done | — | workplans/KAIZEN-WP-0014-repository-consolidation.md |
|
||||
| task | KAIZEN-WP-0014-T06 | done | — | workplans/KAIZEN-WP-0014-repository-consolidation.md |
|
||||
|
|
|
|||
|
|
@ -119,8 +119,10 @@ kaizen-agentic schedule prepare coach # markdown bundle
|
|||
kaizen-agentic schedule prepare optimization --format json
|
||||
```
|
||||
|
||||
activity-core fires the schedule and creates a task per (repo, agent); the task
|
||||
runs `schedule prepare`. kaizen-agentic does not run cron or invoke Claude.
|
||||
activity-core fires the schedule and creates durable `ops_run` work per
|
||||
(repo, agent). rein-aharness claims that work and runs the governed
|
||||
`agent-session`, including `schedule prepare`. kaizen-agentic does not run cron,
|
||||
own the queue, resolve credentials, or invoke an LLM.
|
||||
|
||||
### Forward-deployed engagements (WP-0009 / DEC-FDA-001)
|
||||
```bash
|
||||
|
|
|
|||
|
|
@ -56,9 +56,9 @@ invoke kaizen-agentic CLI commands.
|
|||
|
||||
**kaizen-agentic maintainer checklist:**
|
||||
|
||||
- [ ] Three definition files committed under `docs/integrations/activity-definitions/`
|
||||
- [ ] activity-core PR or issue opened to register definitions
|
||||
- [ ] Smoke test commands documented below pass on a pilot repo
|
||||
- [x] Three definition files committed under `docs/integrations/activity-definitions/`
|
||||
- [x] activity-core handoff completed for the resolver and pilot definitions
|
||||
- [x] Smoke test commands documented below passed on the pilot roster
|
||||
|
||||
**Smoke test (manual):**
|
||||
|
||||
|
|
@ -71,7 +71,7 @@ kaizen-agentic metrics optimize
|
|||
test -f .kaizen/metrics/optimizer/analysis.json && echo OK
|
||||
```
|
||||
|
||||
**Boundary:** kaizen-agentic does not run Temporal schedules.
|
||||
**Boundary:** kaizen-agentic does not run Temporal schedules or own durable work.
|
||||
|
||||
### Scheduled agent execution (WP-0006, ADR-005)
|
||||
|
||||
|
|
@ -109,8 +109,26 @@ kaizen-agentic schedule validate && kaizen-agentic schedule list
|
|||
- [discover-kaizen-scheduled-repos.md](integrations/discover-kaizen-scheduled-repos.md) — resolver spec
|
||||
- [kaizen-schedule-prepared-event.md](integrations/kaizen-schedule-prepared-event.md) — event payload
|
||||
|
||||
**Boundary:** kaizen-agentic declares and prepares; activity-core schedules;
|
||||
state-hub owns the roster.
|
||||
### Current automated runtime
|
||||
|
||||
The original WP-0006 resolver and manual prepare smoke established the supplier
|
||||
contract. Current unattended execution composes it as follows:
|
||||
|
||||
| Stage | Owner | Contract |
|
||||
|-------|-------|----------|
|
||||
| Schedule/event and eligibility | activity-core | Temporal definition/rule plus repo/agent context |
|
||||
| Durable work | activity-core | Unique idempotency key, `ops_run` state, lease, retry, result |
|
||||
| Claim and execution | rein-aharness | Claim loop, `agent-session` approach, policy/profile/runtime resolution |
|
||||
| Agent orientation | kaizen-agentic | `schedule prepare <agent>` offline bundle |
|
||||
| Coordination evidence | State Hub | Roster, workplan/progress references; never prompts or secrets |
|
||||
| Improvement evidence | kaizen-agentic / artifact-store | Project metrics and optional durable artifacts |
|
||||
|
||||
Manual invocation remains supported for smoke tests and operator-controlled
|
||||
work. The automated path should keep prompts, secrets, and raw model output out
|
||||
of `ops_run` and State Hub records.
|
||||
|
||||
**Boundary:** kaizen-agentic declares and prepares; activity-core schedules and
|
||||
queues; rein-aharness executes; State Hub owns the roster and coordination view.
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -37,14 +37,36 @@ end-to-end flow:
|
|||
```
|
||||
activity-core cron
|
||||
→ context resolver (roster ∩ repos with schedule.yml)
|
||||
→ task per (repo, agent)
|
||||
→ coding-agent session runs `kaizen-agentic schedule prepare <agent>`
|
||||
→ durable work per (repo, agent)
|
||||
→ governed runner executes `kaizen-agentic schedule prepare <agent>`
|
||||
→ session executes the agent instructions in that repo
|
||||
```
|
||||
|
||||
kaizen-agentic's responsibilities are exactly two: **declare** the schedule
|
||||
(`.kaizen/schedule.yml`) and **prepare** an orientation bundle for a run. It
|
||||
does **not** fire cron, create tasks, or invoke Claude.
|
||||
does **not** fire cron, own the durable work queue, or invoke an LLM.
|
||||
|
||||
### Current runtime realization (2026-08-20)
|
||||
|
||||
The initial contract above remains valid, but the generic word “task” now has a
|
||||
specific durable implementation:
|
||||
|
||||
```
|
||||
activity-core Temporal schedule/event
|
||||
→ rule evaluation and eligibility
|
||||
→ unique, idempotent ops_run with lease/retry state
|
||||
→ rein-aharness claim loop
|
||||
→ agent-session approach and governed runtime/profile resolution
|
||||
→ kaizen-agentic schedule prepare <agent>
|
||||
→ bounded coding-agent session
|
||||
→ ops_run result + State Hub progress + .kaizen metrics/artifact evidence
|
||||
```
|
||||
|
||||
`activity-core` owns schedule and durable work state. `rein-aharness` owns
|
||||
claiming, execution policy, credential routing, runtime selection, and bounded
|
||||
session operation. Kaizen Agentic continues to own declaration, agent craft,
|
||||
preparation, and improvement evidence. A human-started coding-agent session
|
||||
remains a supported execution mode and reference smoke path.
|
||||
|
||||
### 1. Schedule manifest — `.kaizen/schedule.yml`
|
||||
|
||||
|
|
@ -123,10 +145,13 @@ kaizen-agentic schedule prepare <agent> [--target PATH] [--format markdown|json]
|
|||
|
||||
## Boundaries
|
||||
|
||||
- **No scheduling code** in kaizen-agentic. Cron and task creation belong to
|
||||
activity-core; the roster query belongs to state-hub.
|
||||
- **No scheduling or durable-queue code** in kaizen-agentic. Temporal schedules,
|
||||
rule evaluation, and `ops_run` state belong to activity-core; the roster query
|
||||
belongs to State Hub.
|
||||
- **No LLM invocation.** `prepare` produces a runner-agnostic bundle; a human or
|
||||
automated coding-agent session executes it.
|
||||
rein-aharness-governed coding-agent session executes it.
|
||||
- **No runtime authority or credentials.** Those remain with rein-aharness and
|
||||
the ecosystem credential/authorization owners.
|
||||
- **State-hub schema changes** (roster opt-in flag) are designed here but
|
||||
implemented in `the-custodian` (repo boundary).
|
||||
|
||||
|
|
@ -134,7 +159,7 @@ kaizen-agentic schedule prepare <agent> [--target PATH] [--format markdown|json]
|
|||
|
||||
- Operators declare per-repo schedules and a fleet roster without tribal
|
||||
knowledge.
|
||||
- activity-core can fire recurring tasks referencing `schedule prepare`.
|
||||
- activity-core can fire recurring durable work referencing `schedule prepare`.
|
||||
- A scheduled session opens with full orientation (prompt + memory + metrics).
|
||||
- The existing `weekly-metrics-optimize` definition (ADR-004 / WP-0004) remains
|
||||
complementary; an `optimization` agent run may chain `schedule prepare
|
||||
|
|
|
|||
|
|
@ -127,16 +127,21 @@ should amend this ADR (or a successor), not re-open DEC-FDA-001 silently.
|
|||
|
||||
### Negative / trade-offs
|
||||
|
||||
- Pilot vault currently sits in the supplier repo (`engagements/pilots/`) — must
|
||||
still be treated as client confidential; export to client repo is recommended
|
||||
before multi-tenant growth
|
||||
- activity-core automation for host duties is optional Phase 3 (manual prepare OK)
|
||||
- Pilot vault currently sits in the supplier repo (`engagements/pilots/`) under
|
||||
transitional custody. The Railiance01 receiving authority is
|
||||
`railiance-infra`; transfer requires explicit receiver acceptance before the
|
||||
supplier copy is removed or reduced to a pointer.
|
||||
- Manual preparation remains supported. Unattended host duties require an
|
||||
engagement-specific activity-core definition and a rein-aharness execution
|
||||
profile in addition to the generic `ops_run`/`agent-session` path.
|
||||
- Kai is not a payment processor; EUR path remains future work
|
||||
|
||||
### Follow-ups
|
||||
|
||||
- Export pilot vault to client-owned path when railiance ops repo is ready
|
||||
- Optional activity-core ActivityDefinitions for daily host-operator prepare
|
||||
- Complete the proposed pilot transfer to the client-owned `railiance-infra`
|
||||
evidence path and record its accepted commit
|
||||
- Register engagement-specific activity-core definitions and rein-aharness
|
||||
profile for daily host-operator preparation when unattended operation is desired
|
||||
- EUR commercial FX after 2–3 engagement calibration cycles
|
||||
|
||||
## Pilot evidence
|
||||
|
|
|
|||
|
|
@ -158,7 +158,7 @@ kaizen-agentic memory brief tdd-workflow
|
|||
# → paste output into Claude with agent-coach.md loaded
|
||||
|
||||
# Review accumulated memory for a specific agent
|
||||
kaizen-agentic memory show project-management
|
||||
kaizen-agentic memory show project-assistant
|
||||
```
|
||||
|
||||
---
|
||||
|
|
@ -242,7 +242,7 @@ All agents that do session-bound project work have `memory: enabled` in their fr
|
|||
|
||||
| Agent | Category | Notes |
|
||||
|-------|----------|-------|
|
||||
| project-management | process | Reference implementation of the session protocol pattern |
|
||||
| project-assistant | process | Reference implementation of the session protocol pattern |
|
||||
| tdd-workflow | testing | |
|
||||
| requirements-engineering | process | |
|
||||
| scope-analyst | process | |
|
||||
|
|
@ -331,8 +331,10 @@ kaizen-agentic schedule prepare coach # orientation bundle for a scheduled run
|
|||
|
||||
`schedule prepare <agent>` bundles the agent prompt, project memory, metrics
|
||||
summary, and repo pointers — offline, no State Hub required. kaizen-agentic does
|
||||
**not** run cron or invoke Claude; activity-core fires the schedule and a
|
||||
coding-agent session executes the prepared bundle.
|
||||
**not** run cron, own durable work, or invoke an LLM. activity-core fires the
|
||||
schedule and creates `ops_run` work; rein-aharness claims it and executes the
|
||||
prepared bundle through a governed `agent-session`. Manual sessions remain a
|
||||
supported fallback.
|
||||
|
||||
Schema: [integrations/schedule-schema.md](integrations/schedule-schema.md).
|
||||
|
||||
|
|
|
|||
|
|
@ -1,9 +1,15 @@
|
|||
# activity-core Handoff — Scheduled Agent Execution (WP-0006)
|
||||
|
||||
> **Historical supplier handoff, completed for the initial resolver/pilot path.**
|
||||
> The current production composition is activity-core durable `ops_run` work
|
||||
> claimed by rein-aharness through its generic `agent-session` approach. The
|
||||
> resolver and preparation contracts below remain compatible inputs.
|
||||
|
||||
Coordination checklist for the **activity-core** team to enable kaizen scheduled
|
||||
agent runs. kaizen-agentic owns the schedule contract, the prepare CLI, and the
|
||||
ActivityDefinition **drafts**; activity-core owns the resolver, the schedule
|
||||
firing, and task creation (repo boundary, ADR-005).
|
||||
ActivityDefinition **drafts**; activity-core owns the resolver, schedule firing,
|
||||
and durable work creation (repo boundary, ADR-005); rein-aharness owns governed
|
||||
execution.
|
||||
|
||||
Open this as an activity-core issue/PR titled *"Enable kaizen scheduled agent
|
||||
execution (WP-0006)"* and track the boxes there.
|
||||
|
|
@ -56,7 +62,7 @@ in kaizen-agentic drafts) when engagement moves beyond coulomb-loop bootstrap co
|
|||
- [ ] Optional: add `kaizen_schedule_enabled` repo flag + `GET /repos/` filter
|
||||
(v2 pre-filter; the repo file remains the source of truth).
|
||||
|
||||
## Smoke test (manual, runner-agnostic)
|
||||
## Smoke test (manual reference path)
|
||||
|
||||
```bash
|
||||
cd /path/to/pilot-repo
|
||||
|
|
@ -68,6 +74,9 @@ kaizen-agentic schedule prepare coach # non-empty orientation bundle
|
|||
|
||||
Then in activity-core: run the resolver (dry-run) and confirm one
|
||||
`scheduled_run` per enabled `(repo, agent)` with a correct `prepare_command`.
|
||||
For unattended operation, confirm the resulting `ops_run` is claimable and the
|
||||
rein-aharness worker selects the `agent-session` approach before enabling the
|
||||
schedule broadly.
|
||||
|
||||
## Pilot roster
|
||||
|
||||
|
|
|
|||
|
|
@ -87,7 +87,10 @@ kaizen-agentic engagement close-session eng-... \
|
|||
|
||||
### 7. Operate cadence
|
||||
|
||||
- Enable entries in engagement `schedule.yml` (manual prepare until activity-core)
|
||||
- Enable entries in engagement `schedule.yml`; they declare intent but do not
|
||||
activate unattended work by themselves
|
||||
- Continue manual prepare until an engagement-specific activity-core definition
|
||||
and rein-aharness profile have passed a bounded smoke test
|
||||
- Daily: health + load; weekly: OS/security pass (privileged changes still gated)
|
||||
|
||||
### 8. Ramp-down (when ending)
|
||||
|
|
@ -116,7 +119,7 @@ Friction and resolutions from `eng-coulomb-railiance01-ho-001` / KAIZEN-WP-0009.
|
|||
| `k3s kubectl` ServiceUnavailable under memory pressure | Record as finding; avoid hammering API; re-sample after capacity relief |
|
||||
| Nested `.kaizen/metrics` under engagement is correct for custody | Root `.gitignore` `.kaizen/metrics/` only ignores repo-root metrics; pilot metrics are commit-able |
|
||||
| Privileged work tempting on Critical host | RU-08 = **proposal dry-run only** until human approval table filled |
|
||||
| Pilot vault in supplier repo | Treat as client confidential; export to client ops repo before multi-tenant scale |
|
||||
| Pilot vault in supplier repo | Treat as client confidential; target `railiance-infra` for Railiance01 and require receiver acceptance before source cleanup |
|
||||
| activity-core not required for Phase 1 | Manual `prepare` + `close-session`; schedule.yml documents intent |
|
||||
| Kai charges felt real only after close-session | Always close-session after live duties; quote alone is not spend |
|
||||
| High load makes remote `du`/`apt` slow | Prefer short command batches; timeout ≥60s for full assessments |
|
||||
|
|
@ -152,14 +155,19 @@ ssh railiance01 "sudo ufw allow from <PUBLIC_IP> to any port 6443 proto tcp comm
|
|||
|
||||
---
|
||||
|
||||
## Optional activity-core wiring (Phase 3)
|
||||
## Optional unattended wiring (Phase 3)
|
||||
|
||||
Not required for operate. When ready:
|
||||
|
||||
1. Customer or engagement repo owns ActivityDefinition copies that shell out to
|
||||
`kaizen-agentic engagement prepare <id>` then start a coding-agent session
|
||||
2. Resolver points at engagement id / host Target (new work — not WP-0009)
|
||||
3. Keep privilege gates in the agent definition regardless of cron fire
|
||||
1. Customer or engagement repo owns the ActivityDefinition that identifies the
|
||||
engagement and emits idempotent, claimable `ops_run` work in activity-core.
|
||||
2. The run carries `agent-session` approach metadata and a compatible
|
||||
rein-aharness profile reference; it does not carry secrets or raw prompts.
|
||||
3. rein-aharness claims the run, resolves credentials and policy, and executes
|
||||
`kaizen-agentic engagement prepare <id>` inside the bounded session.
|
||||
4. Completion links the `ops_run`, engagement report, metrics, and State Hub
|
||||
progress without duplicating confidential content into coordination records.
|
||||
5. Keep privilege gates in the agent definition regardless of schedule fire.
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
52
engagements/pilots/eng-coulomb-railiance01-ho-001/CUSTODY.md
Normal file
52
engagements/pilots/eng-coulomb-railiance01-ho-001/CUSTODY.md
Normal file
|
|
@ -0,0 +1,52 @@
|
|||
# Custody — eng-coulomb-railiance01-ho-001
|
||||
|
||||
## Decision
|
||||
|
||||
The engagement record and vault are owned by the `coulomb` client and classified
|
||||
`client_confidential`. Their present location in `kaizen-agentic` is
|
||||
transitional supplier custody, not supplier ownership.
|
||||
|
||||
The selected receiving authority is:
|
||||
|
||||
```text
|
||||
repository: railiance-infra
|
||||
path: docs/evidence/resource-hosteurope-railiance01/engagements/
|
||||
eng-coulomb-railiance01-ho-001/
|
||||
```
|
||||
|
||||
`railiance-infra` is the canonical S1 owner for Railiance01 inventory,
|
||||
hardening, access, and host-operational evidence, and already maintains the
|
||||
`resource-hosteurope-railiance01` evidence interface. `reef-railiance` is not
|
||||
the target: it owns grouped reef identity, topology, and bindings, not detailed
|
||||
host-operation records.
|
||||
|
||||
## Current data classes
|
||||
|
||||
| Tree | Classification | Intended custody |
|
||||
|------|----------------|------------------|
|
||||
| `ENGAGEMENT.yaml`, request, schedule, bound definition | client operational record | receiving repo |
|
||||
| `vault/`, reports, checklists, access plan | client confidential | receiving repo |
|
||||
| engagement-local `.kaizen/metrics/` | client execution evidence | receiving repo |
|
||||
| `commercial/` | client settlement metadata | receiving repo or financial authority |
|
||||
| reusable role craft under `roles/host-operator/` | supplier craft | remains in kaizen-agentic |
|
||||
|
||||
The committed access plan contains operational routing and host identity, but
|
||||
no credential value. Secrets, private keys, tokens, and passwords must never be
|
||||
added to this tree or to a transfer package.
|
||||
|
||||
## Transfer gate
|
||||
|
||||
The supplier copy remains the source of truth until all of these are true:
|
||||
|
||||
1. The receiving repository accepts the path and confidentiality policy.
|
||||
2. The complete engagement tree is copied with history or an attributable
|
||||
import commit, and the receiver validates its manifest.
|
||||
3. The receiver records the accepted commit and acceptance date in
|
||||
`vault/handoff/custody-transfer.yaml`.
|
||||
4. Scheduled execution and access references are changed to the receiving path.
|
||||
5. Only then may this supplier copy be reduced to a non-confidential pointer or
|
||||
removed in a separately reviewed, recoverable change.
|
||||
|
||||
Until acceptance, do not add new sensitive operational evidence here unless it
|
||||
is necessary to maintain the active engagement. Do not claim that a handoff
|
||||
pack created inside this repository has itself transferred custody.
|
||||
|
|
@ -26,6 +26,15 @@ spec:
|
|||
vault:
|
||||
root: vault/
|
||||
memory: vault/memory.md
|
||||
custody:
|
||||
owner: coulomb
|
||||
classification: client_confidential
|
||||
current_repo: kaizen-agentic
|
||||
current_state: transitional_supplier_custody
|
||||
target_repo: railiance-infra
|
||||
target_path: docs/evidence/resource-hosteurope-railiance01/engagements/eng-coulomb-railiance01-ho-001/
|
||||
transfer_status: proposed
|
||||
transfer_manifest: vault/handoff/custody-transfer.yaml
|
||||
schedule:
|
||||
path: schedule.yml
|
||||
checklists:
|
||||
|
|
|
|||
|
|
@ -1,5 +1,6 @@
|
|||
# Duty cadence for eng-coulomb-railiance01-ho-001
|
||||
# activity-core wiring optional (Phase 3); manual prepare is enough for Phase 1
|
||||
# Entries declare intent. Manual prepare remains active until an engagement-specific
|
||||
# activity-core definition and rein-aharness profile are registered and smoke-tested.
|
||||
engagement_id: eng-coulomb-railiance01-ho-001
|
||||
timezone: Europe/Berlin
|
||||
entries:
|
||||
|
|
@ -12,7 +13,7 @@ entries:
|
|||
cadence: daily
|
||||
cron: "0 9 * * 1-5"
|
||||
enabled: true
|
||||
notes: "Enabled after T10 ramp-up exit 2026-07-16; manual prepare until activity-core wired"
|
||||
notes: "Declared after T10 ramp-up exit 2026-07-16; manual prepare until activity-core/rein-aharness wiring is accepted"
|
||||
|
||||
- id: weekly-os-security
|
||||
agent: host-operator
|
||||
|
|
@ -22,4 +23,4 @@ entries:
|
|||
cadence: weekly
|
||||
cron: "0 10 * * 1"
|
||||
enabled: true
|
||||
notes: "Privileged upgrades remain human-gated even when enabled"
|
||||
notes: "Privileged upgrades remain human-gated under manual or automated execution"
|
||||
|
|
|
|||
|
|
@ -1,6 +1,7 @@
|
|||
# Handoff pack — eng-coulomb-railiance01-ho-001
|
||||
|
||||
Filled during **ramp-down** (RD-02).
|
||||
Prepared during **ramp-down** (RD-02). The custody target was selected on
|
||||
2026-08-20, but the receiving repository has not yet accepted the transfer.
|
||||
|
||||
## Contents (when complete)
|
||||
|
||||
|
|
@ -10,4 +11,18 @@ Filled during **ramp-down** (RD-02).
|
|||
- Deferred patches and reboot debt
|
||||
- Contacts and access revocation status
|
||||
|
||||
_Status: not started (engagement not in ramp_down)._
|
||||
## Custody
|
||||
|
||||
- Owner: `coulomb`
|
||||
- Classification: `client_confidential`
|
||||
- Current location: transitional supplier custody in `kaizen-agentic`
|
||||
- Receiving authority: `railiance-infra`
|
||||
- Proposed path:
|
||||
`docs/evidence/resource-hosteurope-railiance01/engagements/eng-coulomb-railiance01-ho-001/`
|
||||
- Transfer record: `custody-transfer.yaml`
|
||||
|
||||
The complete engagement tree, rather than only this handoff directory, must be
|
||||
transferred because metrics, reports, approvals, and commercial metadata are
|
||||
all client records. The source is retained until explicit receiver acceptance.
|
||||
|
||||
_Status: handoff target selected; transfer proposed; engagement still operating._
|
||||
|
|
|
|||
|
|
@ -0,0 +1,27 @@
|
|||
apiVersion: kaizen.agentic/v1
|
||||
kind: EngagementCustodyTransfer
|
||||
metadata:
|
||||
engagement_id: eng-coulomb-railiance01-ho-001
|
||||
prepared: '2026-08-20'
|
||||
spec:
|
||||
owner: coulomb
|
||||
classification: client_confidential
|
||||
source:
|
||||
repo: kaizen-agentic
|
||||
path: engagements/pilots/eng-coulomb-railiance01-ho-001/
|
||||
custody: transitional_supplier
|
||||
destination:
|
||||
repo: railiance-infra
|
||||
path: docs/evidence/resource-hosteurope-railiance01/engagements/eng-coulomb-railiance01-ho-001/
|
||||
reason: canonical S1 authority for Railiance01 host-operational evidence
|
||||
transfer_scope: complete_engagement_tree
|
||||
exclusions:
|
||||
- roles/host-operator/
|
||||
acceptance:
|
||||
status: proposed
|
||||
accepted_commit: null
|
||||
accepted_by: null
|
||||
accepted_at: null
|
||||
source_disposition:
|
||||
status: retained_until_acceptance
|
||||
action_after_acceptance: replace_with_non_confidential_pointer_after_review
|
||||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
id: capability.agents.kaizen-framework
|
||||
name: Kaizen Agentic Framework
|
||||
summary: AI agency framework providing 20 specialized deployable agent instruction sets plus persistent,
|
||||
project-scoped memory and cross-agent coordination via a Coach meta-agent.
|
||||
summary: AI agency framework providing 20 deployable agent instruction sets, project memory,
|
||||
metrics, role and engagement contracts, and scheduled preparation for governed execution.
|
||||
owner: kaizen-agentic
|
||||
status: draft
|
||||
domain: agents
|
||||
|
|
@ -10,13 +10,16 @@ tags:
|
|||
- agents
|
||||
- memory
|
||||
- coordination
|
||||
- metrics
|
||||
- scheduling
|
||||
- engagements
|
||||
maturity:
|
||||
discovery:
|
||||
current: D3
|
||||
target: D5
|
||||
confidence: medium
|
||||
rationale: README documents the agent library, the agency framework (persistent memory, Coach meta-agent
|
||||
synthesising fleet-wide patterns), and a versioned release (v1.4.0); has .forgejo/workflows CI.
|
||||
rationale: README, SCOPE, ADRs, and integration contracts document the agent library, memory,
|
||||
metrics, scheduling, role and engagement surfaces, and versioned release v1.4.0; CI is present.
|
||||
availability:
|
||||
current: A2
|
||||
target: A3
|
||||
|
|
@ -32,6 +35,9 @@ external_evidence:
|
|||
- 20 specialized agent instruction sets
|
||||
- persistent project-scoped agent memory
|
||||
- Coach meta-agent for fleet-wide pattern synthesis
|
||||
- project metrics and optimizer workflow
|
||||
- role packages and file-backed client engagements
|
||||
- schedule validation and offline execution-bundle preparation
|
||||
broken_expectations: []
|
||||
out_of_scope_expectations: []
|
||||
reliability:
|
||||
|
|
@ -39,14 +45,17 @@ external_evidence:
|
|||
confidence: low
|
||||
basis: consumer_quality_signals
|
||||
known_reliability_risks:
|
||||
- no external reuse evidence yet outside the originating project
|
||||
- downstream execution depends on activity-core and rein-aharness contracts outside this repository
|
||||
discovery:
|
||||
intent: Let agents arrive in a project already informed and improve over time through persistent, project-scoped
|
||||
memory and fleet-wide coordination via a Coach meta-agent.
|
||||
intent: Let agents arrive informed, work within explicit roles and engagement boundaries,
|
||||
and improve through project memory, execution evidence, and governed scheduling contracts.
|
||||
includes:
|
||||
- 20 specialized agent instruction sets
|
||||
- persistent memory and coordination framework
|
||||
- Coach meta-agent pattern synthesis
|
||||
- project execution metrics and optimizer artifacts
|
||||
- role packages and forward-deployed engagement lifecycle helpers
|
||||
- repo-local schedule manifests and offline preparation bundles
|
||||
excludes:
|
||||
- the underlying LLM inference itself (agents are instruction sets, not a model)
|
||||
assumptions: []
|
||||
|
|
@ -57,11 +66,13 @@ availability:
|
|||
target_level: A3
|
||||
current_artifacts:
|
||||
- Python package (`kaizen-agentic`) v1.4.0
|
||||
- CLI (`agents-install-cli`)
|
||||
- CLI (`kaizen-agentic`)
|
||||
- versioned role, engagement, metrics, protocol, and schedule contracts
|
||||
target_artifacts: []
|
||||
consumption_modes:
|
||||
- cli
|
||||
- library import
|
||||
- file contracts
|
||||
relations:
|
||||
depends_on: []
|
||||
supports: []
|
||||
|
|
@ -78,10 +89,12 @@ evidence:
|
|||
consumer_guidance:
|
||||
recommended_for:
|
||||
- projects wanting a deployable, memory-persistent agent fleet with cross-agent coordination
|
||||
- governed runtimes needing offline agent orientation and schedule preparation contracts
|
||||
not_recommended_for:
|
||||
- needs for a single stateless agent (framework overhead not justified)
|
||||
known_limitations:
|
||||
- no cross-project reuse evidence recorded yet
|
||||
- this package prepares work but does not schedule, authorize, or invoke an LLM
|
||||
- production reliability telemetry is not yet sufficient for a higher reliability rating
|
||||
promotion_history: []
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
version: 1
|
||||
updated: '2026-07-06'
|
||||
domain: helix_forge
|
||||
updated: '2026-08-20'
|
||||
domain: agents
|
||||
capabilities:
|
||||
- id: capability.agents.kaizen-framework
|
||||
name: Kaizen Agentic Framework
|
||||
summary: AI agency framework providing 20 specialized deployable agent instruction sets plus persistent,
|
||||
project-scoped memory and cross-agent coordination via a Coach meta-agent.
|
||||
summary: AI agency framework providing 20 deployable agent instruction sets, project memory,
|
||||
metrics, role and engagement contracts, and scheduled preparation for governed execution.
|
||||
vector: D3 / A2 / C1 / R0
|
||||
domain: agents
|
||||
status: draft
|
||||
|
|
@ -15,6 +15,10 @@ capabilities:
|
|||
- agents
|
||||
- memory
|
||||
- coordination
|
||||
- metrics
|
||||
- scheduling
|
||||
- engagements
|
||||
consumption_modes:
|
||||
- cli
|
||||
- library import
|
||||
- file contracts
|
||||
|
|
|
|||
89
workplans/KAIZEN-WP-0014-repository-consolidation.md
Normal file
89
workplans/KAIZEN-WP-0014-repository-consolidation.md
Normal 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.
|
||||
Loading…
Add table
Add a link
Reference in a new issue