Platform scripts, MCP servers, deployment and docs for the KAB runs
- 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>
This commit is contained in:
@@ -4,7 +4,7 @@ Repository-wide facts for coding agents. Pattern- and agent-specific context liv
|
||||
|
||||
## Layout
|
||||
|
||||
- **`<pattern>/<Feature>/<agent>/`.** The patterns are `sub-agents` and `individual-agents`. A Feature folder is named `ALZ-F0N: <Feature> Workflow Agent`. ALZ-F01 is built; the F02 and F03 folders are empty.
|
||||
- **`<pattern>/<Feature>/<agent>/`.** The patterns are `sub-agents` and `individual-agents`. A Feature folder is named `ALZ-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 own `scripts/build_workflow.py` and, for individual agents, its pattern ADRs and `.agents/`. Relative links inside a Feature (`../scripts/`, `../workflows/`, `../../../docs/adr/` from an agent's `docs/adr/`) resolve inside that Feature.
|
||||
- **Shared, at the root:**
|
||||
- `scripts/`:
|
||||
@@ -17,7 +17,7 @@ Repository-wide facts for coding agents. Pattern- and agent-specific context liv
|
||||
|
||||
## 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; `cloud-knowledge` takes Kyndryl's, tenant-wide. 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.
|
||||
`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
|
||||
|
||||
@@ -48,7 +48,7 @@ Repository-wide facts for coding agents. Pattern- and agent-specific context liv
|
||||
- Inputs come `from_workflow`, `from_steps` or `static` (front steps only).
|
||||
- `parallelGroup` and `executionLevel` order the steps.
|
||||
- Approvals are `hitl` with `checkpoint_type: approval`.
|
||||
- **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`. Whether the cluster's LiteLLM serves each name hasn't been confirmed.
|
||||
- **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 serves `gpt-4o`, `gpt-5.4`, `gpt-5.6-sol` and `text-embedding-3-small` (checked 2026-11-01); `claude-sonnet-5-5` isn't served there, and a call to it fails.
|
||||
|
||||
## Glossary
|
||||
|
||||
|
||||
Reference in New Issue
Block a user