How JUSTYPE works

1. Instruction

JUSTYPE starts with the exact text you enter. It normalizes punctuation and whitespace, then separates lines and sentence-ending punctuation into instructions. It does not send the text to a general-purpose language model.

2. Parse

The parser checks supported patterns in a fixed order. A matching phrase creates one or more typed candidate rules. A sentence can also use limited context, such as the most recently seen fee source, but the parser does not infer arbitrary intent.

3. Normalize

Normalization enables rules by default, removes exact structural duplicates, assigns stable IDs, and calculates effective percentages. For example, half of a 2% sell fee becomes a 1% effective allocation while retaining its 50% share-of-fee meaning.

If an absolute allocation needs a buy or sell fee source and none exists, the normalizer can infer a fee of the required size. The UI tells the user when it did so.

4. Validate

The validator checks a deliberately limited set of errors and warnings. It rejects fee percentages outside 0–25%, over-allocated fee sources, and contradictory fee changes at the same time. It warns about incomplete details and a maximum buy larger than a maximum wallet.

5. Canonical frontend rules

The normalized TokenRule[] is the frontend’s current canonical configuration. Review, local storage, rule descriptions, trade arithmetic, and Behavior Score consume these objects. There is no current contract consumer.

6. Visualize

Behavior Score groups active fee sources with their destinations, preserves explicit burn relationships, and renders time, limit, milestone, access, liquidity, and protection rules. Disabled rules disappear from the score.