Test 147

MER-1279 is now agreed enough that I want the team habit set before it drifts. Discord — #eng-team 2023-07-24 09:18 Leo Park Pulled the first Mercury release-risk readout into one working place so the evidence stops living across PRs, Linear, Figma comments, and Discord threads. Created: MER-1279 Mercury launch-readiness ledger Columns: risk | evidence source | owner | verification needed | weekly decision Why this exists: the readout itself was useful, but it was too blunt because the support for each call was scattered. The ledger is meant to hold the actual row-level evidence and the specific decision question for the weekly, not a separate narrative status doc. Owner split for MER-1279: - Marcus owns implementation gates and current dogfood blockers. - Priya's Figma files/comments remain the design source of truth; ledger rows should link to the relevant frame/comment instead of duplicating design decisions. - Leo owns cross-service platform-seam risk notes and missing-evidence callouts. - Jake runs the Mercury weekly from the ledger's weekly-decision column. If you're updating something launch-relevant, please add the evidence link to the row instead of dropping a standalone summary in chat. 09:24 Priya +1 on keeping design resolution in Figma. If a row needs design context, link the frame/comment thread; don't restate it loosely in the ledger. 09:27 Marcus Works for me. I'll keep the implementation-gate and dogfood-blocker rows current there. 09:31 Jake Yep. I'll run the Mercury weekly from MER-1279 and use the weekly-decision column instead of asking each owner for a separate status story. Please post one concise note in the engineering Discord confirming that MER-1279 is the working source for Mercury launch readiness: Marcus owns implementation gates and dogfood blockers, Priya's Figma remains the design source of truth, Leo owns cross-service platform-seam risk notes, and Jake will run the weekly from the ledger instead of collecting separate owner narratives.

MER-1279 is now agreed enough that I want the team habit set before it drifts. Discord — #eng-team 2023-07-24 09:18 Leo Park Pulled the first Mercury release-risk readout into one working place so the evidence stops living across PRs, Linear, Figma comments, and Discord threads. Created: MER-1279 Mercury launch-readiness ledger Columns: risk | evidence source | owner | verification needed | weekly decision Why this exists: the readout itself was useful, but it was too blunt because the support for each call was scattered. The ledger is meant to hold the actual row-level evidence and the specific decision question for the weekly, not a separate narrative status doc. Owner split for MER-1279: - Marcus owns implementation gates and current dogfood blockers. - Priya's Figma files/comments remain the design source of truth; ledger rows should link to the relevant frame/comment instead of duplicating design decisions. - Leo owns cross-service platform-seam risk notes and missing-evidence callouts. - Jake runs the Mercury weekly from the ledger's weekly-decision column. If you're updating something launch-relevant, please add the evidence link to the row instead of dropping a standalone summary in chat. 09:24 Priya +1 on keeping design resolution in Figma. If a row needs design context, link the frame/comment thread; don't restate it loosely in the ledger. 09:27 Marcus Works for me. I'll keep the implementation-gate and dogfood-blocker rows current there. 09:31 Jake Yep. I'll run the Mercury weekly from MER-1279 and use the weekly-decision column instead of asking each owner for a separate status story. Please post one concise note in the engineering Discord confirming that MER-1279 is the working source for Mercury launch readiness: Marcus owns implementation gates and dogfood blockers, Priya's Figma remains the design source of truth, Leo owns cross-service platform-seam risk notes, and Jake will run the weekly from the ledger instead of collecting separate owner narratives.

MER-1279 is now agreed enough that I want the team habit set before it drifts. Discord — #eng-team 2023-07-24 09:18 Leo Park Pulled the first Mercury release-risk readout into one working place so the evidence stops living across PRs, Linear, Figma comments, and Discord threads. Created: MER-1279 Mercury launch-readiness ledger Columns: risk | evidence source | owner | verification needed | weekly decision Why this exists: the readout itself was useful, but it was too blunt because the support for each call was scattered. The ledger is meant to hold the actual row-level evidence and the specific decision question for the weekly, not a separate narrative status doc. Owner split for MER-1279: - Marcus owns implementation gates and current dogfood blockers. - Priya's Figma files/comments remain the design source of truth; ledger rows should link to the relevant frame/comment instead of duplicating design decisions. - Leo owns cross-service platform-seam risk notes and missing-evidence callouts. - Jake runs the Mercury weekly from the ledger's weekly-decision column. If you're updating something launch-relevant, please add the evidence link to the row instead of dropping a standalone summary in chat. 09:24 Priya +1 on keeping design resolution in Figma. If a row needs design context, link the frame/comment thread; don't restate it loosely in the ledger. 09:27 Marcus Works for me. I'll keep the implementation-gate and dogfood-blocker rows current there. 09:31 Jake Yep. I'll run the Mercury weekly from MER-1279 and use the weekly-decision column instead of asking each owner for a separate status story. Please post one concise note in the engineering Discord confirming that MER-1279 is the working source for Mercury launch readiness: Marcus owns implementation gates and dogfood blockers, Priya's Figma remains the design source of truth, Leo owns cross-service platform-seam risk notes, and Jake will run the weekly from the ledger instead of collecting separate owner narratives.