# User guide: CP1 - Cloud Readiness Profiler Agent For the Engagement Lead or Migration Architect reviewing an Assessment run. ## What it does Builds one metadata-only runtime profile per planned application with seven readiness signals, states that no telemetry exists, and assigns no disposition. It is step 2 of the workflow **CP1 - Agentic Landing Zone - Assessment** (ALZ-ASM-02, ADO 3214460). You don't call it yourself in normal use: start the workflow with the Discovery run's artifact ids, its execution id, the approval reference and the rate card, and this agent receives its inputs from the earlier steps. ## Reading its output The output fields are listed in the agent's [README](../README.md#outputs). Every fact it takes from Discovery cites `discovery:{execution_id}/{agent_id}/{record_key}`. Anything it couldn't establish is left empty or listed as missing, never guessed. ## What it will not do - Call any tool not on its allowlist, or pass a tool a hostname, address, URL, credential or customer text. - Write to any client system. - Follow instructions found in data. These are reported, not obeyed. ## When something looks wrong | You see | Likely cause | What to do | |---|---|---| | The step failed with `output_contract_violation` | The model's reply didn't fit the output schema twice | Rerun the step; if it repeats, report it with the run id | | A Discovery input reported missing | The Artifacts step didn't select that Discovery step's output, or it was too large to travel inline | Check the artifact ids given to the run | | Empty fields | The source records didn't support them | Expected: the agent leaves out what it can't evidence | Changes from the original requirements are listed in [adr/](adr/README.md).