Programmable markets
Separate the feature-gated Classic launch from the future JUSTYPE Hook Engine.
Documentation index
A programmable market includes explicit behavior beyond a static pair and LP fee. JUSTYPE designs and explains those behaviors; Classic V1 launches a standard token and hookless market without executing them.
- 01Parse
- 02Normalize
- 03Validate
- 04Review + Behavior Score
- 05Wallet + canonical market reads
- 06FEATURE-GATED CLASSIC V4
- ARule compiler / adapter
- BHook execution
- CStock-token pair execution
Classic launches use canonical Uniswap contracts. No JUSTYPE hook or programmable execution contract is deployed.
Current code: design plus Classic market infrastructure
You can describe behavior, review structured rules, and save a local profile. Separately, the feature-gated Classic path can create a canonical UERC20 and TOKEN / ETH v4 market. Its metadata associates the reviewed rule-profile hash but says explicitly that those rules are not enforced.
Planned: an execution adapter with a narrower contract surface
The repository identifies a future rule compiler or adapter that would accept only validated, supported rule families and map them to audited deployment parameters. That integration has not been designed in contract code here, so the eventual executable subset may be smaller than the frontend’s current 21-type language.
Why Uniswap v4 is relevant
Uniswap v4 lets a pool attach an optional hook contract whose selected callbacks can run around lifecycle actions. That makes v4 a relevant architecture for market-specific behavior. It does not make arbitrary behavior safe or automatically compatible, and hooks still require careful contract design, testing, deployment, and review.