- 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>
34 lines
3.4 KiB
Markdown
34 lines
3.4 KiB
Markdown
# 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](deployment.md) | Platform operators: building, pushing and deploying every agent and MCP server with kustomize |
|
|
| [artifact-integration-plan-2026-10-29.md](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](hyperscaler-mcp-servers-plan-2026-10-30.md) | Engineers and reviewers: the plan to build the Azure, AWS and Google Cloud discovery MCP servers |
|
|
| [hyperscaler-interchange-review-note-2026-11-01.md](hyperscaler-interchange-review-note-2026-11-01.md) | Reviewers: using the real cloud servers in one set of Discovery agents, parked for future review |
|
|
| [customer-cloud-access.md](customer-cloud-access.md) | Customer cloud administrators: granting read-only access for discovery |
|
|
| [platform-issues/](platform-issues/) | Platform team: KAB problems found while building these agents |
|
|
| [source-material/](source-material/) | Everyone: the inputs these agents were built from (read-only) |
|
|
| [strategy-outline/](strategy-outline/) | Not yet written |
|
|
|
|
## Platform issues
|
|
|
|
| Issue | Status |
|
|
|---|---|
|
|
| [MCP server registration fails with a 500 (default tenant not mapped in the MCP gateway)](platform-issues/mcp-gateway-default-tenant/report-2026-10-29.md) | 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](platform-issues/vault-service-not-deployed/report-2026-10-30.md) | Open. It blocks every stored MCP credential. |
|
|
| [The Artifacts step can't select an earlier step's output within the same run](platform-issues/artifacts-step-within-a-run/report-2026-10-29.md) | Open, with questions for the platform team. It doesn't block F01, where hand-offs use `from_steps`. It affects F01 → F02. |
|
|
| [A workflow can't run or chain another workflow](platform-issues/workflow-composition/report-2026-11-02.md) | Open. Each Feature is started by hand, with the previous Feature's artifact ids. It affects F01 → F02 and every later hand-off. |
|
|
| [The Artifacts step's lookup isn't scoped to the run's tenant or project](platform-issues/select-artifacts-tenant-scope/report-2026-11-02.md) | Open, needs triage: a possible tenant-isolation defect, found by reading the code and not tested. CP1 selects by exact id until it's resolved. |
|
|
| [MCP tools and context in the individual-agents pattern](platform-issues/agent-tools-and-context/individual-agents-report-2026-11-01.md) | Open. Some step outputs reach no later step, and large hand-offs are unconfirmed. The sub-agent pattern's review will follow |
|
|
|
|
## 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 |
|