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>
25 lines
1.3 KiB
Markdown
25 lines
1.3 KiB
Markdown
# Context: CP1 - Estate Scan Executor Agent
|
|
|
|
For coding agents. People's documentation is in `docs/`.
|
|
|
|
| | |
|
|
|---|---|
|
|
| Story | ALZ-DSC-02 (ADO 3214452); v1.1 story file `drafts/cp1/agentic-landing-zone/stories/F01-discovery/ALZ-DSC-02-*` in the engineering hub workspace |
|
|
| Workflow step | 2 of `../workflows/cp1-alz-discovery-individual.json` |
|
|
| Inputs from earlier steps | `tasks` <- `s1.tasks` |
|
|
| MCP tools (read-only) | `alz-estate.scan_target`, `alz-cloud.get_resource_metadata` |
|
|
| Model | `gpt-5.6-sol` (`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.
|