Files
cp1-agents/individual-agents/ALZ-F01: Discovery Workflow Agent/CLAUDE.md
Jonathan Boniface 9e503885cc ALZ-F01 Discovery: package step, value scorecard, application grouping, cases
- New cp1-discovery-package-agent (ADR 0020): one package per reviewed run, every part
  hashed (sha256 over canonical JSON), with a manifest and a value scorecard.
- Applications grouped CMDB -> tag -> resource group with a judged model fallback (ADR 0021):
  CMDB 0.7.0 carries ownership, dependency mapping 0.6.0 groups, report 0.9.0 shows them.
- Critic 0.6.1 accepts the producers' enums; build_workflow.py refuses a consumer enum
  narrower than its producer's.
- Code hooks, sub-agents and tests for the inventory, CMDB, dependency, planner and critic
  agents; the report and Well-Architected review agents; ADRs 0012-0021.
- Workflow cases with value bars and run limits; run evaluation and usage collection scripts;
  the run context template and the field-by-field review for ADR 0016.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-05 22:13:25 +00:00

30 lines
2.5 KiB
Markdown

# Individual agents: ALZ-F01 Discovery
CP1 Discovery as eleven separate KAB agents chained by the workflow, cp4-agents style. Its counterpart, `../../sub-agents/ALZ-F01: Discovery Workflow Agent/`, is the sub-agent pattern. **Keep the two patterns apart:** never copy `app/`, sub-agents or workspace code into this folder, and never merge their ADRs.
@.agents/CONTEXT.md
@.agents/PLAN.md
Each agent folder has its own `CLAUDE.md` and `.agents/CONTEXT.md`. Repository-wide rules are in `../../CLAUDE.md`.
Read `../../docs/platform-issues/agent-tools-and-context/individual-agents-report-2026-11-01.md` before changing an agent's tools, a schema or `STEPS`, and run `python3 scripts/check_context_doc.py` afterwards.
## Commands (from this folder)
```sh
python3 ../../scripts/check_agents.py --runtime-image cruciblecoredevacr.azurecr.io/kab/agent-runtime-adk:0.35.7 cp1-*/
python3 scripts/build_workflow.py # after any schemas/ change; it asserts every from_steps field exists and no input refuses a value its producer can hold
python3 scripts/evaluate_workflow_run.py workflows/cases/<case>/case.yaml <steps.json> --usage <usage.json>
python3 scripts/collect_run_usage.py <execution id> --out <usage.json> # read-only kubectl logs
(cd ../.. && python3 scripts/render_k8s.py deploy/crucible-kab-dev.yaml <agent> && kustomize build build/crucible-kab-dev/<agent>)
```
## Rules
- **Code hooks only where an ADR says so** (0014, 0015, 0017, 0018, 0019, 0020). Otherwise an agent stays declarative. The shared `check_agents.py` refuses an `app/` to any agent that declares no hook or function. Don't relax it.
- **Every step's output reaches the package** (`s13`, ADR 0020). A new output field needs a row in `cp1-discovery-package-agent/app/package.py` `INPUTS` and its wiring in `scripts/build_workflow.py`; the package's tests check the two match.
- **Cases carry a value bar and limits** (`value:`, `limits:` in `workflows/cases/*/case.yaml`). Raise a bar when a change improves the scorecard; never lower one to make a run pass.
- **The agent folders were generated** by `scripts/scaffold_from_stories.py`. Edit a folder directly, or change the script and regenerate. Regenerating rewrites whole folders, so review the diff afterwards.
- **Keep `repo: cp1-agents-individual`** on these agents in `../../deploy/`. The label is part of each Deployment's selector.
- **A change to an original requirement** needs three things: an ADR in `docs/adr/`, a link to it from each affected agent's `docs/adr/README.md`, and a step in `.agents/PLAN.md`.