Your engineering process, followed by Claude, Cursor, Codex, and OpenCode Claude

I read your saved roadmap — 11 tasks still open across three milestones. Here's the honest split.

Blocked until billing is live: webhook signature verification and the refund + revocation runbook. Neither can be validated without real payment events.

Safe to start now: API contract tests, staging load test with alert thresholds, and a draft launch checklist. None of those need production cards.

Needs production + real payments: end-to-end purchase smoke and final go-live sign-off. Schedule those after redirects are wired.

One thing the plan wording glosses over: it says M5 blocks M6, which is true for billing policy, but you can still ship the site and wire redirects first — that unblocks a week of parallel work.

I'd tackle it in this order: contract tests → deploy + redirects → billing hardening in parallel → E2E checklist → go-live. Contract tests are the fastest win and they de-risk the SDK work you flagged last session.

Want me to mark contract tests in progress and draft the parallel track?

I searched your indexed library — three docs mention EU subprocessors. You didn't need to re-upload anything; they're already on your machine from when you indexed them.

Your EU residency policy is the source of truth: customer PII stays in EU regions, and any metadata subprocessors need written approval before go-live. That's in the policy PDF you saved under policies/.

Nexus's SOC2 is where it gets interesting. Primary storage is in Dublin — that passes residency. But the subprocessor table lists US analytics for usage events, which is probably the gap you're feeling.

Your internal legal FAQ backs that up: when residency passes but a subprocessor sits outside the EU, route it to legal for an exception — don't assume the vendor is cleared.

So Nexus is conditional: fine on storage, not fine on analytics metadata without a legal call.

Want a one-page summary for legal with the exact passages cited?

I pulled your subscription export and applied the churn_v3 filters you saved after the CFO call — enterprise trials under 14 days are excluded, logo churn uses paid seats only.

North America still leads at 32%, Europe is close behind at 29%, but Latin America is the fastest-growing region at 259% YoY. On products, AI Copilot is the standout — it went from $2.8K to $189K in a single year.

Security Suite remains the revenue leader overall; Workflow Auto is the one to watch on the downside — it dropped sharply in 2026. Collab Hub still has the highest margin if you need a profitability slide.

Want a PDF with the full ranked table and a delta footnote for the board deck?

I compared your midterm scan against the lecture notes you indexed — here's what actually cost you points.

On question 7 (∫₀² x·e^(x²) dx) you set up the integrand but stopped before finishing substitution. Your work shows you recognized e^(x²) inside the integral — you just didn't complete the u-sub.

Your Week 5 notes say: when you see f′(x)·g(f(x)), let u = f(x). Here u = x², so du = 2x dx — you needed a ½ factor before integrating e^u. Prof. Chen's shortcut for this pattern is in Lecture 6, slide 14, which you also have indexed.

Same slip on Q11 and Q14 — all three are substitution, not integration-by-parts. That's roughly 18 points you can recover with targeted practice, not a full re-read of the unit.

I can generate five drill problems on substitution only, matched to the notation style you saved. Or a quick practice test if you want exam conditions.

Start with drills, or a timed practice test first?

Morning — I loaded your last session and the structured context orkai keeps for you.

You set an explicit rule: one-line commit message, only after unit tests pass. I learned that you open with a risk pass before Friday releases and that we're on the auth middleware change from yesterday.

Nothing to re-explain — that's already in context before you ask anything.

All green. Per your rule, here's the one-liner:

Scope matches what we discussed yesterday — session-scoped key only, no global bleed. If you widen it, the commit message should say so.

Stage it, or adjust the scope first?