Before
Raw transcript
sample-transcript.md · Tue 19 May 2026, 9:31–9:52 AESTAuto-transcription export, unedited. Attendees: Priya Nair (EM, chair), Marcus Webb (Backend), Jenna Liu (Frontend), Tom Okafor (QA), Sofia Reyes (PM). Apologies: Dev Patel (on leave until Mon 25 May).
00:00:12PRIYAOkay, I can see everyone except — is Dev joining?
00:00:16JENNADev's on leave, remember? Back Monday.
00:00:19PRIYARight, yes. Okay, let's keep this tight, I've got a ten o'clock. Usual run-through on the billing migration, then Sofia has a comms item. Marcus, kick us off?
00:00:34MARCUSYeah, so. Backfill is at — let me check — eighty-two per cent as of this morning. The bulk of the historical invoices are across. But I hit something on Friday that I need a call on. Annual plans that came over from the old Stripe setup in, I think 2023 — some of them have duplicate invoice rows. Same invoice, two rows, slightly different metadata.
00:01:02PRIYAHow many are we talking?
00:01:05MARCUSAbout four hundred accounts. Not huge, but if we blindly port both rows, worst case the new service thinks there are two open invoices and —
00:01:14SOFIA[overlapping] — and we double-charge someone.
00:01:15MARCUS— potentially double-charge, yeah. And it's the annual folks, so big invoice values.
00:01:21PRIYAOkay. Options?
00:01:24MARCUSTwo. Fix it at the source, in the legacy biller, and re-run those accounts. Or dedupe in the migration script — keep the row with the newer metadata, drop the other one, and write every dropped row out to an audit log.
00:01:40JENNAIsn't the legacy biller frozen? I thought we agreed no more changes to it after March.
00:01:45MARCUSThat's my hesitation too. Touching it now means reopening change approval, and honestly the code in there is, uh, archaeological.
00:01:54PRIYAYeah, no. We are not reopening the legacy biller for this. Let's dedupe in the migration script. Keep newest, and log every skipped row somewhere Tom can audit. That's the decision unless someone objects. ... No? Good. Marcus, when can the patch land?
00:02:10MARCUSIf today goes okay — by Friday. Friday for the patched script plus the audit log.
00:02:15PRIYAFriday it is.
00:02:17TOMCan you flag me on the audit log format? If I'm the one verifying it, I'd rather not reverse-engineer a CSV at midnight.
00:02:24MARCUS[laughs] Fair. I'll loop you in on the PR.
00:02:28PRIYAJenna, frontend.
00:02:31JENNANew invoice UI is basically done behind the flag. Table view, PDF download, dunning banners — all working against the staging service. The only thing I genuinely cannot finish is the error states, because I still don't have final copy. I've got rough placeholder text in there and I am not shipping that to real customers.
00:03:08SOFIAThat's on me. Sorry, Jenna — the copy has been sitting in the review doc since Wednesday, legal wanted one change on the failed-payment wording. I'll have final error-state copy to you by Thursday. Thursday this week, I mean.
00:03:24JENNAIf I get it Thursday I can have the whole thing on staging with the flag on the day after. So Friday.
00:03:31PRIYALovely. Tom?
00:03:35TOMMixed week. The regression suite is green locally, but CI has been flaky since — [dog barking] — sorry, that's next door's dog. One sec.
00:03:55JENNAHe has opinions about billing.
00:03:59TOM[laughs] He's anti-migration. Anyway. CI's been flaky since Wednesday. It's not our code — it's the payment sandbox timing out. Roughly one run in four, the sandbox takes over thirty seconds to answer and the whole suite bails.
00:04:17PRIYAOne run in four? That's going to hurt during cutover week.
00:04:21TOMYeah, exactly. So, two things. Short term — the sandbox provider shipped a [inaudible 00:04:31] which defaults you onto the old API version, so tomorrow I'll pin our CI config to their v2 endpoint explicitly. That should kill most of the timeouts.
00:04:49TOMLonger term, we should agree a retry budget for the suite. Like — do we allow one automatic retry on network-class failures, or is that just hiding real problems? But that's a policy conversation, not a this-week thing.
00:05:06PRIYAAgreed — park the retry budget and bring it to the go/no-go, we'll have a week of data by then. Pin the version tomorrow.
00:05:17JENNAWhile we're paused — is the kitchen actually being renovated, or is that a rumour? Because the coffee machine has been living in the corridor for two weeks and it's starting to feel permanent.
00:05:29PRIYA[laughs] Facilities says the machine goes back in on Thursday.
00:05:33MARCUSPriorities sorted, then. Migration's a distant second.
00:05:36PRIYAOkay, okay. Back to it. Sofia — comms.
00:05:42SOFIAYes. So, the thing I've been flagging for two weeks: we owe the annual-plan customers an email before cutover. They're the ones with the duplicate-invoice risk Marcus just described, and they're also the ones who'll see the new invoice layout first. I want the email to land at least a week before we flip anything.
00:06:12SOFIATwo things. The affected account list — Marcus, can you get me that by Friday? The full annual-plan list, with the roughly four hundred flagged separately.
00:06:24MARCUSYep, Friday's fine — it falls out of the audit log anyway.
00:06:28SOFIAPerfect. Then I'll draft the email once I have the list. I'll aim to have a draft in the doc by the middle of next week. Legal will want a pass, so the earlier the better.
00:06:47SOFIAMe for content, legal for the compliance wording. And honestly I'd like Dev to glance at the header banner when they're back Monday — the current template still has the old logo lockup, it looks off next to the new invoice design.
00:07:04PRIYAFine, but don't let the banner block the send. Copy first.
00:07:11PRIYAOkay. Big one. Cutover. Are we still saying June second?
00:07:18MARCUSFrom my side — if the dedupe patch lands Friday and the backfill finishes over the weekend, yes. I'd want the following week for verification runs, but the second is a Tuesday, which is what we wanted. Nobody cuts over on a Friday.
00:07:36TOMI'm a conditional yes. Condition is a clean week of CI after I pin the sandbox version. If we're still seeing timeouts next week, I don't trust our own signals during cutover, and that scares me more than the migration itself.
00:07:53SOFIAAnd I need the email out by roughly the twenty-fifth or twenty-sixth to give customers a week's notice. Which means the list Friday, draft mid-next-week, legal Thursday-ish. It's tight but it works.
00:08:10JENNAStaging Friday, so yes. Two full weeks of the flag on staging before cutover. Comfortable.
00:08:17PRIYAAlright. Let's lock it: target cutover Tuesday the second of June. Go/no-go review Thursday the twenty-eighth — everyone in this meeting, thirty minutes, and Tom brings the CI numbers. I'll send the invite for the twenty-eighth today.
00:08:38SPEAKER 2Same. And if the audit log shows anything weird in the four hundred, I'll raise it before the twenty-eighth, not at it.
00:08:47SOFIAThanks, Marcus. That's exactly what I need for the email tone, actually — whether we say "we found and fixed" or "nothing changed for you."
00:09:01TOMYeah, quick but it matters. On-call paged me Saturday night — a customer invoice question escalated, and the runbook still points at the legacy biller dashboards. Whoever's on call during cutover is going to be flying blind. Someone should really update the incident runbook for the new service before we cut over.
00:09:24PRIYANoted, and agreed. I'm not going to volunteer anyone at nine-fifty on a Tuesday — I'll raise it in the channel today and we'll get a name against it this week.
00:09:39SOFIALast one from me, thirty seconds. Meridian — the account, not the person — asked again about EU tax-compliant invoice formatting. Second time this quarter. I know it's not this migration, I just don't want to keep losing the request.
00:09:56PRIYANot in this migration, correct. Park it — write it up and bring it to next quarter's planning. It's a real thing, it's just not a May thing.
00:10:06SOFIAParked. I'll put it in the planning doc.
00:10:09PRIYARight. Done in twenty-one minutes, which might be a record. Same time next week, and I'll see most of you at the go/no-go on the twenty-eighth. Thanks, all.
[END OF TRANSCRIPT — 00:21:14 elapsed. Recording tool paused during two silences totalling ~10 min; timestamps are speech-time offsets, wall-clock duration was 21 minutes.]
Abridged here for the demo page — the pack's sample-transcript.md contains every line.
After
Generated minutes
Minutes — Relay billing migration — weekly standup
Summary
The team confirmed the Relay billing migration remains on track for a target cutover of Tuesday 2 June 2026, with a go/no-go review on Thursday 28 May. Duplicate invoice rows affecting ~400 annual-plan accounts will be deduplicated in the migration script rather than by reopening the frozen legacy biller, with every dropped row written to an audit log for QA verification. Pre-cutover work was sequenced: the dedupe patch, the affected-account list and the staging deployment of the new invoice UI are all due Friday 22 May, and annual-plan customers will be emailed roughly a week before cutover. The incident runbook still points at the legacy biller and has no owner for the update — flagged as a high risk to resolve before the go/no-go.
Decisions
| # | Decision | Decided by |
|---|---|---|
| D1 | Dedupe the ~400 duplicate annual-plan invoice rows in the migration script — keep the newer-metadata row, log every dropped row to an audit log — rather than reopening the frozen legacy biller. | Priya Nair |
| D2 | Target cutover locked for Tuesday 2 June 2026; go/no-go review Thursday 28 May (30 min, all attendees, Tom brings the CI numbers). | Priya Nair |
| D3 | The customer-email header-banner review must not block the send; copy sign-off (Sofia content, legal compliance) comes first. | Priya Nair |
Action items
| # | Action | Owner | Due | Priority |
|---|---|---|---|---|
| A1 | Land the patched migration script with duplicate-invoice dedupe plus audit log. | Marcus Webb | 2026-05-22 | high |
| A2 | Loop Tom in on the migration-script PR to review the audit-log format. | Marcus Webb | — | medium |
| A3 | Deliver final error-state copy for the new invoice UI to Jenna (incl. legal's failed-payment change). | Sofia Reyes | 2026-05-21 | high |
| A4 | Deploy the complete invoice UI to staging with the flag on, once copy arrives. | Jenna Liu | 2026-05-22 | medium |
| A5 | Pin CI to the payment-sandbox v2 endpoint to stop the timeouts. | Tom Okafor | 2026-05-20 | high |
| A6 | Send Sofia the full annual-plan account list with the ~400 flagged separately. | Marcus Webb | 2026-05-22 | high |
| A7 | Draft the pre-cutover email to annual-plan customers ahead of legal review. | Sofia Reyes | 2026-05-27 | high |
| A8 | Review the email header banner on return from leave (non-blocking per D3). | Dev Patel | — | low |
| A9 | Send the calendar invite for the 28 May go/no-go. | Priya Nair | 2026-05-19 | medium |
| A10 | Raise any audit-log anomalies in the ~400 accounts before the go/no-go, not at it. | Marcus Webb | 2026-05-28 | medium |
| A11 | Update the incident runbook to point at the new billing service dashboards before cutover. | UNASSIGNED ⚠ | — | high |
| A12 | Raise runbook ownership in the team channel and get a named owner this week. | Priya Nair | 2026-05-19 | medium |
| A13 | Write up the EU tax-compliant invoicing request (Meridian) for next quarter's planning doc. | Sofia Reyes | — | low |
Discussion
Backfill progress and duplicate invoice rows
Backfill ~82% complete. Marcus found duplicate invoice rows on ~400 annual-plan accounts from the 2023 Stripe migration — porting both rows risks double-charging high-value customers. Fixing at source would reopen the frozen legacy biller. Outcome: dedupe in the migration script (D1); patch + audit log due Friday (A1).
New invoice UI (frontend)
UI complete behind the flag except error states, blocked on final copy held up by one legal change. Jenna will not ship placeholder text. Outcome: copy Thursday (A3); staging with flag on Friday (A4).
QA and CI stability
Suite green locally, but CI fails ~1 run in 4 since Wednesday — payment sandbox timeouts after a provider release defaulted CI to the old API version. Retry-budget policy judged not a this-week fix. Outcome: pin v2 endpoint Wednesday (A5); retry budget parked to the go/no-go (P1).
Pre-cutover customer communications
Annual-plan customers to be emailed at least a week before cutover. Marcus supplies the account list; Sofia drafts, legal reviews; banner review by Dev is non-blocking (D3). Outcome: list Friday (A6); draft ≈ 27 May (A7); banner non-blocking (A8).
Cutover date and go/no-go
Conditional yeses from every workstream — Marcus (patch + weekend backfill), Tom (a clean CI week after the pin), Sofia (email out by ~25–26 May), Jenna (two weeks on staging). Outcome: cutover locked 2 June (D2); go/no-go 28 May (F1); invite same day (A9).
Incident runbook currency
Saturday-night escalation exposed the runbook still points at legacy biller dashboards — on-call during cutover would be flying blind. Nobody volunteered in the meeting. Outcome: update needed but UNASSIGNED (A11); ownership being sourced via the channel (A12).
EU tax-compliant invoice formatting (Meridian)
Second request this quarter; real but out of scope for May. Outcome: parked to next quarter's planning (P2, A13).
Risks & blockers
- Duplicate rows on ~400 annual-plan accounts could double-charge customers — Marcus Webb, high. Mitigation: D1 + audit log + A10.
- CI failing ~1 in 4 undermines trust in signals during cutover week — Tom Okafor, medium. Mitigation: A5; cutover conditional on a clean CI week.
- Incident runbook points at the legacy biller; on-call flying blind — Tom Okafor, high. Mitigation: A12; the update itself unassigned (A11).
- Customer-email timeline has no slack (list 22 May → draft → legal → send by ~25–26 May) — Sofia Reyes, medium. See extraction notes.
Parking lot
- CI retry budget for network-class failures — deferred to the 28 May go/no-go with a week of post-pin data.
- EU tax-compliant invoice formatting (Meridian) — deferred to next quarter's planning.
Follow-ups
- Go/no-go review — 2026-05-28 — cutover readiness; Tom brings CI numbers.
- Next weekly standup — 2026-05-26.
- Billing migration cutover (target) — 2026-06-02.
Transcription & extraction notes
- [00:08:38] "SPEAKER 2" attributed to Marcus Webb: Sofia replies "Thanks, Marcus" immediately after, and the content concerns the audit log he owns.
- [00:04:31] inaudible segment: the specific sandbox-provider release was not captured; only its stated effect is recorded.
- A7 due date 2026-05-27 is approximate: "middle of next week" resolved per the date-resolution rules.
- Sofia's email timeline is internally tight (send ~25–26 May vs draft ~27 May, legal 28 May). Recorded as stated; owner should reconcile.
- A8 assigned to Dev Patel in absentia, not yet acknowledged — owner confidence "inferred".
- A11 is UNASSIGNED — agreed as needed but nobody took it; ownership being resolved via A12.
- Duration (21 min) from the transcript footer's explicit wall-clock statement; speech-time timestamps end at ~00:10:20.
- Off-topic chatter (kitchen renovation / coffee machine, a neighbour's dog) was omitted from the minutes.
Excerpt of sample-output.json — the same facts as the minutes, machine-readable and validated against output-schema.json. Note the owner-confidence and due-date-source fields, and the verbatim evidence quotes.
{
"meeting": {
"title": "Relay billing migration — weekly standup",
"date": "2026-05-19", "start_time": "09:31", "timezone": "AEST",
"duration_minutes": 21, "meeting_type": "standup",
"attendees": [ …5 attendees with roles… ],
"apologies": ["Dev Patel (Product Designer) — on leave until Monday 25 May"]
},
"summary": "The team confirmed the Relay billing migration remains on track…",
"decisions": [
{
"id": "D1",
"decision": "Duplicate invoice rows on the ~400 affected annual-plan accounts will be deduplicated in the migration script — keep the row with the newer metadata, drop the other, and write every dropped row to an audit log — rather than fixing the data in the legacy biller.",
"rationale": "The legacy biller has been frozen since March; touching it would reopen change approval on very old code.",
"decided_by": "Priya Nair", "unanimous": true
}, … D2, D3 …
],
"action_items": [
{
"id": "A1",
"task": "Land the patched migration script with duplicate-invoice deduplication (keep the row with the newer metadata, drop the other) plus an audit log recording every dropped row.",
"owner": "Marcus Webb",
"owner_confidence": "explicit",
"due_date": "2026-05-22",
"due_date_source": "resolved_relative",
"priority": "high",
"source_quote": "If today goes okay — by Friday. Friday for the patched script plus the audit log."
},
…
{
"id": "A11",
"task": "Update the incident runbook to point at the new billing service dashboards before cutover.",
"owner": null,
"owner_confidence": "unassigned",
"due_date": null,
"due_date_source": "none",
"priority": "high",
"source_quote": "Someone should really update the incident runbook for the new service before we cut over."
}, … 13 items total …
],
"risks": [ …4 risks with severity + mitigation… ],
"parking_lot": [ …2 parked topics… ],
"follow_ups": [ …3 scheduled events… ],
"extraction_notes": [
"[00:08:38] 'SPEAKER 2' attributed to Marcus Webb: Sofia replies 'Thanks, Marcus' immediately after…",
"A11 (incident runbook update) is UNASSIGNED — the work was agreed as needed but nobody took it…",
… 8 notes total …
]
}
The full, unabridged JSON (17 KB, schema-valid) ships in the pack as sample-output.json.