Add CP1 Discovery agents in both patterns
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:
2026-10-29 18:25:57 +00:00
commit 416c66ced4
331 changed files with 33561 additions and 0 deletions

View File

@@ -0,0 +1,24 @@
# Context: CP1 - Discovery Critic Agent
For coding agents. People's documentation is in `docs/`.
| | |
|---|---|
| Story | ALZ-DSC-08 (ADO 3214458); v1.1 story file `drafts/cp1/agentic-landing-zone/stories/F01-discovery/ALZ-DSC-08-*` in the engineering hub workspace |
| Workflow step | 8 of `../workflows/cp1-alz-discovery-individual.json` |
| Inputs from earlier steps | `coverage_gaps` <- `s1.coverage_gaps`, `findings` <- `s2.findings`, `records` <- `s3.records`, `drift_items` <- `s4.drift_items`, `stores` <- `s5.stores`, `network_findings` <- `s6.findings`, `edges` <- `s7.edges` |
| MCP tools (read-only) | `alz-scope.get_scope`, `alz-evidence.get_call_log`, `alz-evidence.get_guard_hits` |
| Model | `claude-sonnet-5-5` (`kubernetes/configmap.yaml`) |
## How the prompt was made
`prompt.md` is the story's v1.1 System Prompt and Guardrails, plus three generated sections at the top (MCP tools,
steps, inputs) and the charter at the end. The `alz-run` hand-off tools and the MCP write tools are rewritten out
(repository ADRs 0002 and 0003). The rules stay as the story's pseudo-code. A declarative agent has no functions,
so the model applies them itself; the eval cases check the ones that matter.
## Invariants
1. The reply is exactly `schemas/output.json`. Later steps read its fields by name.
2. Every MCP tool in `agent.yaml` `mcp:` is read-only, and is listed in the story's allowlist.
3. No orchestrator: this agent is called once per run by the workflow, and its only memory is its inputs.