- Six declarative agents generated from the v1.1 stories (scaffold_from_stories.py, ADR 0001),
and a 9-step workflow export (build_workflow.py).
- Code-only intake (ADR 0008) verifies the one Discovery package in code before any agent.
- The rate card is the run input rate_card_document; no upload step (ADR 0009).
- Critic 0.1.6 after live runs on crucible-kab-dev:
- K-12 model independence checked at build time against each agent's deployed model
(ADR 0010); the critic reports it from its two inputs;
- receives in_cloud_estate for K-10; an unverified K-10 never fails the run alone;
- K-08 allows the scoring note to list findings as advisory, as ALZ-ASM-04 must;
- carries ALZ-ASM-03's and ALZ-ASM-04's rule sections, copied by the scaffold, so it can
recalculate risk, confidence and TCO.
- The scaffold refuses to regenerate unless every story file is present.
- Case azure-crucible-kab-dev-assessment with an illustrative rate card.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
CP1 - Cloud Readiness Profiler Agent
Builds one metadata-only runtime profile per planned application with seven readiness signals, states that no telemetry exists, and assigns no disposition.
ALZ-ASM-02 (ADO 3214460): one step of the workflow "CP1 - Agentic Landing Zone - Assessment". Version 0.1.0,
built 2026-11-02 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, e.g. ENG-MERIDIAN-001. |
run_id |
string | no | The Assessment run; the same id across the workflow's steps. |
discovery_execution_id |
string | yes | The Discovery run's execution id, e.g. exec_0d5c0e2a7f01. Every reference to a Discovery record names it. |
discovery_documents |
string / null | no | The Discovery run's step outputs as text: the Artifacts step's records, parsed by the parse step (p1.parsed_content). One JSON document per selected artifact, separated by a line '---'. |
discovery_files |
array / null | no | The parse step's file_metadata (p1.file_metadata): the selected artifacts' names, in the order their text appears in discovery_documents. |
tasks |
array | yes | |
applications |
array | yes |
Outputs
| Field | Type | Required | Description |
|---|---|---|---|
discovery_execution_id |
string | yes | |
profiles |
array | yes | |
gaps |
array | yes | |
findings_note |
string | yes |
MCP tools
Azure Discovery.azure_list_servers, Azure Discovery.azure_list_workloads, Azure Discovery.azure_list_kubernetes_clusters, Azure Discovery.azure_list_data_stores, AWS Discovery.aws_list_servers, AWS Discovery.aws_list_workloads, AWS Discovery.aws_list_kubernetes_clusters, AWS Discovery.aws_list_data_stores, Google Cloud Discovery.gcp_list_servers, Google Cloud Discovery.gcp_list_workloads, Google Cloud Discovery.gcp_list_kubernetes_clusters, Google Cloud Discovery.gcp_list_data_stores, all read-only, declared under mcp: in agent.yaml and reached through the MCP gateway. They are the existing servers in mcp-servers/; no server was added for Assessment. All declared servers must be registered and healthy for the agent to start (ADR 0007).
Run it locally
docker build -t cp1-cloud-readiness-profiler-agent:local .
docker run --rm -p 8080:8080 \
-e LITELLM_MODEL=gpt-5.6-sol \
-e LITELLM_PROXY_BASE=<your LiteLLM gateway> \
-e LITELLM_MASTER_KEY=<your LiteLLM key> \
-e MCP_GATEWAY_URL=<your MCP gateway> \
-e MCP_AGENT_API_KEY=<the agent's MCP key> \
cp1-cloud-readiness-profiler-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/; for coding agents,
CLAUDE.md and .agents/.