You said you want to deliver these this week. Re-verified against the relationship record today, not carried over from the earlier list.
Sources read: the Aug 7 Otter transcript, the Aug 7 recording analysis, the Aug 4 strategy debrief, and communication-log.md in ~/relationships/kristin. Last verified: 2026-08-11.
Read this first
The list was six. It is actually four, plus one check.
Two corrections came out of re-reading the record, and both change what you have to do.
Cloudflare Stream is not yours. It is hers.
Corrected
The earlier list had this waiting on you. The raw Aug 7 transcript says the opposite. Your words: "getting your Cloudflare account set up to accept video... I did it on my account for staging." You already did the staging side. What is outstanding is Kristin setting up her own Cloudflare account, which you asked her to do that day.
The record disagrees with itself: communication-log.md lists this as yours, the recording analysis and the transcript both put it on her. The transcript is the primary source, so it wins.
Your part, and it is smallSend her the setup steps so she is not blocked on figuring it out. That is a short message, not a build task.
The platform split is not a decision. It is already decided.
Build work
It was framed as a business decision waiting on you. It is not. The shape was settled on Aug 4 and reaffirmed on Aug 7, with Kristin saying "Okay. Yep. I agree with that." Marketplace is public for Explorers, Learning Lab is creator-only. The Aug 4 action item reads "Ethan: implement the technical platform split". Nothing is waiting on your judgment here. It is waiting on the build.
This matters because it moves the item from your decision queue into your build queue, and it is step one of the four-step launch sequence you both agreed to.
Waiting on you — 4 items
In the order that unblocks her fastest
Ordered by what releases Kristin to do her own work, since the launch sequence you agreed to runs through you first.
1Platform split — Marketplace vs. Learning Lab
Build
Step one of the agreed four-step launch sequence: you split the platform, then she populates both spaces, then the landing page routes people, then founding creators get invited. Every other launch task sits downstream of this one. Your Aug 5 email told her it is "not built yet", so she is not surprised, only waiting. Spec detail from Aug 7 worth not losing: guests do not submit gratitude, to remove friction for people who are not paying.
Blocks: everything. Her content population, her landing page, the founding-creator invites, and the launch itself.
What you doNothing to decide. Route it to joyos-labs-director as a build. Open since Aug 4, 7 days.
2Explorer interface mockups
Artifact
You committed to these on Aug 7, verbatim: "I'll do some mockups." She answered "That would be great." The shape is already settled, so there is nothing left to figure out: the Explorer surface reuses the Creator Studio look and feel, with a top bar for community and members, and Explorer-visible items only. Not a separate product.
Blocks: her master landing page, which has to route Explorers and Creators differently and cannot be designed until the Explorer side has a face.
What you doNothing to decide. Route to joyos-labs-director, which should run it through the mockup path rather than hand-building components. Open since Aug 7, 4 days.
3Stripe Connect payout tax research
Research
Committed Aug 4 (you said you would look at it "after 10pm" that night). It is now a much smaller job than it was. On Aug 7 Kristin relayed her accountant's read: the Stripe Connect payout structure itself is not a tax problem for JoyOS, because the money passes through rather than landing as revenue. The only genuinely open piece is 1099-K reporting once payout volume gets high enough to trigger it, and whether Stripe Connect's built-in reporting covers that automatically.
Blocks: item 4 below, which is the email that carries this answer to her accountant.
What you doNothing to decide. One narrow research question, then written up. Pairs naturally with item 4 in a single sitting. Open since Aug 4, 7 days.
4Accountant-facing Stripe Connect / 1099-K summary
Draft, then you send
Committed Aug 7. You offered to write something Kristin can forward straight to her accountant explaining how Connect payouts and 1099-K reporting work. It should confirm the part her accountant already got right, and answer the 1099-K threshold question he flagged.
Blocks: her accountant signing off, which sits upstream of turning real payouts on.
What you doIt gets drafted for you and left as a draft. Sending is yours, and nothing goes to Kristin or her accountant without you pressing send. Open since Aug 7, 4 days.
Do not repeat this to her yet
The production promotion is still unverified
It was flagged unverified on the earlier page. It is still unverified, and I am saying so rather than repeating it as fact.
Did the gated batch actually ship?
Unverified
Your Aug 5 email told her a batch was "ready and gated for production, waiting on one final check", explicitly not live. Whether it has gone out since could not be established here: the joyos-labs directory has no git metadata to read branch truth from, so which tree is actually serving production cannot be determined without the agents that own that question.
Checked and came back empty: no readable git remote state at that path, so no branch comparison was possible. That is a real limit, not a conclusion that it did not ship.
What you doDo not tell her it is live, and do not tell her it is not. Route the check to joyos-labs-prod-promotion before your next contact with her. If it did ship, say plainly that it went out rather than re-announcing the fixes she already knows about.
Verify before it appears in any message to her
Honest sequencing
Four this week is realistic. Six was not.
You have ELP shipping, a proposal going to Russ, and client delivery obligations in the same week.
The platform split is the only one that actually matters this week. It is the single item holding up her entire side of the launch, and it is the largest of the four. If exactly one thing lands, it should be this.
The Explorer mockups are second, and they are cheap relative to their leverage: they release her to build the landing page, which she named as her own next step.
The tax research and the accountant email are one sitting, not two. The research question narrowed to a single point after her accountant's Aug 7 read, and the email is the delivery vehicle for that answer. Doing them together is roughly an hour of your attention, mostly on approving the draft.
What I would not promise her this week: the platform split landing fully finished and verified on production. It is a real build sitting behind an unverified promotion pipeline, in a week where three other clients want your time. Telling her it will be done and having it slip is worse than telling her it is in progress and showing her mockups on Friday.
The honest weekSplit in flight, mockups delivered, accountant email sent, Cloudflare instructions passed to her. That is four things she can feel. Promising six and landing two reads as a slower week than promising four and landing four.