Files
cp1-agents/individual-agents/ALZ-F01: Discovery Workflow Agent/cp1-discovery-package-agent/docs/user-guide.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

2.7 KiB

User guide: CP1 - Discovery Package Agent

For the Engagement Lead who approves a Discovery run, and for whoever starts the Assessment workflow from it.

What it does

After you continue past the report's review point, this step gathers every Discovery step's output into one package, with a manifest, and scores how much of what Assessment needs the run gives. It calls no model and no tool. You don't call it yourself: it runs as step s13 of CP1 - Agentic Landing Zone - Discovery.

Starting Assessment from it

KAB keeps the package as one project artifact. Its name is <execution id>_step_<position>: KAB numbers a run's step artifacts by position in the workflow, not by step id, and the package is _step_12 in the current workflow. Select that one artifact in the Assessment workflow's Artifacts step, rather than one artifact per Discovery step.

Reading the manifest

Field Read it as
complete true only when every required part arrived and the critic passed. If false, problems says why: don't start Assessment until it's resolved
critic_verdict The critic's verdict on the run
source_gaps Sources the run didn't read (for example itsm, or cmdb when none was uploaded). Assessment treats what they would give as declared gaps
parts Each part present, with its sha256 and item count. The parts are copied unchanged from the steps
agent_versions The agent versions the workflow was built with
scorecard How far the run answers Assessment's needs (below)

Reading the scorecard

Measure Read it as
f02_fields For each inventory record, the fields Assessment reads: filled has a value; declared_gap has none, for a reason the run declared; missing has none and no reason. filled is the value; a declared gap is honest but not value
f02_run The run-level facts Assessment checks before it starts
decisions What the run leaves for a person, by kind: CMDB drift, edges to validate, dangling CMDB relationships, SME review, coverage gaps, critic issues, Well-Architected fails
findings How many findings name an owner and a recommended action

When something looks wrong

You see Likely cause What to do
complete is false with "part missing" A step before it produced no output for that part Check that step in the run; rerun the workflow if it failed
complete is false with "critic verdict is fail" The critic failed the run, and the review still continued Resolve the critic's reasons before starting Assessment
A part's sha256 doesn't match The package was changed after it was made Use the artifact KAB stored for the run, never an edited copy