Stakeholder Gates
Active Workflows
Approval Chains
GRC rejection — v2.0 scope reduction required
4 participants · yesterday
Rejecting GRC and sending back to Build. All 4 quality metrics are failing — this needs a full engineering review, not incremental fixes. The v2.0 scope was too ambitious for the data quality we have.
All 4 metrics are failing on v2.0. I've rolled back the prompt changes from last week. @James Chen can you run the eval suite against the previous config and confirm we're back to baseline?
Agreed. Reduced scope is the right call. @Simon R. — please re-submit for GRC once 3/4 metrics are passing. I've booked the GRC slot for Apr 20. @Jamie L. FYI on the timeline.
Amendment progress — scope rework week 2
3 participants · yesterday
Reviewed the new prompt set. Logic looks significantly cleaner. Main concern: the reconciliation logic is still pulling from the same data source that was causing the 87% rate. That source has known freshness issues — we need to either fix the source or add a freshness check.