Tool Gate · How it works
How the Enum & Status-Value Drift Sweep gate works
How the Enum & Status-Value Drift Sweep grades 5 fields' observed values against the set you declared allowed — SET CLOSED, VARIANTS PRESENT, or SET BROKEN — with a row-share gate that promotes a spelling variant to SET BROKEN past 5% of rows: one genuinely new value reads SETS BROKEN even with 99% of rows clean.
How the 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 — and then a gate that can only make it worse.
The 5 fields
| Field | Verdict |
|---|---|
| invoice.statefix first | SET BROKEN25,560 rows - partially_paid is out of set |
| lead.source_channel | SET BROKEN10,900 rows - 8% on a Referral variant, gate fired |
| ticket.status | VARIANTS PRESENT76,088 rows - 88 rows (0%) on an In Progress variant |
| order.status | VARIANTS PRESENT76,088 rows - 88 rows (0%) on an In Progress variant, twin of ticket.status |
| subscription.plan | SET CLOSED32,300 rows - every value in the declared set |
The verdict bands
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.
In the worked sample it reads SETS BROKEN — 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. The one thing to fix first: invoice.state - partially_paid is a genuinely new value, not a spelling variant; add it to the declared set or route those rows before trusting anything downstream..
Common questions
Can every field look survivable on the How the Enum & Status-Value Drift gate works and the company still read SETS BROKEN?
Yes. The roll-up takes the worst of 5 fields — never the average — then a worsen-only gate, the Row-share gate gate, escalates when trouble clusters. In the worked sample it reads SETS BROKEN because 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.
What is a worsen-only gate?
A dispositive rule that can only lower a verdict, never raise it. One fatal flaw overrides an otherwise-set of survivable lines, because a single disqualifying gap shouldn't hide behind an average of the healthy ones. The tool also names the one thing to fix first — here, "invoice.state - partially_paid is a genuinely new value, not a spelling variant; add it to the declared set or route those rows before trusting anything downstream.".
Grades the values you paste in. Not legal or compliance advice, and it connects to nothing on its own.
Embed this diagram
Free to share and embed with attribution (CC BY 4.0) — keep the link to redhub.ai.
Interactive — renders the live diagram
<iframe src="https://redhub.ai/visuals/tool/enum-status-value-drift-sweep.html" title="How the Enum & Status-Value Drift Sweep gate works — RedHub AI" width="760" height="1690" loading="lazy" style="border:0;width:100%;max-width:760px"></iframe>
<p style="font:14px/1.5 system-ui,sans-serif"><a href="https://redhub.ai/visuals/tool/enum-status-value-drift-sweep">How the Enum & Status-Value Drift Sweep gate works</a> — by <a href="https://redhub.ai">RedHub AI</a>, the AI that tells you when to doubt it.</p>Image + link — a static picture for any blog
<a href="https://redhub.ai/visuals/tool/enum-status-value-drift-sweep"><img src="https://redhub.ai/visuals/tool/enum-status-value-drift-sweep-share.png" alt="Diagram of the Enum & Status-Value Drift Sweep: five fields rolled up worst-not-average, a row-share gate, and the set reading SETS BROKEN on one out-of-set value." width="760" loading="lazy" style="max-width:100%;height:auto;border-radius:16px"></a>
<p style="font:14px/1.5 system-ui,sans-serif"><a href="https://redhub.ai">RedHub AI</a> — the AI that tells you when to doubt it.</p>
This is how Enum & Status-Value Drift Sweep works. More diagrams in the Visual Field Guide.