Supported primitives
Learn how fee, split, destination, time, limit, and milestone map to the real rule model.
Documentation index
Families help humans scan the language
Primitive families are an editorial map over the implementation. They help answer “what kind of behavior is this?” without forcing a reader to memorize 21 internal type names.
- FEE
- A percentage configured on buys or sells, with optional duration or large-trade condition.
- SPLIT
- How one collected fee is divided among allocation rules. It is a relationship, not a TokenRule type.
- DESTINATION
- Where configured value is intended to go: buyback, burn, holders, stakers, liquidity, or liquidity providers.
- TIME
- When trading or another behavior begins, ends, or changes.
- LIMIT
- A configured boundary on trade size, wallet size, frequency, access, liquidity removal, or a protection condition.
- MILESTONE
- A buyer count or interval that triggers a configured reward in the model.
Families are not execution promises
Some families contain rules that are more completely parsed than others. Sell fees and allocation splits have focused normalization and validation. Access and volatility rules can be represented, but do not have connected lists, balances, or price oracles. The rule reference states the boundary for each type.
Composition happens through shared fields
Allocation rules compose through a shared fee source such as sellFee. A buyback and staking reward can each own 50% of that source. A burn composes with a buyback only when it explicitly says its source is the buyback. A time rule names the fee side it changes.
Other relationships are less formal today. A timed activation stores a human action string, not a rule ID, and multiple access restrictions are not reduced into formal boolean logic.