- Scripts to run workflows from a YAML context or run inputs (kab_run_workflow.py, with --input name=@file), store per-project discovery connections, bootstrap agent MCP keys, refresh the KAB token, publish reports and build estate snapshots. - Hyperscaler discovery servers extended in place; cloud-knowledge folded into them. - deploy/crucible-kab-dev.yaml: the Discovery package agent and the Assessment agents. - Platform issue write-ups and current-wiring notes under docs/platform-issues/. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
5.7 KiB
5.7 KiB
Context: cp1-agents
Repository-wide facts for coding agents. Pattern- and agent-specific context lives in individual-agents/<Feature>/.agents/ and in <agent>/.agents/.
Layout
<pattern>/<Feature>/<agent>/. The patterns aresub-agentsandindividual-agents. A Feature folder is namedALZ-F0N: <Feature> Workflow Agent. ALZ-F01 is built in both patterns; ALZ-F02 is built in the individual pattern only (not deployed); the F03 folders are empty.- A Feature folder works like a small repository: its agents,
workflows/, its ownscripts/build_workflow.pyand, for individual agents, its pattern ADRs and.agents/. Relative links inside a Feature (../scripts/,../workflows/,../../../docs/adr/from an agent'sdocs/adr/) resolve inside that Feature. - Shared, at the root:
scripts/:check_agents.py(cp4's rules, plusapp/only when declared);render_k8s.py(finds an agent by name under either pattern);kab_import_workflow.py <Feature folder>(loads that Feature'sscripts/build_workflow.py);kab_front_steps.py(Feature builders import it fromparents[3]/scripts);render_mcp_server.py,smoke_mcp_server.py.
mcp-servers/,deploy/, anddocs/.
MCP servers
mcp-servers/ holds rendered servers: never edit server.py by hand. See mcp-servers/README.md. azure-discovery, aws-discovery and gcp-discovery take a customer credential per project. Well-Architected guidance is a tool on the Azure and GCP servers; the separate cloud-knowledge server was retired on 2026-11-04. They're deployed to mcp-servers on public Python images (not hardened; no customer data yet), are registered in the CP1 Agentic Landing Zone tenant (6ae37d13999438461a529409), aren't tested on a real cloud, and no agent declares them.
Sources of truth
| What | Where |
|---|---|
| Requirements | ADO project "Global Modernization Engineering Hub - Agent Board": Epic 3214440, Features 3214441–3214447, F01 stories 3214451–3214458. The v1.1 story files are in the engineering hub workspace (drafts/cp1/agentic-landing-zone/), not in this repository |
| Agent shape | docs/source-material/agent-shapes/agent-pattern and subagent-pattern (KAB's; their .env files are local and git-ignored, and the zips, which contain .env files, are left out) |
| KAB workflow exports used as references | docs/source-material/workflow-files/ |
| Workflow documentation | docs/source-material/workflow-documentation/ |
| Reference repository | cp4-agents (gitea.kyndemo.live/agents/cp4-agents): layout, check script, workflow export format |
| Changes to requirements | Sub-agents: <agent>/docs/adr/. Individual agents: individual-agents/<Feature>/docs/adr/ |
| Platform problems found | docs/platform-issues/ |
Platform facts
- Runtime image:
cruciblecoredevacr.azurecr.io/kab/agent-runtime-adk:0.35.7. Images are pushed tocruciblecoredevacr.azurecr.io/kab/cp1/<component>:<version>. - Cluster: context
crucible-kab-dev-aks, in the Windows kubeconfig/mnt/c/Users/JonathanBoniface/.kube/config.- Agents run in namespace
agents, MCP servers inmcp-servers, and the gateways incore-components. - Model gateway:
http://kyn-agent-builder-litellm.core-components.svc.cluster.local:4000. Its key is Secretagent-builder-secrets, keylitellm-master-key, inagents. - MCP gateway:
http://kyn-agent-builder-mcp-gateway.core-components.svc.cluster.local:8000. - Shared storage: PVC
execution-storage-pvc(RWX) inagents, mounted at/data/executions. The platform doesn't setEXECUTION_STORAGE_ROOT, so an agent that writes there sets it in its own ConfigMap. - There's no
agent-platform-connectionsConfigMap, so the gateway URLs go in each agent's ConfigMap throughdeploy/<profile>.yaml.
- Agents run in namespace
- The
repolabel is in every Deployment's selector (includeSelectors: true). The individual agents keeprepo: cp1-agents-individual(set per agent indeploy/), and the orchestrator and the MCP server usecp1-agents. - 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. - MCP server registration fails as of 2026-10-29. In the gateway's single tenancy mode, a server insert passes row-level security only when the caller's tenant is
default, and KAB's default tenant isn't mapped to it. Seedocs/platform-issues/mcp-gateway-default-tenant/. - Workflow export (
export_version2.0.0):- Each agent step is a
generic_agent_calltohttp://<agent>.agents.svc.cluster.local:8080. - Inputs come
from_workflow,from_stepsorstatic(front steps only). parallelGroupandexecutionLevelorder the steps.- Approvals are
hitlwithcheckpoint_type: approval.
- Each agent step is a
- Models on the Azure resource behind the gateway:
gpt-4o,gpt-5.6-sol,claude-sonnet-5-5,claude-haiku-5-5,text-embedding-3-small. The cluster's LiteLLM servesgpt-4o,gpt-5.4,gpt-5.6-solandtext-embedding-3-small(checked 2026-11-01);claude-sonnet-5-5isn't served there, and a call to it fails.
Glossary
| Term | Meaning |
|---|---|
| Orchestrator | The sub-agent pattern's one agent per Feature. It makes every MCP call and holds the run workspace. |
| Sub-agent | A story's agent, run by the orchestrator through delegate (as_tool: false). It has functions only, never MCP tools. |
| Run workspace | Write-once records plus a hash-chained manifest, under /data/executions/alz-discovery/<engagement>/<run>/ |
| Phase | One request's share of a workflow: plan, collect, analyse or critique, for Discovery |
| Logical MCP server | A name in agent.yaml mcp: (alz-scope …), mapped to a deployed server at the MCP gateway |