# Proofs of Concept
Six proofs of concept (PoCs), one folder each. Each folder has its own README, documents and, where there is code, its own commands, run from inside that folder.
| PoC | Folder | What it is | Contents |
|---|---|---|---|
| **PoC 1: Slack Automation Platform** | [poc1-slack-platform/](poc1-slack-platform/README.md) | A small platform that connects Slack to a web app without an API, Jira and a knowledge base, with an LLM for the reading and writing in between. Three use cases: web form automation, daily report, knowledge base chatbot | Code, AWS deployment (CloudFormation, ECS Fargate), platform documents 01 to 09, one concept document per use case in `docs/concepts/` |
| **PoC 2: AIPF** | [poc2-aipf/](poc2-aipf/README.md) | The organisation's own AI platform, on which agents carry the roles of a development team across the software lifecycle | Documents only. The POC code is in the separate `aipf-sdlc` repository |
| **PoC 3: Project Notebook** | [poc3-project-notebook/](poc3-project-notebook/README.md) | A web app in the style of NotebookLM: a project team asks questions about Confluence and Jira content and the files attached to it, writes study material and research reports from it and reads each source's sync state, with access per space and project, page and issue restrictions, and an MCP server for code editors | Code, AWS deployment, an [executive overview](poc3-project-notebook/docs/01-executive-overview.md), an [engineering guide](poc3-project-notebook/docs/02-engineering-guide.md), and the full concept in [CONCEPT.md](poc3-project-notebook/CONCEPT.md) |
| **PoC 4: API Automation** | [poc4-api-automation/](poc4-api-automation/README.md) | API test automation with Playwright Test for two Spring Boot REST services, built and measured on a local simulation of the real project (two services, database, identity provider, stubbed third parties on Docker), so the framework, the pipeline stage and the contract check can move to the real project | Code (simulation in `sim/`, test suite in `tests/`), a reference CodeBuild spec, the [strategy and findings](poc4-api-automation/docs/01-strategy-and-findings.md) and the [adoption guide](poc4-api-automation/docs/02-adoption-guide.md) |
| **PoC 5: Databricks Lakehouse** | [poc5-databricks-lakehouse/](poc5-databricks-lakehouse/HANDOVER.md) | A lakehouse on Databricks for retail, e-commerce and logistics, built on public or synthetic data as hands-on practice for the Databricks Certified Context Engineer Associate exam | Not started: only the handover brief |
| **PoC 6: Spec Review Agent** | [poc6-spec-review-agent/](poc6-spec-review-agent/README.md) | An agent that reviews a synthetic Japanese specification and writes the question list (質問表) for the customer as JSON and Excel, scored by code against planted problems. The case study for the Claude Certified Architect – Foundations exam | Python code (hand-written Messages API loop first, then Agent SDK, MCP server, Claude Code configuration), the synthetic spec and answer list, a [study map](poc6-spec-review-agent/docs/study-map.md) and [decision notes](poc6-spec-review-agent/docs/decisions.md) |
## Kits
Reusable packages built from the PoCs, released as versioned zip files on the repository's GitHub releases (tag `<kit>-v<version>`). The list, the naming rules and the release steps are in [kits/README.md](kits/README.md).
| Kit | From | What it is |
|---|---|---|
| [api-test-agent-kit](kits/api-test-agent-kit/KIT.md) | PoC 4 | The Playwright API test suite with the rules, skills, plain-language test-case catalogue and tooling that let a coding agent set up, write, maintain and sync API tests |
## How the PoCs relate
- PoC 3 takes its settings from environment variables, and also reads PoC 1's settings files (`poc1-slack-platform/.env`, `infra/local.env`) when they exist. Its AWS resources are its own (prefix and tag `poc3-kb`).
- PoC 2's knowledge base work builds on PoC 1's documents 08 and 09.
- PoC 4 runs entirely on Docker on one machine and uses no AWS resources or shared settings.
- PoC 5 and PoC 6 use no AWS resources and no settings of the other PoCs. PoC 6 calls the Claude API with its own key, within a budget the owner approved.
- Each PoC's AWS resources are tagged separately: `slack-web-automation-poc` for PoC 1, `poc3-kb` for PoC 3.
## Not in git
Settings and secrets that differ per environment stay out of git: `.env`, `infra/local.env` and `infra/kb-cert/` in PoC 1, `infra/deploy.local.json` in PoC 3, `tests/envs/*.env` (except the dummy `local.env`) in PoC 4, `.env` and the run output `runs/` in PoC 6, and every `node_modules/`, `.venv/`, build output and generated test data. See `.gitignore`.