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>
2.2 KiB
2.2 KiB
Context: individual agents, ALZ-F01 Discovery
Facts for this Feature's individual-agents pattern, for coding agents. Repository-wide facts are in ../../.agents/CONTEXT.md. Per-agent context is in <agent>/.agents/CONTEXT.md.
Pattern
- Eight declarative agents, one per ALZ-DSC story. Each declares its own read-only MCP tools under
mcp:(allowed for top-level agents; only sub-agents can't hold MCP tools). - The workflow (
workflows/cp1-alz-discovery-individual.json) is the orchestration: step order throughparallelGroupandexecutionLevel, and data throughfrom_steps("<input>": "sN.<output field>"). The step map isSTEPSinscripts/build_workflow.py. - Nothing persists between steps except their replies (ADR 0010). There's no workspace, no hooks and no enforced verdict; the critic is gated by a human approval (ADR 0006).
Sources of truth
| What | Where |
|---|---|
| Requirements | ADO Epic 3214440, Feature 3214441, stories 3214451–3214458; v1.1 story files in the engineering hub workspace (drafts/cp1/agentic-landing-zone/stories/F01-discovery/) |
| Agent shape and repository conventions | cp4-agents (gitea.kyndemo.live/agents/cp4-agents) |
| Changes to requirements | docs/adr/ (this pattern only) |
| The MCP server | ../../mcp-servers/alz-discovery-sample (shared with the sub-agent pattern) |
Platform facts
- Runtime:
cruciblecoredevacr.azurecr.io/kab/agent-runtime-adk:0.35.7. Images are pushed tocruciblecoredevacr.azurecr.io/kab/cp1/<agent>:<version>. - Cluster:
crucible-kab-dev-aks, namespaceagents, kubeconfig/mnt/c/Users/JonathanBoniface/.kube/config. The gateways are incore-components: LiteLLM on:4000, the MCP gateway on:8000. There's noagent-platform-connectionsConfigMap, so the deploy profile sets the gateway URLs. - An agent needs its own
MCP_AGENT_API_KEY(Secret<agent>-secrets), issued when it's created in KAB. Without it, every request fails at startup. - As of 2026-10-29, MCP server registration fails in the MCP gateway, because KAB's default tenant
6ada663eb5b88053a9e43723isn't mapped there (it fails row-level security). This blocks every agent in both patterns.