Files
cp1-agents/individual-agents/ALZ-F01: Discovery Workflow Agent/.agents/PLAN.md
Jonathan Boniface 416c66ced4
All checks were successful
check agents / check (push) Successful in 10s
Add CP1 Discovery agents in both patterns
ALZ-F01 Discovery as a sub-agent orchestrator (sub-agents/) and as eight
individual declarative agents (individual-agents/), with their KAB workflow
exports. Shared check, render and import scripts, the alz-discovery-sample
MCP server, the crucible-kab-dev deploy profile, deployment docs, platform
issue reports and the source material. Agent steps time out at 20 minutes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 18:25:57 +00:00

28 lines
2.9 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Implementation plan: individual agents, ALZ-F01 Discovery
For coding agents. Update the status in the same change as the work.
Status values: `done`, `blocked (<on whom>)`, `todo`.
| # | Step | Verified by | Status |
|---|---|---|---|
| 1 | Generate the eight agent folders from the v1.1 stories, cp4-agents style, without `alz-run` or the write tools | `scripts/check_agents.py` (cp4's rules) 0 problems; the runtime parses every `agent.yaml`; every schema is valid | done |
| 2 | Eval cases per agent, Meridian estate, `timeout: 330` | `python -m kyndryl_agent_runtime.eval --validate` | done (not yet run live) |
| 3 | Workflow export: 8 steps, `from_steps` hand-offs, critic approval | `build_workflow.py` asserts the fields on both sides; same keys as cp4's export | done |
| 4 | Deploy profile and kustomize render | `render_k8s.py` + `kustomize build` (3 objects each) | done |
| 5 | Docs: README, user guides, ADRs 0001–0010; agent context | Review | done |
| 6 | Fix the MCP gateway tenant mapping so MCP servers can be registered | Registration saves | blocked (KAB platform admin) |
| 7 | Build and push the eight images | `podman push` | done (2026-10-29, on the pinned runtime 0.35.7) |
| 8 | Create the eight agents in KAB; store each `MCP_AGENT_API_KEY` | Secrets exist; no file holds a key | blocked (step 6) |
| 9 | `kubectl diff -k`, then `apply -k`, for each agent | Pods ready; agent cards served | done (2026-10-29): all 8 Ready, cards served; requests fail at startup until step 8 |
| 9a | Uploads and artifacts (ADR 0011): `source_documents` / `reference_documents` on the planner and inventory (0.2.0, regenerated), front steps in `build_workflow.py`, `scripts/kab_import_workflow.py` | cp4 check 0 problems; runtime parse; eval validation; builder asserts wiring | done (2026-10-29) |
| 9b | Move into `kab-agents-and-workflows/cp1-agents` (`individual-agents/<Feature>/`); shared scripts, MCP server and deploy profile at the repository root; `repo: cp1-agents-individual` kept per agent (Deployment selector) | `check_agents.py` 0 problems; `build_workflow.py` output identical; `kubectl diff -k` empty for all 8 | done (2026-10-29) |
| 9c | Timeouts: every workflow step 20 minutes (`AGENT_STEP_TIMEOUT_MINUTES`, shared); `AGENT_MAX_DURATION_SECONDS` 1140 in each ConfigMap and in the scaffold | Export rebuilt; `kubectl diff -k` shows only that line for all 8 | done (2026-10-29); not yet applied |
| 10 | Run each agent's eval cases, then the workflow on `ENG-MERIDIAN-001` | All cases pass; the critic step waits for approval | todo |
| 11 | Compare with `sub-agents/ALZ-F01: Discovery Workflow Agent/` and record which pattern is adopted | An ADR in both patterns | todo (product owner) |
## Open questions (owner)
- **Platform team:** the tenant mapping (step 6). Does the executor externalise large step outputs between steps? (ADR 0010)
- **Product owner:** confirm the Proposed ADRs: 0003, 0004, 0005, 0006, 0007, 0008, 0010.