Files
cp1-agents/individual-agents/ALZ-F02: Assessment & Disposition Workflow Agent/cp1-migration-risk-scorer-agent
Jonathan Boniface 041e199248
Some checks failed
check agents / check (push) Failing after 12s
ALZ-F02 Assessment: critic code checks (ADR 0011), represents edges (ADR 0012)
- Critic 0.2.0 / 0.2.1: K-04 (risk), K-05 (confidence), K-06 (TCO), K-07 (routing) and K-11
  (schema and 7R enum) run in code in the critic's hooks (app/arithmetic.py,
  app/business_logic.py); post_process sets those checks, the rejected dispositions, the
  sign-off queue and the verdict. The model keeps the judgement checks; a different reading of
  a code check is kept in unverified_claims. K-07 checks the disposition agent's own queue.
  Tests on the records of run exec_4d88027a4d26, whose model sums were wrong.
- A represents edge is not a dependency (ADR 0012): risk scorer 0.1.1 and disposition 0.1.2
  leave it out of dependents and dependencies; the disposition and critic prompts carry the
  risk scorer's rule. Run exec_1f518b04d6e4: APP-001's risk 1.00 -> 0.00, out of the tail.
- The scaffold declares the critic's hooks, copies app/ in its Dockerfile, and keeps its
  app/ and tests/ when regenerating.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-06 13:20:40 +00:00
..

CP1 - Migration Risk Scorer Agent

Scores each planned application's migration risk from four weighted factors, names missing factors, and flags the high-risk tail by score or hard trigger.

ALZ-ASM-03 (ADO 3214461): 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
scores array yes
high_risk_tail array yes
findings_note string yes

MCP tools

None. Scoring, confidence and TCO are rules in prompt.md, recalculated by the critic (ADR 0001).

Run it locally

docker build -t cp1-migration-risk-scorer-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-migration-risk-scorer-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/.