Internal Workspace · The Codex · not for public distribution
Yemaya·The Codex
Codex › Living Log
Living Document · Updated by every CPN agent

CPN Living Log — Clinical Partners Network

The cross-agent working doc. Every agent who touches CPN appends here. The top sections are the current snapshot; the bottom is the chronological history.

Project: Active 6 sub-phases tracked Yemaya site LIVE · cpn.laboracollective.com (SSL issued) Stripe membership LIVE (3 products / 6 prices) /internal/ Codex workspace deployed (8 pages) Trilogy essays — republish in AV format planned /internal/ auth still pending decision Living Log adoption still unenforced Last updated: 2026-05-06 (entry 6)

On this page

How to use this doc

If you are an agent working on CPN, you MUST: (1) read the entire top half of this file before writing, (2) append your update to the bottom in a new <div class="update-entry"> block using the template at the end, (3) update the "Current state" section if your work materially changed it, (4) update the "Active blockers" or "Open questions" lists if you resolved or added items.
If you are YC reviewing: the top sections (What CPN Is → Open Questions) are always-current. Scroll past those for the chronological log of who did what when. Most recent agent entry is at the top of the updates section.

Primary (live, editable): ~/Downloads/CPN_LIVING_LOG.html. This is what agents append to. Snapshot backup: Shared drives/Business Operations/Product Development/Clinical Partners Network Program/Cross-Agent Working Docs/CPN_LIVING_LOG.html on Google Drive — re-copied on every append so it stays current. Other agents — Antigravity, Multi-account Claude, Plaud, Gemini, etc. — should write to the primary at ~/Downloads/ and re-sync to Drive on close.

What CPN is

The Clinical Partners Network (CPN) is the credentialed home for the women's health story — clinicians and journalists telling it together, on infrastructure that doesn't suppress it. Members are clinicians, doulas, midwives, wellness practitioners, advocates, journalists, and media. Each member gets a microsite at theirname.laboracollective.com — same architecture, different content shape, no algorithmic suppression. CPN is one of the two-platform vision's two halves: The Mother / Healer / Clinician → Labora Collective; The Lover / Creator / Storyteller → Powerhouse Novelas. CPN sits on the LC side. Journalists were always part of the plan; they are now formalized.

The six sub-phases

The umbrella PROJECTS row in Airtable tracks six sub-phases. TASKS use the existing Phase 1–6 single-select to map.

— Phase 1 —
CPN Clinical Network
Provider directory, referral, credentialing, salons, intake forms, onboarding flows, partner ROI tracking. The original CPN program.
— Phase 2 —
CPN Education
Curricula, workshops, certifications. Doula training, field guides, the four-tier compendium (Basic/Intermediate/Advanced/Connector).
— Phase 3 —
CPN Media Arm — Publishing Platform
Credentialed publishing for clinicians, doulas, wellness, advocates. Substack-equivalent with clinician-grade editorial standards. Phase 1 cohort: 10–20 hand-picked providers in 60 days.
— Phase 4 —
CPN Media Arm — Journalists (NEW, EXPLICIT)
Journalists as first-class CPN members. Same architecture, different content shape (long-form, investigative, op-ed, visual storytelling). Always intended; now formalized.
— Phase 5 —
CPN Public-Facing Site
cpn.laboracollective.com — the consolidated home for CPN information. Built 2026-04-29. Deploy blocked on YC.
— Phase 6 —
CPN Editorial Recruitment
Breana recruitment thread + future editorial hires. Aisha's scope still being defined.

Load-bearing voice (verbatim)

Do not paraphrase. Do not soften. These phrases are load-bearing. They appear verbatim on the cpn.laboracollective.com site, in the strategy doc Part 11, and in member-facing copy. Any agent producing CPN content must use these exact phrasings where the topic calls for them.

Current state at a glance

What exists today (2026-04-29)

What's queued (Phase 1 priorities)

Active blockers

B4 — Source-of-truth restoration pending YC review of salvage deck (raised 2026-05-05)

The 262-session salvage audit (entry 3 below) found 11 salvageable items + 3 recommended actions, packaged into a 16-slide decision deck at ~/Documents/CPN/decks/2026-05-05_CPN_Salvage_Decisions.html. Restoration scope can't be locked until YC steps through the deck and approves / declines / defers each finding. What it would take to unblock: ~15 min on the deck. The two highest-stakes calls are Q6 and Q7 (below).

B2 — Living Log is not being used by agents (systemic, blocks compounding)

Audit ran 2026-05-05: this machine alone has 262 Cowork sessions + ~10 Claude Code sessions that mention CPN across Mar–May 2026. Of those, ~70 were human-initiated conversations, 147 were Dispatch-spawned subagents, 25 were scheduled routines. None of the post-2026-04-29 sessions appended to this Living Log. The doc was created on Apr 29 specifically to fix the "agents don't build on each other" problem, and then no agent used it. Result: every CPN session re-discovers context from scratch — the exact pattern this file was meant to break.

What it would take to fix: a hook or skill that fires on any Cowork/Code/Dispatch session whose CWD or subject mentions CPN, instructing the agent to read this file first and append on close. Without that automation, the convention is unenforceable. Companion catalog of all 262 sessions: ~/Downloads/CPN_SESSION_CATALOG.html.

B1 — RESOLVED 2026-05-06 — Site live

Repo at yconnor-maker/cpn-laboracollective (private, latest commit 42bb98c). Netlify project cpn-laboracollective deployed (latest deploy 69fbeb54). Custom domain cpn.laboracollective.com set in Netlify, in DNS zone (NETLIFY-record CNAME-equivalent), SSL cert issued on *.laboracollective.com wildcard (valid through 2026-07-29). Default URL: cpn-laboracollective.netlify.app. Verified in entry 5.

Open questions for YC

Q1 — Provider Defense Pack: fold into CPN umbrella?

Row recM5VwdbaNA1H8jD "Provider Defense Pack" surfaced in the audit because the name contains "Provider," but it's legal/clinical defense docs — distinct concept from CPN-as-network. Did NOT merge. Confirm: should it fold in, or stay separate?

Q2 — Editorial Candidate Recruitment: needs its own PROJECTS row?

Brief named this row but it doesn't exist as a PROJECTS entry in Airtable. The "Define Aisha's scope" task from the legacy CPN row was tagged Phase 6 as a placeholder. Confirm: create a PROJECTS row under Phase 6, or is the Breana thread tracked elsewhere (TASK-only / Coda / Slack)?

Q3 — PROJECTS Status: add an "Archived" or "Merged" option?

Schema currently offers Active/Paused/Completed only. Used Completed + Name-prefix [MERGED] for the 3 archived source rows in this session. Confirm: want a real Archived/Merged option added to schema, or is the prefix-pattern sufficient? (Per Commandment VI, schema additions need YC's explicit greenlight.)

Q4 — How should this Living Log be enforced? (raised 2026-05-05)

The 2026-05-05 audit (B2) showed 22+ CPN sessions ran in the six days after the Living Log was created and none appended. Adoption needs automation. Choose one: (a) a skill that auto-triggers on phrases "CPN", "Clinical Partner Network", "Doula Field Guide" and instructs the agent to read this file first, append on close — most portable across Cowork/Code/Dispatch; (b) a hook in settings.json on session start when CWD or subject mentions CPN — only works in CCD; (c) a CLAUDE.md instruction injected into every CPN-related repo — only fires when an agent reads the project root. My recommendation: (a) skill — but YC owns the call.

Q5 — Should we extend the audit to other devices? (raised 2026-05-05; corrected)

The 262-session count covers Cowork session JSONs on this Mac only. Cowork is desktop-only (no cloud version exists — Cowork web is not a product); each Mac stores its own session JSONs locally. Confirm: have you run Cowork on any other device? If yes, the audit needs to run on that machine too. If no, this Mac's catalog is complete. (Previous version of this question incorrectly referenced "cloud Cowork" — Anthropic's cloud product is Claude Code on the web, a developer tool, separate from Cowork.)

Q6 — Pricing reconciliation: who moved CPN from $97/$197 to $35/$65/$129? (raised 2026-05-05)

The salvage audit (entry 3) surfaced two sole-copy files at yc-ops-hub/assets/cpn-network/ from April 2 with locked decisions: D10 set CPN subscription at $97/yr Member, $197/yr Pro; D2 set partnership tiers at $500/quarter (Tier 2) and $2K-5K/quarter (Tier 3). The 2026-05-02 reconciliation deck (PR #14) replaced these with $35/$65/$129 monthly Open Pathway and an all-free 5-tier Invited Partner structure — with no "superseded" annotation. Confirm: was the May 2 pricing your call, or did the agent make it on May 2 and silently overwrite April 2? Until this is answered, both numbers are technically "canonical" depending on which file an agent reads first. (See deck slide 6 + slide 14.)

Q7 — Tier framework: 3-tier (your original) vs 5-tier (May 2)? (raised 2026-05-05)

Your original CPN Design Document at ~/Documents/AI Agent Inbox/CPN_Networks_Documents/CPN_Design_Document.docx ("Prepared by Dr. Yamicia Connor · April 2026 · INTERNAL — PRE-LAUNCH") defines a clean 3-tier model: T1 Clinical Reviewer (~2 hrs/mo) · T2 Contributing Partner (~4-6 hrs/mo) · T3 Strategic Partner (ongoing). The May 2 reconciliation deck has a 5-tier Invited Partner structure (Advisor / Contributor / Partner / Strategic / Institutional). Confirm: was the 5-tier expansion your call? If yes, the original 3-tier should be archived with rationale. If no, the May 2 deck needs revision. (See deck slide 3.)

Sources of truth (canonical links)

Airtable (system of record for projects/tasks/decisions/reviews)

Drive (canonical content storage)

Coda (long-form CPN documentation)

Code + deploy

Slack

Drive snapshot — Cross-Agent Working Docs (added 2026-05-05)


Agent updates (chronological — most recent first)

2026-06-27 Claude · Code (Opus 4.8, remote/web session) Closeout of the submissions + community-data work (entry 7): merged + deployed, wired Netlify→Airtable mirroring, and staged the team comms. NOTE: Slack and Airtable MCP writes were unavailable this session (approval prompt cannot render in the headless remote run) — the #yc_log post, Ayesha DM, and Airtable PROJECTS/Build-Quantum updates are staged below for YC or an interactive session to execute.

What shipped (live)

Base decision

Next steps (owner)

Blocked this session (need YC / interactive session)

Staged #yc_log message (paste-ready)

✅ CPN-001 · Submissions funnel + Community Data — SHIPPED & LIVE · 2026-06-27 Built + deployed on cpn.laboracollective.com (Netlify cpn-laboracollective, git-linked). PRs #4 (pages) + #5 (Airtable fn) merged; deploy 6a400c8e live. Fold 1 — Call for Submissions (articles + voice notes): /submit/ (form yemaya-submission, ?src= attribution); campaign pages /campaigns/clinicians, /campaigns/community, /campaigns/writers; /internal/outreach/ paste-ready copy. Fold 2 — Community-level data (conversation, not a pipeline): /community-data/ (form yemaya-community-data; NOT a medical intake). Plumbing: Netlify fn submission-created mirrors both forms → Airtable Editorial Pipeline base (appi63sF9wC7M0lbM); self-provisions Submissions — Inbound + Community Data — Interest tables; AIRTABLE_API_KEY + base id set; both forms registered. Next: [YC/Ayesha] test 1 submission + 1 signup to confirm Airtable write + schema-write scope; [Ayesha] triage Submissions — Inbound + start outreach; [YC] optional form email notifications; [Decisions] community-data home + intake-vs-QC promotion.

Staged Ayesha DM (paste-ready)

Hi Ayesha — looping you in on the CPN build YC and I just shipped on cpn.laboracollective.com: • /submit/ — public call for articles + voice notes (any audience: clinicians, doulas, writers, patients) • /campaigns/clinicians, /campaigns/community, /campaigns/writers — targeted landing pages feeding /submit • /community-data/ — consent-first "start the conversation" interest page (not a medical intake) • /internal/outreach/ — paste-ready email + social copy per audience, ready to run Submissions auto-mirror into Airtable (Editorial Pipeline base) → "Submissions — Inbound"; community signups → "Community Data — Interest." Where you'd come in: (1) triage incoming submissions in Submissions — Inbound; (2) kick off outreach with the /internal/outreach/ copy; (3) could you send one test submission so we confirm the Airtable mirror is writing? Full details in #yc_log. — via YC's Claude

Files created or modified

For next agent / YC

2026-06-27 Claude · Code (Opus 4.8) YC: (1) start inviting people to submit articles — journals/columns — with campaigns targeting all demographics so the audience grows broadly; people can submit voice notes and/or articles. (2) start moving forward on community-level data / inviting patients to contribute, "or at least start that conversation." YC also asked for the outreach copy. Built the public submission funnel + a light community-data page + paste-ready campaign copy.

Session purpose

Two-fold ask. Fold 1 — submissions: open a public "Call for Submissions" that accepts written pieces AND voice notes, framed to invite contributors across every demographic (clinicians, birth workers, journalists, patients/community), plus demographic-targeted campaign landing pages and ready-to-paste outreach copy. Fold 2 — community data: a light "start the conversation" page introducing community-level / patient-contributed data with an interest form (explicitly NOT a medical intake yet). Confirmed scope with YC via question prompt before building: Fold 2 = light page; Fold 1 = submit page + campaign pages + outreach copy.

What shipped

Decisions made

Blockers raised

Open questions raised

Sources read

Files created or modified

For next agent

2026-05-06 Claude · Code (Opus 4.7, 1M context) Continuation of entry 5 — YC said "yes" on Q10 (push redirect) and "let's move to Phase 2 today." Shipped Phase 2 /internal/ Codex workspace + closed the remaining Phase 1 items.

Session purpose

Pick up from entry 5's three-item ask. YC's reply: redirect (yes), PR #24 merge (yes), move to Phase 2 today. Trilogy essay URLs are not coming as plain links — YC plans to republish all three essays in audiovisual format (ElevenLabs voice + imagery, LinkedIn + Substack versions, full AV experience on the website). Plus a fourth essay about Yemaya itself. That's a separate workflow — flagged for AV essay skill creation. This entry covers the closeouts + Phase 2 build.

What shipped

Decisions made

Blockers resolved

Blockers carried forward / new

Open questions raised / carried forward

For YC (consolidated ask)

For next agent

Sources read

Files created or modified

2026-05-06 Claude · Code (Opus 4.7, 1M context) Pick up from entry 4 signout — verify live site, reconcile DNS state vs. signout claim, close items programmatically, surface a single consolidated ask for YC.

Session purpose

Continuation of the 2026-05-06 Yemaya site rebuild session (Entry 4). Entry 4's signout flagged DNS for cpn.laboracollective.com as the only manual YC step left and listed it as Pending #1 / Urgent. This entry verifies what's live, reconciles DNS reality against that claim, and surfaces what truly still requires YC.

What was verified

Blockers resolved

Blockers carried forward

Open questions raised / carried forward

For YC (consolidated ask)

For next agent

Sources read

Files created or modified

2026-05-06 Claude · Code (Opus 4.7, 1M context) Rebrand CPN site as Yemaya · The Codex, ship live, build application form, hand off to next agent.

Session purpose

YC wanted the CPN site rebuilt and deployed for media opportunities. Long working session: brand architecture, voice/structural framing through ~10 rounds of iteration, evidence-rich receipts section, application form, deploy, comprehensive handoff for next agent.

What shipped

Decisions made (design + brand)

Blockers raised

Open questions raised

Sources read

Files created or modified

For next agent

2026-05-05 Claude · Code (Opus 4.7, 1M context) Before doing source-of-truth restoration, identify what's worth salvaging from the 262-session catalog beyond what YC explicitly knows about.

Session purpose

YC opened a fresh CPN Project session and explicitly redirected the listed first task ("source-of-truth restoration") to a prior question: "is there anything in the 262 conversations that needs to be salvaged other than what I explicitly know about." Goal: scan the 262-session catalog (entry 2) for substantive content not already on either canonical surface (Living Log + 2026-05-02 reconciliation deck), so that any subsequent restoration captures everything in one pass.

What shipped

What the audit found (top 6 HIGH-value items)

5 MEDIUM-value findings (in deck slides 8-12)

Decisions made

Blockers raised

Open questions raised

Sources read

Files created or modified

For next agent

2026-05-05 Claude · Code (Opus 4.7, 1M context) Surface every prior CPN conversation across Cowork / Code / Dispatch — YC believed there were "almost a dozen"; reality is ~262.

Session purpose

YC: "I have had almost a dozen conversations across Claude Cowork, Code, and Dispatch regarding CPN. I need you to help me surface those conversations and what was discussed." Goal was to inventory all prior CPN-related Claude work across surfaces so YC can see the full corpus and so future agents can stop re-deriving context from zero.

What shipped

What the audit found (the headline numbers)

The systemic finding (raised as B2)

The Living Log was created 2026-04-29 specifically to make CPN agents build on each other. Between Apr 30 and May 5, ~22 Cowork sessions that mention CPN ran on this machine (plus an unknown number on cloud + other accounts), and not one appended to this file. YC's reaction on seeing the count: "This is absolutely nuts. What this is telling me is that agents are doing things without ever looking at what other agents have done previously, and so we're not building on each other. We're just wasting resources." She is correct. The convention is unenforced and therefore unused. See B2 for what fixing it would require.

Decisions made

Blockers raised

Open questions raised

Sources read

Files created or modified

For next agent

2026-04-29 Claude · Cowork CPN umbrella merge + cpn.laboracollective.com build

Session purpose

YC directive (1) merge all CPN-related work into ONE umbrella project with sub-phases; (2) build cpn.laboracollective.com as a real deployed Netlify microsite consolidating CPN information; (3) explicitly formalize journalists + media as first-class CPN members ("always part of the plan, now formalized" — not a pivot).

What shipped

Decisions made

Blockers raised

Open questions raised

Sources read

Files created or modified

For next agent

Append template (for next agent)

When you finish your CPN session, copy this block, fill it in, and paste it as the FIRST entry in the "Agent updates" section above (most recent first). Update the "Current state at a glance" and "Active blockers" / "Open questions" sections if your work changed them.

Append this HTML block to the top of the updates section:

<div class="update-entry">
  <div class="update-meta">
    <span class="update-date">YYYY-MM-DD</span>
    <span class="update-agent">[Agent Name] · [Platform]</span>
    <span class="update-purpose">[One-sentence session purpose]</span>
  </div>

  <h4>Session purpose</h4>
  <p>[Why this session ran. What YC asked for or what triggered it.]</p>

  <h4>What shipped</h4>
  <ul>
    <li>[Concrete deliverable with location/ID]</li>
  </ul>

  <h4>Decisions made</h4>
  <ul>
    <li>[Decision + rationale]</li>
  </ul>

  <h4>Blockers raised</h4>
  <ul>
    <li>[Blocker title + what's needed]</li>
  </ul>

  <h4>Open questions raised</h4>
  <ul>
    <li>[Question for YC]</li>
  </ul>

  <h4>Sources read</h4>
  <ul>
    <li>[Airtable base/table IDs · Drive file IDs · Coda doc IDs · Slack channel IDs · file paths]</li>
  </ul>

  <h4>Files created or modified</h4>
  <ul>
    <li><code>[absolute path]</code> — [one-line description]</li>
  </ul>

  <h4>For next agent</h4>
  <ul>
    <li>[What's queued + any handoff notes]</li>
  </ul>
</div>
Reminder: in addition to appending your entry, update the always-current top sections (Current state, Active blockers, Open questions) so YC always sees the latest snapshot at the top.