Files
cp1-agents/docs/README.md
Jonathan Boniface c14a94f33b
Some checks failed
check agents / check (push) Failing after 12s
Add hyperscaler discovery MCP servers and Well-Architected guidance
azure-discovery, aws-discovery and gcp-discovery collect read-only metadata
on servers, workloads, Kubernetes clusters, networks, data stores, policies
and provider recommendations. Credentials arrive per call from the vault.
Replies are paged, scrubbed of secrets and anonymised, and throttled calls
back off. cloud-knowledge searches each provider's Well-Architected guidance
from fixed lists only, so no customer detail can leave the platform.

Adds shared skills, the render and test tooling, a public Python Dockerfile
until the hardened base image is reachable, the customer access guide, the
implementation plan and the Vault Service platform issue.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-30 20:11:57 +00:00

2.4 KiB

cp1-agents: documentation

Repository-wide documents for people. The docs for each agent are in its own docs/ folder, and the individual-agents pattern's ADRs are in individual-agents/<Feature>/docs/adr/.

Document For
deployment.md Platform operators: building, pushing and deploying every agent and MCP server with kustomize
artifact-integration-plan-2026-10-29.md Reviewers: how uploaded files and project artifacts reach the agents in both patterns
hyperscaler-mcp-servers-plan-2026-10-30.md Engineers and reviewers: the plan to build the Azure, AWS and Google Cloud discovery MCP servers
customer-cloud-access.md Customer cloud administrators: granting read-only access for discovery
platform-issues/ Platform team: KAB problems found while building these agents
source-material/ Everyone: the inputs these agents were built from (read-only)
strategy-outline/ Not yet written

Platform issues

Issue Status
MCP server registration fails with a 500 (default tenant not mapped in the MCP gateway) Resolved 2026-10-30: registration returns 201, and the gateway now runs with MCP_GATEWAY_TENANCY_MODE=pooled, which binds each caller's tenant. The manifests alongside the report weren't applied from this repository.
The Vault Service isn't deployed on the dev cluster Open. It blocks every stored MCP credential.
The Artifacts step can't select an earlier step's output within the same run Open, with questions for the platform team. It doesn't block F01, where hand-offs use from_steps. It affects F01 → F02.

Source material

Folder Contents
source-material/agent-shapes/ KAB's agent-pattern and subagent-pattern. Their .env files are local only (git-ignored), and the zip archives are left out.
source-material/workflow-files/ KAB workflow exports used as format references
source-material/workflow-documentation/ The Discovery workflow description (PDF) and example user story files