You describe what a token should do. JUSTYPE turns the supported parts of that instruction into structured rules, checks what it can, and shows the result as a Behavior Score.
It makes a complex market configuration easier to describe and easier to inspect.
Most token tools begin with parameter fields. JUSTYPE begins with the behavior: take a fee on sells, route part of it to buybacks, lower it later, or limit one trade. The current product recognizes supported phrases and turns them into a typed frontend configuration.
That configuration is useful before execution because it forces an ambiguous idea into explicit values and relationships. Today, finishing the flow creates a local profile in your browser—not a token contract or public market.
The exact sentences you write
→Supported phrases become typed candidates
→IDs, shares and limited defaults settle
→Implemented errors and warnings run
→The saved frontend specification
→The same active rules become visual
The parser does not execute prose. It recognizes supported patterns, preserves anything it does not recognize, then normalization and validation create a reviewable rule set. If a sentence is unsupported, JUSTYPE asks you to fix it instead of making something up.
A primitive is a human family such as FEE, TIME, or LIMIT. A rule is the typed object that carries actual values. SPLIT is a relationship among a fee and its destination rules; it is not an internal opcode.
The implementation supports 21 structured rule types and 28 manual catalog choices. Support here means the frontend can represent and display the behavior. It does not mean a JUSTYPE contract enforces it.
Take 2% on sells. Use half of sell fees to buy back MOG. Send the rest to stakers.
sellFeeTake 2% when someone sells.buybackUse half of the sell fee to buy MOG.stakingRewardsSend half of the sell fee to stakers.Frontend configuration example. No onchain output or transaction is implied.
The score is generated from the active normalized rule objects. It shows what the saved configuration says: source, percentage, destination, timing, limits, and milestones. It is not a safety rating, audit, market forecast, or execution proof.
No JUSTYPE contract, hook address, or live execution path exists in this repository.
Uniswap v4 is relevant because optional hooks can run custom logic around pool actions. JUSTYPE documents that as a future direction. No JUSTYPE hook, contract address, live wallet path, trade, stake, fee route, or indexer exists today.
01It does not generate or execute Solidity from your sentence.
02It does not deploy a token or Uniswap v4 pool.
03It does not connect a wallet or submit transactions.
04It does not verify that a configuration is economically safe.
05It does not publish internal fixture markets or activity as real data.
06It does not sync your local profile across browsers or devices.
Do not rely on a compact headline. Follow each fee source, branch, time change, limit, and milestone.
A clear Behavior Score can describe a bad incentive. Validity is not endorsement.
In a future onchain product, verify chain, token, pool, hook, configuration, deployment provenance, and audits. None is available for current local profiles.
Time, price, access, rewards, and routing may require oracles, lists, custody, accounting, and indexers that introduce their own failure modes.
Programmable mechanics do not create demand, liquidity, honest creators, or investment safety.