Add CP1 Discovery agents in both patterns
All checks were successful
check agents / check (push) Successful in 10s
All checks were successful
check agents / check (push) Successful in 10s
ALZ-F01 Discovery as a sub-agent orchestrator (sub-agents/) and as eight individual declarative agents (individual-agents/), with their KAB workflow exports. Shared check, render and import scripts, the alz-discovery-sample MCP server, the crucible-kab-dev deploy profile, deployment docs, platform issue reports and the source material. Agent steps time out at 20 minutes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,11 @@
|
||||
# Changes to ALZ-DSC-02's original requirements
|
||||
|
||||
The decisions are recorded once, for all eight agents, in the Feature's [docs/adr/](../../../docs/adr/README.md). These change what the ALZ-DSC-02 story (ADO 3214452) and its v1.1 story files say:
|
||||
|
||||
- [ADR 0001](../../../docs/adr/0001.md)
|
||||
- [ADR 0002](../../../docs/adr/0002.md)
|
||||
- [ADR 0004](../../../docs/adr/0004.md)
|
||||
- [ADR 0007](../../../docs/adr/0007.md)
|
||||
- [ADR 0008](../../../docs/adr/0008.md)
|
||||
|
||||
A change that affects only this agent gets its own record here, numbered `02-NNNN`.
|
||||
@@ -0,0 +1,33 @@
|
||||
# User guide: CP1 - Estate Scan Executor Agent
|
||||
|
||||
For the Engagement Lead or delivery engineer reviewing a discovery run.
|
||||
|
||||
## What it does
|
||||
|
||||
Scans every planned scope entry at metadata level, one entry per call, and returns one structured finding per entry, flagging and never obeying prompt injection.
|
||||
|
||||
It is step 2 of the workflow **CP1 - Agentic Landing Zone - Discovery** (ALZ-DSC-02, ADO 3214452). You don't
|
||||
call it yourself in normal use: run the workflow with `engagement_id` and `run_id`, 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 states cites an
|
||||
`evidence_ref` from the MCP call it came from. Anything it couldn't establish is left empty, or listed as a gap or
|
||||
an issue, never guessed.
|
||||
|
||||
## What it will not do
|
||||
|
||||
- Call any tool not on its allowlist, or pass a tool a hostname, address, URL or credential.
|
||||
- Write to any client system: all its tools are read-only.
|
||||
- Follow instructions found in data. These are recorded as prompt-injection findings.
|
||||
|
||||
## 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 refused tool call in the output | The MCP gateway refused the call (allowlist, scope or rate) | Check the agent's registration on the MCP gateway |
|
||||
| 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).
|
||||
Reference in New Issue
Block a user