Lucidum Reverse Engineering

Build field knowledge from Lucidum exports. Test valid field/operator combinations.

69 confirmed
216 inferred
285 total fields
43 operator rules
1 imports
24.2% reverse engineered

Upload Lucidum Export

Drop a .json file exported from Lucidum. The system will parse every condition to learn field types, operators, and valid combinations.

📂

Drag & drop a Lucidum .json export here, or click to browse

Condition Builder

Build and validate Lucidum conditions interactively. Only valid operator/value combos are allowed.

 

Field Registry

Field Name searchFieldName Type Base? Status

Fields Not in LDG

Base fields discovered from 560 live Smart Labels that do NOT exist in our LDG catalog. These are Lucidum-native fields we can use in conditions.

searchFieldName Friendly Name Type Operators Usage In LDG? In field_map?

Str Type Fields (Smart Label Outputs)

These 44 fields use the Str type (distinct from String). They are Smart Label output fields — lowercase names representing conditions produced by other labels. Operators: == and match.

Field Name Operators Usage

Extra_Data Key Catalog

Vendor-specific Extra_Data keys discovered in live labels. Used as Extra_Data > Key match <key_name> > Value match <value>.

Operator-Type Matrix

Every confirmed type+operator combination with usage counts from 560 live labels. Darker = more frequent.

Embed_List Patterns

Known parent-child structures for Embed_List fields. These define how nested conditions are built.

Open Questions & Unknowns

Items to investigate in future reverse engineering sessions.

Explored API Endpoints

Lucidum API endpoints we tested and their results.