The JUSTYPE language
Understand the constrained language that turns supported phrases into structured rules.
Documentation index
Most launch interfaces expose fields. JUSTYPE exposes a constrained way to describe market behavior, then shows the exact structured interpretation back to you.
Constrained, not magical
The current language is a deterministic collection of accepted patterns backed by a manual rule catalog. It is intentionally narrower than arbitrary English. That constraint makes the result reviewable: a phrase either produces known typed rules or stays unrecognized.
JUSTYPE does not generate Solidity, execute the prompt, or ask an AI model to invent contract logic.
One instruction can compose several families
Take 4% on sells. Use half of sell fees to buy back MOG. Send 25% of sell fees to stakers. Burn everything bought back. Lower the sell fee from 4% to 1% after 7 days. Limit sells to 0.5% of supply. Reward every 100th buyer with 1,000 MOG.
This example becomes seven typed rules spanning a fee, two fee destinations, an explicit burn, a time change, a sell limit, and a buyer milestone. “Split” describes the relationship among the fee and destination rules; it is not a seventh opcode or a standalone rule type.
Accepted patterns are examples
The reference lists phrases covered by the current parser. Small wording changes may still match, but the list is not a promise that any sentence with the same meaning will be understood. Use explicit values and inspect the result.
For behaviors that are difficult to express, choose a structured behavior from the catalog and edit its values directly.
The sentence is not the source of truth after parsing
The saved normalized rule objects are the source for the current frontend. If you manually change a rule after typing, the Behavior Score follows the edited rule object. This avoids treating prose as executable state.