This bundle turns the attached Heady directives and configuration seeds into a production-oriented monorepo with Cloudflare edge workers, Cloud Run services, shared runtime packages, pgvector migrations, deployment workflows, and operational runbooks. Internal source material comes from the attached workspace directives, HCFullPipeline definitions, and cognitive configuration.
Cloudflare’s remote MCP guidance recommends Streamable HTTP as the current transport standard and Durable Objects when MCP sessions need state, which fits HeadyMCP’s edge-native control plane (Cloudflare Agents docs).
Cloudflare Vectorize supports up to 5 million vectors per index and up to 1536 dimensions, which makes it a strong edge retrieval layer while origin pgvector remains the authoritative memory plane (Cloudflare Vectorize).
HeadyMCP publicly positions itself as an edge-native MCP server with JSON-RPC transport, SSE support, and 30+ tools for IDEs such as VS Code, Cursor, and Windsurf (HeadyMCP).
HeadyAPI publicly positions itself as a liquid gateway that races 4+ providers and uses auto-failover, which directly informs the worker routing layer included here (HeadyAPI).
- Shared phi and CSL packages
- 15 Cloud Run service scaffolds
- 4 Cloudflare worker scaffolds
- pgvector and Graph RAG migrations
- CI/CD, Docker, smoke tests, and deployment templates
- Reconciled directives and missing cognitive-layer files
- Runbooks, ADRs, and activation checklists
- Install
pnpmand Node 22. - Copy
.env.exampleto.envand fill secrets. - Provision Cloudflare, GCP, PostgreSQL with pgvector, and Redis.
- Run
pnpm installthenpnpm build. - Run
pnpm devordocker compose up --build. - Deploy Cloudflare workers and Cloud Run services via the included GitHub Actions.
This bundle gives you the complete file system, contracts, deployment scaffolding, and core runtime glue needed for production hardening. Final go-live still requires live credentials, DNS, certificates, Cloudflare/GCP accounts, and real provider keys.