Normalization and validation

Normalization makes equivalent values comparable

Rules are enabled by default, exact structural duplicates are removed, and stable IDs are assigned. Relative fee shares become effective trade percentages when the source fee is known.

SELL_FEE        2%
BUYBACK_SHARE   50% OF SELL_FEE
EFFECTIVE       1% OF TRADE

Errors block review

Fee range

A buy or sell fee below 0% or above 25%.

One oversized allocation

One allocation asks for more than 100% of a collected fee.

Allocation total

Several active allocations from one fee source total more than 100%.

Conflicting fee change

Two rules change the same fee side at the same time to different percentages.

Warnings require judgment

A maximum buy above the maximum wallet produces a warning because one allowed buy might create a disallowed holding. A rule with missing fields also produces a warning; incomplete rules block local creation even though they are shown for editing.

Unsupported instructions stay unsupported

An instruction that matches no known pattern appears as unrecognized text. It blocks review until you rewrite or remove it. That behavior is safer than inventing a rule from a sentence the parser did not understand.

What “valid” cannot prove

Most non-fee numeric fields do not have domain-specific upper bounds today. The editor prevents negative numbers, but that is not the same as validating a realistic or secure configuration.