# CP1 - Estate Scan Executor Agent Scans every planned scope entry at metadata level, one entry per call, and returns one structured finding per entry, flagging and never obeying prompt injection. ALZ-DSC-02 (ADO 3214452): one step of the workflow "CP1 - Agentic Landing Zone - Discovery". Version 0.1.0, built 2026-10-29 on the KAB agent runtime 0.35.7 (`agent-runtime-adk`). The runtime builds the agent from `agent.yaml`: its instructions are `prompt.md`, and it accepts and returns only what `schemas/` declares. There is no orchestrator; the workflow passes each step's output to the next. ## Inputs | Field | Type | Required | Description | |---|---|---|---| | `engagement_id` | string | yes | The engagement being discovered, e.g. ENG-MERIDIAN-001. | | `run_id` | string | no | The discovery run; the same id across the workflow's steps. | | `tasks` | array | yes | | ## Outputs | Field | Type | Required | Description | |---|---|---|---| | `findings` | array | yes | | ## MCP tools `alz-estate.scan_target`, `alz-cloud.get_resource_metadata`, all read-only, declared under `mcp:` in `agent.yaml` and reached through the MCP gateway. [`mcp-servers/alz-discovery-sample`](../../../mcp-servers/alz-discovery-sample/) serves them over the Meridian Retail Group sample estate. ## Knowledge packs None. ## Run it locally ```sh docker build -t cp1-estate-scan-executor-agent:local . docker run --rm -p 8080:8080 \ -e LITELLM_MODEL=gpt-5.6-sol \ -e LITELLM_PROXY_BASE= \ -e LITELLM_MASTER_KEY= \ -e MCP_GATEWAY_URL= \ -e MCP_AGENT_API_KEY= \ cp1-estate-scan-executor-agent:local curl http://localhost:8080/.well-known/agent-card.json ``` Then `python -m kyndryl_agent_runtime.eval --url http://localhost:8080 --cases eval/cases.yaml` runs the eval cases (it needs `kyndryl-agent-runtime[eval]`). Documentation for people is in [`docs/`](docs/); for coding agents, `CLAUDE.md` and `.agents/`.