RedHub AI
How the roll-up gate works
How the Enum & Status-Value Drift gate works
This tool grades the values a field actually holds against the set you declared allowed. It reads 5 fields and rolls them into one verdict — the worst, never the average — then a gate that can only make it worse.
The 5 fields
A field reads SET BROKEN if any value truly falls outside the declared set - like invoice.state's partially_paid - or if variant rows alone clear 5% of the field's rows, which promotes a spelling variant into a second value your systems write regularly, even with zero out-of-set rows.
Why: Two fields hold VARIANTS PRESENT with a harmless spelling drift on well under 1% of rows. But invoice.state carries a genuinely new value - partially_paid - that was never declared, and lead.source_channel's Referral variant alone clears the 5% row-share gate. The sweep reads the worst field, not the average, so it's SETS BROKEN.
No single field is the crisis — the clustering is. The roll-up takes the worst, the gate escalates when trouble compounds, and it names the one thing to fix first. Grades the values you paste in. Not legal or compliance advice, and it connects to nothing on its own.