Storm parity: validation follows the supplied loader and RE2 specification. Match previews use a documented JavaScript approximation; production loader behavior and exact FUZZY semantics still require confirmation in Storm.
Storm taxonomy workspace
Build a Storm-ready taxonomy.
Start with seed phrases or review an existing term file.
Step 1 · Create
Start from seeds
Add a topic and a few phrases. We will build the first draft.
Advanced generation options
Ambiguous seeds - anchor before emitting
These seeds are ordinary English words; standalone patterns fail the reasonable-person test. Anchor each one (spec techniques 1–3), or include it anyway and accept the risk.
View generated rows
| term_id | type | term_text | coverage |
|---|
Step 2
Review with confidence.
See what is ready, what needs attention, and why.
Review a taxonomy
Upload a Storm file or continue with your current draft.
Composition
What needs attention
Safe cleanup options
Open row editor
| severity | term_id | type | term_text | tag | finding |
|---|
Step 3
Test it. Then ship it.
See what matches before you export.
Try a sample
Matches
Run a labeled evaluation
View row-level evidence
| verdict | term_id | type | term_text | pos hits | neg hits | example |
|---|
Ready when validation passes
Export package
Download the Storm CSV or keep the audit trail.