Files
cp1-agents/individual-agents/ALZ-F02: Assessment & Disposition Workflow Agent
Jonathan Boniface 66c32745aa
Some checks failed
check agents / check (push) Failing after 14s
F02: Assessment report and package (ADR 0014, 0015); register agents in KAB
- Report (cp1-assessment-report-agent 0.2.0, step s7): a model writes the
  Assessment report from facts worked out in code (register, gaps, scorecard,
  rule traces, checks, and what each application is from the Discovery
  package); code sets the verdict and renders the pages. The
  disposition_signoff review point moves from the critic to the report.
- Package (cp1-assessment-package-agent 0.1.1, step s8): after sign-off, every
  step's output in one package, with a register, a gaps register, the
  sign-off record, lineage and a sha256 per part, in code. Page step s9.
- scripts/kab_register_agents.py: registers deployed agents in KAB's agent
  catalog (an in-place workflow update doesn't).
- Runs exec_1b1257380df7 (014) and exec_374d5d577077 (015) completed on
  crucible-kab-dev: critic pass, report figures all in its facts, package
  complete with every digest recomputing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-08 20:19:10 +00:00
..

ALZ-F02 Assessment & Disposition: individual agents

Six declarative KAB agents, one per ALZ-ASM story, chained by one KAB workflow, behind a code-only intake step that checks the Discovery package first (ADR 0008). They take an approved Discovery run's package and a rate card. For every application they produce a readiness profile, a migration risk score, advisory security findings (in-cloud estates only), a 7R disposition with an indicative TCO, and an independent critic's verdict, then a report the Engagement Lead signs off from as disposition_signoff, and one package for the later Features.

Requirements: ADO Feature 3214442, stories 3214459–3214464. The sub-agent pattern for this Feature isn't built yet, and the two are kept separate.

The workflow

workflows/cp1-alz-assessment-individual.json, built by scripts/build_workflow.py:

Step What Inputs from
a1 Artifacts: the Discovery run's package, by exact id The run (artifact_ids)
p1 Parse Assessment Files over a1's records a1.artifacts
s0 Assessment Intake (ADR 0008): checks the package in code (one package, every part's sha256, complete, critic pass, the named Discovery run); a refused package fails the run here p1
s1 Assessment Planner (ALZ-ASM-01): checks the preconditions and plans, or refuses p1, the run's rate_card_document, after s0
s2 Cloud Readiness Profiler (ALZ-ASM-02) p1, s1
s3 Migration Risk Scorer (ALZ-ASM-03) p1, s1
s4 Security Posture Assessment (ALZ-ASM-05): not applicable on-premises p1, s1
s5 7R Disposition & TCO (ALZ-ASM-04) p1, the run's rate_card_document, s1, s2, s3, s4
s6 Assessment Critic & Sign-off Router (ALZ-ASM-06) All of the above
s7 Assessment Report (ADR 0015): a model writes the report from facts worked out in code; approval step (disposition_signoff) s0 to s6
s8 Assessment Package (ADR 0014): after the approval, one package for Strategy and the later Features, in code: every step's output, a register per application, a gaps register, the report and the sign-off record s0 to s7, the run's inputs
s9 Format Assessment report for UI: the approved report as a page s7

s2, s3 and s4 run in parallel.

The Engagement Lead signs off from the Assessment report (s7, ADR 0015). The run's deliverables are the package (s8, ADR 0014) and the report's page (s9). Both exist only for a run continued at disposition_signoff, and continuing signs off the sign-off queue as it stands.

Starting a run

  1. Choose a Discovery run whose critic verdict is pass and which was approved. Note its execution id and the artifact id of its package step output (F01 ADR 0020). KAB names a run's step artifacts by position, not step id: the package is {execution_id}_step_12 in the current Discovery workflow. Select only that one artifact: the intake refuses anything else.

  2. Start the workflow with these values:

    • engagement_id
    • run_id
    • discovery_execution_id
    • discovery_approval_ref: the decision record approving the Discovery run
    • artifact_ids: the Discovery package artifact
    • rate_card_document: the rate card's JSON, as text (ADR 0009). There's no upload: an uploaded file would reach the parse step and be read in place of the Discovery package

    Alternatively, fix the artifact ids in the export with python3 scripts/build_workflow.py --artifact-id <id> ....

  3. Expect the intake to fail the run if the package is missing, changed, incomplete, from a failed critic, or from another Discovery run or engagement: its error lists every reason.

  4. Expect a refusal, not a plan, if no approval is given or there's no rate card. The critic then fails the run.

Rate card

The rate card is a JSON file with rate_card_id, currency and items. Each item has:

  • rate_id
  • category
  • description
  • annual_rate
  • equivalent_for: the services, products or asset classes it can replace
  • licence_terms

An illustrative sample for the Meridian Retail Group estate is in workflows/cases/meridian-assessment/rate-card.json. TCO is indicative; the Business Case (ALZ-BCS-02) gives the authoritative figure.

MCP servers

None added. Only ALZ-ASM-02 and ALZ-ASM-05 call tools, all read-only and all on existing servers in mcp-servers/: azure-discovery, aws-discovery and gcp-discovery, including their Well-Architected guidance tools. All three must be registered and healthy before those two agents can start (ADR 0007). The other four agents call no tool.

Decisions

The decision records cover how this pattern meets or interprets the stories:

  • Scoring as prompt rules that the critic recalculates.
  • Discovery's outputs arriving as parsed text, with the run id and approval as run inputs.
  • The rate card format.
  • Sign-off as the critic step's approval.
  • The models used.
  • The tool-call check this pattern can't make.
  • The MCP servers that must be registered first.

Status

Built and checked offline: six folders pass check_agents.py, the workflow export builds, and all 25 declared tools exist on their servers. Nothing is deployed, and no eval case or workflow run has been executed yet. The remaining steps are in .agents/PLAN.md.