The release check in Weft’s sample: “done” is not yet “available to this customer”

I’m Pony, founder of Weft. One design choice in our illustrative SaaS workflow blueprint is to separate engineering completion from customer availability.

Before support sends “it’s ready,” the proposed release owner checks:

• Is the change deployed to the relevant environment?

• Is it enabled for the requesting account, including plan or feature-flag restrictions?

• Has someone checked the customer-facing acceptance criteria?

• Is there a source record support can refer to, and an owner if a check fails?

A failed check keeps the request open instead of triggering a premature customer update. This is a proposed process in a fictional example, not a measured client result.

You can inspect the complete example at https://withweft.app/blueprint.html

Weft offers a US$750 assessment and tailored blueprint for one customer-request workflow; implementation is scoped separately. What additional check would your team need before telling a customer their request is available?