At 07:10 I measured 1.8 NTU on the pour-over, which exceeds our informal ≤1.0 NTU acceptance, so I logged an OOS and opened a CAPA against the filter. Triplicate sips showed 3.2% RSD and an aroma drift outside control limits; do I revalidate the grinder or implement a more aggressive pre-rinse cycle?
At 07:10, flush the line 30 seconds and pre-rinse [redacted]; monitor “1.8 NTU” drop. @beansQA thoughts?
I’ve had luck wiring Filestage’s “Approved” webhook to a Jira Automation incoming webhook to auto-transition to Ready for Dev, add the Filestage timestamp in a comment, and paste the Figma Dev Mode named version link we create at handoff to “freeze scope” (https://support.atlassian.com/cloud-automation/docs/triggers/#Incoming-webhook). Small caveat: set a second rule to reopen to In Review if the Filestage status flips back — does that fit your setup, or are you on Marker.io?
Extend bloom to 45s, discard first [redacted], and recheck ‘1.8 NTU’ at 93°C — did aroma drift tighten?