# 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//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 | | [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) | Open. It blocks MCP registration for both patterns. The proposed gateway manifests are alongside the report and **have not been applied**. | | [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. | ## 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 |