00 — Context
Note (2026-06-02): This chapter’s narrative sections (Problem statement, Business motivation, Scope, Success criteria, Stakeholders) are placeholders. The substantive plan for this project lives in the signed PDF (
Adventive_Public_API_Cloudflare_Migration_Plan.pdf, Version 2, 2026-04-22) and the implementation chapters (06-implementation-steps.md,07-as-built-runbook.md). The Project coordinates section below is promoted from personal Claude memory on 2026-06-02 and is the authoritative pointer to where the implementation lives.
Project coordinates
Section titled “Project coordinates”The Adventive Public API migration (CodeIgniter PHP → Cloudflare Worker, TypeScript/Hono) is implemented as a standalone repository outside the engineering documentation workspace.
- Local repo path:
~/Repositories/GitHub/Adventive/adventive-public-api-worker/ - GitHub slug:
Adventive/adventive-public-api-worker - Implementation surface: Claude Code (not Cowork). This was agreed on 2026-04-23. Cowork’s role is planning, PDFs, and cross-app coordination; Claude Code handles the code and the
wranglerpipeline. - Handoff folder:
docs/projects/public-api-cf-migration/handoff/containsCLAUDE.md,PLAN.md, andCLAUDE_CODE_KICKOFF.md. Claude Code’s first action is to ensure the repo path exists,git init, and copyCLAUDE.md+PLAN.mdfrom the handoff folder into the repo root. - Signed plan PDF:
Adventive_Public_API_Cloudflare_Migration_Plan.pdf(Version 2, 2026-04-22).
Non-goals during the code session
Section titled “Non-goals during the code session”The implementation session does not execute:
- Real
wrangler deployto any environment. - Cloudflare resource provisioning (Hyperdrive, KV, Durable Objects, etc.).
- Edits to the legacy PHP repository.
- Use of live secrets.
git pushto a remote.
Phases 0, 1, 2, 3, and 8 of the plan are executed by Jeff outside the code session.
Pause checkpoints
Section titled “Pause checkpoints”Claude Code pauses at the end of Phase 5 (middleware complete) and at the end of Phase 6 (all handlers complete). At each checkpoint Claude Code posts a gate-run summary and waits for an explicit “continue” before resuming.
Problem statement
Section titled “Problem statement”What is broken, slow, expensive, risky, or about to end-of-life?
Business motivation
Section titled “Business motivation”Why does this matter now? Deadline, compliance, cost, customer impact, strategic fit.
- In scope:
- Out of scope:
- Deferred:
Success criteria
Section titled “Success criteria”How will we know we’re done? Concrete, measurable, testable.
Stakeholders
Section titled “Stakeholders”| Role | Name | Interest |
|---|---|---|
| Owner | Jeff Lambert | Architecture and migration sequencing |
| Approver | ||
| Consulted | ||
| Informed |