What this is
CCAPI is the Claude project where cross-session continuity, protocol decisions, and technical infrastructure state are tracked. It is not a content project — it is the layer that keeps the other projects coherent. The “Code” in the name reflects its origin as the sandbox where Claude Code work happens, and its raison d’être as the technical environment for building, deploying, and testing.
What CCAPI actually touches
Not just protocol-keeping — CCAPI is the Claude Code operational spine that built: toi (toi.html, Netlify deployment, webhook architecture, Builds 3.2/3.9), briancrescenzo.com (DNS, sales pages for whmi and tsp, Jitsi session types), pp-awg (the story bible was generated using Claude Code to extract 26 Ulysses files — one of CCAPI’s most significant achievements and proof the methodology has creative/literary applications, not just technical ones), Quartz/Netlify deployment, GitHub/Airtable account creation, the cross-project glossary database (65+ entries seeded).
Evolution timeline (key inflection points)
Haiku queue adopted (April 20) then retired as mandatory (April 24–26) — not a capability failure but a workflow decision once the addendum approach proved more reliable for continuity, with explicit token headroom justifying the cost. Claude Code auth conflict resolved (env var override). UTK→ukbtp naming correction (mid-propagation, two instances still uncorrected as of June 26). Quartz deployed (June 19–21) then a stale-note-caught-and-corrected cycle (June 25–26) — a concrete, dated instance of the standing principle that KB claims propagated without verification are a known failure mode. GitHub/Airtable accounts created, Path B (Airtable relational) piloted on Continuum’s resume.
The pattern across all of these: adopt something, discover its real failure mode through use, correct it, write the correction down so the next session doesn’t re-derive it. That loop is closer to what CCAPI actually is than any single protocol currently in force.
Key relationships
Every project in the ecosystem touches CCAPI. toi (built the instrument), pp-awg (story bible extraction), ukbtp (protocols tested here, genericized there), wwz (Quartz/Kumu pipeline), Kieran (outside collaborator, explicitly NOT integrated with CCAPI — runs separate Claude implementation), continuum (whmi/Shamu sales pages built here).
Current state (as of June 28, 2026)
23+ versioned session addenda (v1.0–v23.0+). Quartz live at continuum-at-mmh.netlify.app. GitHub repo connection and single-document content-migration test are the next concrete infrastructure steps, unblocked but not yet executed.
Open items
Two remaining UTK→ukbtp instances in CCAPI’s own KB. GitHub repo creation. Single-document Quartz pipeline test (continuum.md ready). kumu/Notion bridge gap — no defined mechanism for Quartz output reaching Kumu.
Status note
This resume was written last, by design, after every other project in the ecosystem was resumed — so it could be sourced from real cross-project material rather than self-description. A first draft was produced and rejected as too narrow (protocol-keeper framing). This is the corrected version, synthesized June 28, 2026.
Migrated from Notion Pre-Quartz database (38d2a648-07c2-8147-badc-ef5e6e57becb).